9 More Discussions You Might Find Interesting
1. Solaris
Hi
I seem to have a problem in my solaris 10server, when I type mailx the following pop up:
mailx
mailx version 5.0 Type ? for help.
"/var/mail//moneta": 109 messages 1 new 109 unread
U100 Mail Delivery Subs Thu Sep 17 04:34 133/5631 Warning: could not send m
U101 moneta ... (2 Replies)
Discussion started by: fretagi
2 Replies
2. Shell Programming and Scripting
Hi,
I have two scripts viz
and
I am running them in background.
I wish to know if both the scripts completed execution successfully.
So this is what I have done
/tmp/commet/bin/connectdb1.sh &
condb1=$?
/tmp/commet/bin/connectdb2.sh &
condb2=$?
However, I am getting error... (7 Replies)
Discussion started by: mohtashims
7 Replies
3. Shell Programming and Scripting
Hi,
I have a FTP server and a directory location where i will be FTPing the flat file.
My requirement is
After the flat file was generated to the location, i need to write some trigger file or something to inform them that the file was delivered to them.
Please let me know how i can do... (2 Replies)
Discussion started by: srikanth_sagi
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
There is a unix box in production from which mails will be sent to user/group. From this box, many mails will be sent. But only for one mail which is sent from the box, it is showing a message like "Deferred: 421 Microsoft ESMTP MAIL Service, Version: 6.0.3790.4675 ready at Service not... (2 Replies)
Discussion started by: trichyselva
2 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
First time poster, I hope I have the basics covered.
I am trying to execute a .sh but finding I am getting inconsistent results. A fresh set of eyes would be great.
I am using Solaris 10 zones.
So I am trying to execute a script but I am getting different results between... (2 Replies)
Discussion started by: att01
2 Replies
6. Shell Programming and Scripting
Guys,
How can we know whether a script has been executed successfully or not ?
We dont have any log directories, and we are not given a chance to modify the script. Could someone help me out with this Thanks (2 Replies)
Discussion started by: bobby1015
2 Replies
7. Shell Programming and Scripting
Hi,
I have a program which creates some report and sends it to the users. There are around 15000 users . I guess because of this huge number the mail exchange server is unable to deliver all the mails. So i want to create a log to see who are all the user to whom the report was delivered. I am... (2 Replies)
Discussion started by: gnagendr
2 Replies
8. AIX
Hi,
How difficult would it be to configure an alert on AIX that will inform me every time someone logs into the system? (1 Reply)
Discussion started by: bbbngowc
1 Replies
9. UNIX for Dummies Questions & Answers
Hello There,
Aftar all i successfully installed Solaris 8 on my Primary Slave 2nd Hard disk.
Here what i did.
I kept my first hard disk (Windows Me) on primary Master and put my new 2nd hard disk on Primary Slave, CDROM is on Secondary slave.
When i install solaris8 it ask me two... (0 Replies)
Discussion started by: abidmalik
0 Replies
envelopes(5) File Formats Manual envelopes(5)
NAME
envelopes - sender/recipient lists attached to messages
INTRODUCTION
Electronic mail messages are delivered in envelopes.
An envelope lists a sender and one or more recipients. Usually these envelope addresses are the same as the addresses listed in the mes-
sage header:
(envelope) from djb to root
From: djb
To: root
In more complicated situations, though, the envelope addresses may differ from the header addresses.
ENVELOPE EXAMPLES
When a message is delivered to several people at different locations, it is first photocopied and placed into several envelopes:
(envelope) from djb to root
From: djb Copy #1 of message
To: root, god@brl.mil
(envelope) from djb to god@brl.mil
From: djb Copy #2 of message
To: root, god@brl.mil
When a message is delivered to several people at the same location, the sender doesn't have to photocopy it. He can instead stuff it into
one envelope with several addresses; the recipients will make the photocopy:
(envelope) from djb to god@brl.mil, angel@brl.mil
From: djb
To: god@brl.mil, angel@brl.mil, joe, frde
Bounced mail is sent back to the envelope sender address. The bounced mail doesn't list an envelope sender, so bounce loops are impossi-
ble:
(envelope) from <> to djb
From: MAILER-DAEMON
To: djb
Subject: unknown user frde
The recipient of a message may make another copy and forward it in a new envelope:
(envelope) from djb to joe
From: djb Original message
To: joe
(envelope) from joe to fred
From: djb Forwarded message
To: joe
A mailing list works almost the same way:
(envelope) from djb to sos-list
From: djb Original message
To: sos-list
(envelope) from sos-owner to god@brl.mil
From: djb Forwarded message
To: sos-list to recipient #1
(envelope) from sos-owner to frde
From: djb Forwarded message
To: sos-list to recipient #2
Notice that the mailing list is set up to replace the envelope sender with something new, sos-owner. So bounces will come back to sos-
owner:
(envelope) from <> to sos-owner
From: MAILER-DAEMON
To: sos-owner
Subject: unknown user frde
It's a good idea to set up an extra address, sos-owner, like this: the original envelope sender (djb) has no way to fix bad sos-list
addresses, and of course bounces must not be sent to sos-list itself.
HOW ENVELOPE ADDRESSES ARE STORED
Envelope sender and envelope recipient addresses are transmitted and recorded in several ways.
When a user injects mail through qmail-inject, he can supply a Return-Path line or a -f option for the envelope sender; by default the
envelope sender is his login name. The envelope recipient addresses can be taken from the command line or from various header fields,
depending on the options to qmail-inject. Similar comments apply to sendmail.
When a message is transferred from one machine to another through SMTP, the envelope sender is given in a MAIL FROM command, the envelope
recipients are given in RCPT TO commands, and the message is supplied separately by a DATA command.
When a message is delivered by qmail to a single local recipient, qmail-local records the recipient in Delivered-To and the envelope sender
in Return-Path. It uses Delivered-To to detect mail forwarding loops.
sendmail normally records the envelope sender in Return-Path. It does not record envelope recipient addresses, on the theory that they are
redundant: you received the mail, so you must have been one of the envelope recipients.
Note that, if the header doesn't have any recipient addresses, sendmail will move envelope recipient addresses back into the header. This
situation occurs if all addresses were originally listed as Bcc, since Bcc is automatically removed. When sendmail sees this, it creates a
new Apparently-To header field with the envelope recipient addresses. This has the strange effect that each blind-carbon-copy recipient
will see a list of all recipients on the same machine.
When a message is stored in mbox format, the envelope sender is recorded at the top of the message as a UUCP-style From (no colon) line.
Note that this line is less reliable than the Return-Path line added by qmail-local or sendmail.
SEE ALSO
qmail-header(5), qmail-local(8), qmail-inject(8)
envelopes(5)