Bit late now but the usual method for seeing if a command succeeded is to catch the return code, e.g.:
If the return code is zero then the command succeeded.
Another test you could do is to run mailq and ensure the queue is empty.
Hello,
I need to forward mail wich are in some users mailbox. The .forward redirection is working for all new mails but not for old. Is someone know how to do this ?
Thanks (2 Replies)
Hi there
I am using mailx command to send mails. I want to send some important files to team members and wud like to know if the team member has recd my email or not.
How can I achieve this ?
Currently my piece of code is
uuencode ${FILE_NAME} ${FILE_NAME} >> mail_msg.txt
mailx -s"test... (5 Replies)
Hello guys,
Am trying to enable/start sendmail in Solaris 10. I tried using scvadm and also did it using the /etc/init.d/sendmail restart but no effect. Just returns to the prompt. No errors nothing. I checked if it is running using ps -eaf | grep sendmail, not running :( . I checked the logs... (9 Replies)
Hello All,
i have configured sendmail and trying to set a limit on mail
Ex: If i have send any mail to a email-if that doesn'e exists, i want that after trying for 3 days it should stops sending that mail to user and send a mail to the sender that " sending mail failed , any messaged... (1 Reply)
1.
I need to send emails using a shell script on linux. I want to use the most widespread method (the preferred method). Is one considered deprecated in favor of the other? Which, mail or sendmail ?
2.
Now, without trying to favor mail in the first question: How can I include a From: mail... (1 Reply)
Hi,
Is there any way to check the status of the mail sent or not.e.g
mail -s "Error Message" abc@xyz.com <aaa/bbb/data.txt
Can it return a status code which will confirm the delivery of mail sent?Please suggest.
Thanks,
Anil (1 Reply)
The question is, Does the mail comman actually send using sendmail or something else?
So I am trying to test if sendmail is set up. I used...
cat testemail.txt | mail -s "test mail" myemail@test.com
I used my email though I didn't get an error, but didn't get the email either.
... (2 Replies)
Hi All,
I like to check the status of sendmail and take the appropriate action based on success / failure etc.
I have gone through one of the thread where a suggestion is made to use RC for return code
Following is the code:
==================================
#!/usr/bin/bash
export... (0 Replies)
PHP mail() function doesn't work.
Nor does sendmail:
loaded system configuration file /etc/msmtprc
ignoring user configuration file /home/xi/.msmtprc: No such file or directory
falling back to default account
using account default from /etc/msmtprc
host = xsi
port = 25
proxy host = (not... (1 Reply)
Discussion started by: Xcislav
1 Replies
LEARN ABOUT HPUX
stopping
stopping(7) Miscellaneous Information Manual stopping(7)NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO starting(7)started(7)stopped(7)init(5)Upstart 2009-07-09 stopping(7)