I need to have any mail for virt.dom.ain that doesn't match one of the aliases in /usr/lib/aliases.virt delivered to a particular address, for example, postmaster@virt.dom.ain.

How do I arrange for all incoming email for *@some.domain to go into one pop3 mail account? The customer doesn't want to add a list of specific local parts to the system.

How do I configure Exim to send messages for unknown local users to a central server?

How can I arrange for messages submitted by (for example) Majordomo to be handled specially?

On a host that accepts mail for several domains, do I have to use fully qualified addresses in /etc/aliases or do I have to set up an alias file for each domain?

Some of my users are using the .forward to pipe to a shell command which appends to the user's INBOX. How can I forbid this?

How can I arrange for a default value when using a query-style lookup such as LDAP or NIS+ to handle aliases?

If I don't fully qualify the addresses in a virtual domain's alias file then mail to aliases which also match the local domain get delivered to the local domain.

I want mail for any local part at certain virtual domains to go to a single address for each domain.

How can I make Exim look in the alias NIS map instead of /etc/aliases?

Why will Exim deliver a message locally to any username that is longer than 8 characters as long as the first 8 characters match one of the local usernames?

Why am I seeing the error bad mode (100664) for /home/test/.forward? I've looked through the documentation but can't see anything to suggest that Exim has to do anything other than read the .forward file.

When a user's .forward file is syntactially invalid, Exim defers delivery of all messages to that user, which sometimes include the user's own test messages. Can it be told to ignore the .forward file and/or inform the user of the error?

I have set caseful_local_part on the routers that handle my local domain because my users have upper case letters in their login names, but incoming mail now has to use the correct case. Can I relax this somehow?

Can I use my existing alias files and forward files as well as procmail and effectively drop in Exim in place of Sendmail ?

What is quickest way to set up Exim so any message sent to a non-existing user would bounce back with a different message, based on the name of non-existing user?

What do I need to do to make Exim handle /usr/ucb/vacation processing automatically, so that people could just create a .vacation.msg file in their home directory and not have to edit their .forward file?

I want to use a default entry in my alias file to handle unknown local parts, but it picks up the local parts that the aliases generate. For example, if the alias file is

luke.skywalker: luke
ls: luke
*: postmaster

then messages addressed to luke.skywalker end up at postmaster.

I have some obsolete domains which people have been warned not to use any more. How can I arrange to delete any mail that is sent to them?

How can I arrange that mail addressed to anything@something.mydomain.com gets delivered to something@mydomain.com?

I can't get a regular expression to work in a local_parts option on one of my routers.

How can I arrange for all addresses in a group of domains *.example.com to share the same alias file? I have a number of such groups.

Some of our users have no home directories; the field in the password file contains /no/home/dir. This causes the error failed to stat /no/home/dir (No such file or directory) when Exim tries to look for a .forward file, and the delivery is deferred.

How can I disable Exim's de-duplication features? I want it to do two deliveries if two different aliases expand to the same address.

My users' mailboxes are distributed between several servers according to the first letter of the user name. All the servers receive incoming mail at random. I would like to have the same configuration file for all the servers, which does local delivery for the mailboxes it holds, and sends other addresses to the correct other server. Is this possible?

One of the things I want to set up is for anything@onedomain to forward to anything@anotherdomain. I tried adding $local_part@anotherdomain to my aliases but it did not expand - it sent it to that literal address.

How can I have an address looked up in two different alias files, and delivered to all the addresses that are found?

I've converted from Sendmail, and I notice that Exim doesn't make use of the owner- entries in my alias file to change the sender address in outgoing messages to a mailing list.

I would like to deliver mail addressed to a given domain to local mailboxes, but also to generate messages to the envelope senders.

Whenever Exim tries to route a local address, it gives a permission denied error for the .forward file, like this:

1998-08-10 16:55:32 0z5y2W-0000B8-00 == xxxx@yyy.zzz <xxxx@yyy.zz>
  D=userforward defer (-1): failed to open /home/xxxx/.forward
  (userforward router): Permission denied (euid=1234 egid=101)

How do I configure Exim to allow arbitrary extensions in local parts, of the form +extension?

I use NIS for my user data. How can I stop Exim rejecting mail when my NIS servers are being restarted?

How can I arrange for a single address to be processed by both redirect and accept?

How can I redirect all local parts that are not in my system aliases to a single address? I tried using an asterisk in the system alias file with an lsearch* lookup, but that sent all messages to the default address.

My alias file contains fully qualified addresses as keys (as it was used in sendmail's /etc/mail/virtualusertable), and some wildcard domains in the form @foo.bar. Can Exim handle these?