Complex routing Introduction Sendmail routes mail using the domain of the recipient. If this resolves to this machine (local user), Sendmail uses the user's name to finish the job. Sometime, the decision should be done using both the user's name and destination domain as a whole. 11.. PPrriinncciipplleess One reality of the _I_n_t_e_r_n_e_t these days is the virtual hosting of multiple domains on the same server. This works fine for web service. A single server fakes many virtual servers. For electronic mail, Sendmail has the ability to accept email for multiple domains. Generally, all those domains are aliases (see Aliases for your system in basic sendmail configuration) for your system. If your system has the following aliases: · domain1.com · domain2.com Then user@domain1.com and user@domain2.com points to the same user account and email folder. This may be wrong sometime. Complex user routing can be understood this way: If you receive email for one_user@one_domain then forward this mail to another_user@another_domain using another_email_server. 22.. TTaasskk For each rule, you must filled a screen composed of theses fields. 22..11.. TThhiiss rruullee iiss aaccttiivvee You can deactivate one rule without erasing it. You must regenerate the sendmail.cf file and restart _S_e_n_d_m_a_i_l (Linuxconf will tell you to do so anyway). 22..22.. ttoo The _t_o field contain the original email destination including the full domain name. It is possible to redirect a full domain by only entering the domain name with the _@ character as a prefix (@domain.com). While redirecting a domain is normally done with the special domain routing facility of linuxconf, using complex user routing allow you to redirect a complete domain to a single user account into another domain: Handy! 22..33.. RReewwrriitttteenn ttoo You must enter the new email destination. If you wish to redirect the email to another local user, you can simply enter the user account without domain. This looks like a simple aliases (see "Setting user aliases". While it is not a replacement for it, it is more general. For large user base, the normal user aliases is more efficient as it uses a database. The complex user routing should be used to handle exceptions which can't be solved by normal user aliases. For example, normal user aliases can't solved this. · info@vdomain1.com -> joe · info@vdomain2.com -> jack 22..44.. FFoorrwwaarrdd ttoo sseerrvveerr((oopptt)) Normally _S_e_n_d_m_a_i_l will find the proper server based on the _R_e_w_r_i_t_t_e_n _t_o field. Sometime, you may want to impose a server. You just write the fully qualified name here. 22..55.. MMaaiilleerr If you specify a server, you must specify the protocol to use. Normally esmtp should be used. You can also select uucp-dom when forwarding email through a uucp gateway. This is one case where you will always specify a destination server. 22..66.. CCoommmmeenntt This is a free form comment. You write whatever you want here.