Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Message success/faliure delivery notification - mailx Post 302646509 by manoharg on Friday 25th of May 2012 08:34:11 AM
Old 05-25-2012
Message success/faliure delivery notification - mailx

Guys,

Is it possible to get a delivery status message like success/faliure notification after sending a mail using mailx.

-v option can be used to get the message failure notification if any..

is there any option to get the message success notification?
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

email attachment, with a message using mailx

Hi, I am trying to include a message along with an attachment with an email using mailx on AIX. uuencode Test.dat Test.dat| mailx -s 'Testing' mymail@yahoo.com < MESGFILE This only gives me the contents of MESGFILE as my message. If I remove the < FILE I recieve the attachment. What... (4 Replies)
Discussion started by: edog
4 Replies

2. UNIX for Dummies Questions & Answers

mailx error message : mailx: NUL changed to @

If I use the "Mail" link instead of the "mail" link to ../mailx I get this error. Mail so-n-so @whatever.com mailx: NUL changed to @ Unknown command: "postmaster" The email still goes through but i get the error. If I use "mail" it goes thru without the error. Any ideas?? (2 Replies)
Discussion started by: BG_JrAdmin
2 Replies

3. UNIX for Dummies Questions & Answers

Success status of mailx command

Hi I want to know if the email address in the mailx exists or not Eg: Mailx -s "Subj" hello@ab.com How do I know if the email address is a valid one??? (4 Replies)
Discussion started by: superprogrammer
4 Replies

4. Shell Programming and Scripting

Problem while sending message and attachment with mailx

Hi All, I am trying to send a mail with an attachment and message. Following command I am using. (cat <messagefile> ; uuencode <attachmentfile> <attachmentfile>)|mailx -s"Subject" dave@email.com In the received mail, message body is appearing fine. But attachment is not coming. Rather... (2 Replies)
Discussion started by: nihar.dutta
2 Replies

5. Shell Programming and Scripting

How to receive message in 2 lines using mailx command

Hi, I have a file with 2 records in two lines. While mailing these two records using mailx command, those two records coming in a single line. I have used the following command to send those records via mail. cat filename | mailx -s "subject" mailaddress I want the two records in... (3 Replies)
Discussion started by: siri_886
3 Replies

6. UNIX for Dummies Questions & Answers

Mailx empty body message

Hi, Is there a way to suppress this message? Null message body; hope that's ok My email string is: mailx -s "This is my subject" myemail@domain.com < /dev/null It's just an annoyance to me that I would like see go away. (3 Replies)
Discussion started by: bbbngowc
3 Replies

7. Shell Programming and Scripting

Mailx with attachment and message body

i have to attach the 'body in the email' along with attachment below code is throwing errors, how can i do it ? here body file contains message, it should display in email, please help i am using HP-UX (cat body ;) (uuencode attch1 attch1 ;) | mailx -m -s "testing" "abc@gmail.com" ... (4 Replies)
Discussion started by: only4satish
4 Replies

8. Shell Programming and Scripting

Adding Pager notification to mailx command.

Is it possible to add Pager Notification to mailx command?? :confused: Or by any other mean. ---------- Post updated at 08:49 AM ---------- Previous update was at 07:08 AM ---------- Hi just want to specify that by Pager i mean a message to the mobile number. Suppose i have following... (1 Reply)
Discussion started by: Sharma331
1 Replies

9. Solaris

Mailx message not delivering externally

I have recently all of a sudden stopped receiving my cronjob messages that were being sent with the mailx command. I have not made any changes and it is affecting all my servers at this site only (all running Solaris 10). At my other site I am running a mixture of Solaris 10 and Ubuntu 14, and they... (2 Replies)
Discussion started by: Madrox72
2 Replies
mq_notify(3RT)						    Realtime Library Functions						    mq_notify(3RT)

NAME
mq_notify - notify process (or thread) that a message is available on a queue SYNOPSIS
cc [ flag... ] file... -lrt [ library... ] #include <mqueue.h> int mq_notify(mqd_t mqdes, const struct sigevent *notification); DESCRIPTION
The mq_notify() function provides an asynchronous mechanism for processes to receive notice that messages are available in a message queue, rather than synchronously blocking (waiting) in mq_receive(3RT). If notification is not NULL, this function registers the calling process to be notified of message arrival at an empty message queue asso- ciated with the message queue descriptor, mqdes. The notification specified by notification will be sent to the process when the message queue transitions from empty to non-empty. At any time, only one process may be registered for notification by a specific message queue. If the calling process or any other process has already registered for notification of message arrival at the specified message queue, subse- quent attempts to register for that message queue will fail. The notification argument points to a structure that defines both the signal to be generated and how the calling process will be notified upon I/O completion. If notification->sigev_notify is SIGEV_NONE, then no signal will be posted upon I/O completion, but the error status and the return status for the operation will be set appropriately. If notification->sigev_notify is SIGEV_SIGNAL, then the signal specified in notification->sigev_signo will be sent to the process. If the SA_SIGINFO flag is set for that signal number, then the signal will be queued to the process and the value specified in notification->sigev_value will be the si_value component of the generated signal (see sig- info.h(3HEAD)). If notification is NULL and the process is currently registered for notification by the specified message queue, the existing registration is removed. The message queue is then available for future registration. When the notification is sent to the registered process, its registration is removed. The message queue is then be available for registra- tion. If a process has registered for notification of message arrival at a message queue and some processes is blocked in mq_receive(3RT) waiting to receive a message when a message arrives at the queue, the arriving message will be received by the appropriate mq_receive(3RT), and no notification will be sent to the registered process. The resulting behavior is as if the message queue remains empty, and this notification will not be sent until the next arrival of a message at this queue. Any notification registration is removed if the calling process either closes the message queue or exits. RETURN VALUES
Upon successful completion, mq_notify() returns 0; otherwise, it returns -1 and sets errno to indicate the error. ERRORS
The mq_notify() function will fail if: EBADF The mqdes argument is not a valid message queue descriptor. EBUSY A process is already registered for notification by the message queue. ENOSYS The mq_notify() function is not supported by the system. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
mqueue.h(3HEAD), siginfo.h(3HEAD), signal.h(3HEAD), mq_close(3RT), mq_open(3RT), mq_receive(3RT), mq_send(3RT), attributes(5), standards(5) NOTES
Solaris 2.6 was the first release to support the Asynchronous Input and Output option. Prior to this release, this function always returned -1 and set errno to ENOSYS. SunOS 5.10 28 Jun 2002 mq_notify(3RT)
All times are GMT -4. The time now is 01:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy