What does the error Neither the xxx router nor the yyy transport set a uid for local delivery of... mean?

Exim keeps crashing with segmentation errors (signal 11 or 139) during delivery. This seems to happen when it is about to contact a remote host or when a delivery is deferred.

How can mails that are being routed through routers that do not set check_local_user be delivered under the uid of the recipient?

I want to use MMDF-style mailboxes. How can I get Exim to append the ctrl-A characters that separate indvidual emails?

If a user's mailbox is over quota, is there a way for me to set it up so that the mail bounces to the sender and is not stored in the mail queue?

I'm using tmail to do local deliveries, but when I turned on the use_crlf option on the pipe transport (tmail prefers \r\n terminations) message bodies started to vanish.

When I activate “return receipt” for example in Netscape Mailbox sending options, then I get an error message from Exim... something like not supported. Can I activate delivery confirmations?

What does the message retry time not reached [for any host] on the log mean? Why won't Exim try to deliver the message?

Exim seems to be sending the same message twice, according to the log, although there is a difference in capitalization of the local part of the address.

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 alias but it doesn't work.

Why does the pipe transport add a line starting with >From to messages?

I have set fallback_hosts on my smtp transport, but after the error sem@example.com cannot be resolved at this time Exim isn't using them.

After the holidays my ISP has always hundreds of e-mails waiting for me. These are forced down Exim's throat in one go. Exim spawns a lot of kids, but is there some limit to the number of processes it creates?

When a message in the queue got to 12h old, Exim wrote retry timeout exceeded and removed all messages in the queue to this host - even recent messages. How I can avoid this behaviour? I only want to remove messages that have exceeded the maximum retry time.

Can Exim add a Content-Length: header to messages it delivers?

Exim seems to be trying to deliver a message every 10 minutes, though the retry rules specify longer times after a while, because it is writing a log entry every time, like this:

1999-08-26 14:51:19 11IVsE-000MuP-00 == example@example.com T=smtp defer
(-34): some host address lookups failed and retry time not reached for
other hosts or connection limit reached

I am trying to set exim up to have a automatic failover if it sees that the system that it is sending all mail to is down.

I can't get Exim to deliver over NFS. I get the error fcntl() failed: No locks available, though the lock daemon is running on the NFS server and other hosts are able to access it.

Why does Exim bounce messages without even attempting delivery, giving the error retry time not reached for any host after a long failure period?

My .forward file is |/usr/bin/procmail -f- and mail gets delivered, but there was a bounce to the sender, sending him the output of procmail. How can I prevent this?

Can I write an ordinary file when I run a perl script as a transport filter for the remote_smtp and address_pipe transports?

My /var/spool/mail has grown drastically. Is there any possibility of using two directories?

Sendmail has a program called smrsh that restricts what binaries can be run from sendmail aliases. Is there something like this in Exim ?

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 daemon requires the correct case. How can I fix this?

Is there a command I can send to Exim to retry all queued messages regardless of their retry schedule?

I have the default retry rule, which I thought meant that Exim should keep trying for four days, but it seems to be bouncing some messages immediately.

I'm having trouble with quotas and Courier, because Exim is not handling maildirsize files.

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 the recipient address. Is this possible?

What does the error User 1 set for local_mbx_delivery transport is on the never_users list mean?

Why is $domain not set in the smtp transport?

How can I stop a local transport from trying to access the user's home directory, even when the delivery is to a file that is elsewhere?

The log message error ignored appears after some delivery failures. What does it mean?