-
Notifications
You must be signed in to change notification settings - Fork 179
Q0612
Why does the pipe transport add a line starting with >From
to
messages?
Actually, it adds a line starting with From
followed by a space. This
is commonly referred to as the From_
line, to emphasize the fact that
From
is followed by a space and not a colon. This is a pseudo-header
line that contains the envelope sender address and the time of delivery.
It originated as a separator line in Berkeley format mailboxes, but is
also used in other contexts. (And yes, it is often confused with the
From: header line, and this causes a lot of grief. The use of From_
was one of the really bad email design decisions.) Exim's pipe
transport adds this pseudo-header line by default because
/usr/ucb/vacation needs it, and that is one of the the most common
uses of piping. The procmail local delivery agent also makes use of
the From_
line. If you do not want it, change the setting of
message_prefix
on the pipe transport. For example, to remove the
line altogether, use
message_prefix =
If you are not piping to /usr/ucb/vacation or procmail, it is likely
that you do not need a From_
line, and indeed it may cause problems if
it is present. One user reported that this line gave trouble when a pipe
was used to send messages to Courier's deliverquota program. The line
was retained with the message, and caused problems for MS Exchange 2000
when retrieving messages with its built-in POP collector. Specifically,
it caused Exchange to not be able to recognise message attachments.
- What does the error *Neither the xxx router nor the yyy transport set a
- Exim keeps crashing with segmentation errors (signal 11 or 139) during
- How can mails that are being routed through routers that do not set
- I want to use MMDF-style mailboxes. How can I get Exim to append the
- If a user's mailbox is over quota, is there a way for me to set it up so
- I'm using tmail to do local deliveries, but when I turned on the
- When I activate return receipt > for example in Netscape Mailbox sending options, then I get an error
- What does the message retry time not reached [for any host] on the log
- Exim seems to be sending the same message twice, according to the log,
- How can I force the next retry time for a host to be now?
- I set up
|/bin/grep Subject|/usr/bin/smbclient -M <netbiosname>
as an - Why does the pipe transport add a line starting with
>From
to - I have set
fallback_hosts
on my smtp transport, but after the - After the holidays my ISP has always hundreds of e-mails waiting for me.
- When a message in the queue got to 12h old, Exim wrote *retry timeout
- Can Exim add a Content-Length: header to messages it delivers?
- Exim seems to be trying to deliver a message every 10 minutes, though
- I am trying to set exim up to have a automatic failover if it sees that
- I can't get Exim to deliver over NFS. I get the error *fcntl() failed:
- Why does Exim bounce messages without even attempting delivery, giving
- My .forward file is
|/usr/bin/procmail -f-
and mail gets delivered, - Can I write an ordinary file when I run a perl script as a transport
- My /var/spool/mail has grown drastically. Is there any possibility of
- Sendmail has a program called smrsh that restricts what binaries can
- I wish to have large emails go out one at a time.
- Exim can route local parts independent of their case, but the Cyrus LMTP
- Is there a command I can send to Exim to retry all queued messages
- I have the default retry rule, which I thought meant that Exim should
- I'm having trouble with quotas and Courier, because Exim is not handling
- How can I configure Exim to deliver to a Cyrus message store?
- I would like to choose a retry rule based on on the sender rather than
- What does the error *User 1 set for local_mbx_delivery transport is on
- Why is $domain not set in the smtp transport?
- How can I stop a local transport from trying to access the user's home
- The log message error ignored appears after some delivery failures.