|
|
|
|
||||||
| comp.mail.sendmail Configuring and using the BSD sendmail agent. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hello Group,
A bit of background: I use a server -let's call this one SERVER1- running Scalix 11.3 to manage all my domains and mailboxes which uses sendmail to relay outbound mails to another server of mine -let's call this one SERVER2- as a smarthost. SERVER2 runs sendmail as well, resides in the same network and uses an external server (my ISP's one) as a smarthost for all outbound mails. On SERVER2 amavis in the dual-sendmail configuration is running as well for anti-spam/anti-virus purposes. So far so good, this was the easy part. SERVER2 is the entry point for all mails (also for fetchmail, running on a third server, the gateway), does its checks and if the mail is clean it will be delivered. Scenario: fetchmail@gateway --> sm-daemon1@SERVER2 --> amavis@SERVER2 --> sm- daemon2@SERVER2 --> mailboxes@SERVER1 In SERVER2's mailertable there are entries for the domains hosted on SERVER1 in order to deliver the mails to the respective mailboxes on SERVER1. This is actually working OK for all domains which are completely hosted on SERVER1. But -as always- there is an exception: there is a domain "partially" hosted on SERVER1 -let's call it difficult.domain- because one user in my network wants to keep this other e-mail address of his for historical reasons, all other users of this domain are hosted somewhere else in the outside world. Now, here is my problem: If I send a mail to a user @difficult.domain other than the one locally hosted, the mail keeps bouncing back. Scenario: 1. SERVER1 delivers it via sendmail to SERVER2 (the smarthost) because the address is not managed locally 2. SERVER2 delivers it back to SERVER1 because its mailertable says that it has to do so Now my question to the group: is there any configuration (a mailertable or some other entry) which would allow SERVER2 to deliver the mails @difficult.domain only for one user to SERVER1 and for the rest to the smtp server of my ISP? Is this possible at all? Any would be very much appreciated since I have tried all I could but I am still stuck ... Thanks a lot in advance to you all, LP |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
On 03/25/08 12:21, lpacor@gmail.com wrote:
> Now my question to the group: is there any configuration (a > mailertable or some other entry) which would allow SERVER2 to deliver > the mails @difficult.domain only for one user to SERVER1 and for the > rest to the smtp server of my ISP? Is this possible at all? Search the recent archives of this news group. I believe I recently saw (read: briefly skimmed) a thread about having Mailertable route messages for individual recipients rather than domains. I don't know if it is possible or not, but you may be able to do something where the more specific match (difficult user) is found first followed by the less specific match (difficult domain) is found last. Have the more specific match route the messages to difficult user to SERVER1 while routing the remainder of the messages to your ISP. > Any would be very much appreciated since I have tried all I > could but I am still stuck ... I have not tested any of this. This is just where I would look to try what you are asking to do. If you are unable to have both more specific and less specific matches, you may have to have more specific matches for each recipient, one pointing to SERVER1 and the rest pointing to your ISP. Of course, there is also LDAP routing that you can use to route messages. Grant. . . . |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
lpacor@gmail.com wrote:
> [...] > Now my question to the group: is there any configuration (a > mailertable or some other entry) which would allow SERVER2 to deliver > the mails @difficult.domain only for one user to SERVER1 and for the > rest to the smtp server of my ISP? Is this possible at all? > > Any would be very much appreciated since I have tried all I could > but I am still stuck ... You can use FEATURE(`ldap_routing') It can be used with standard maps (hash,dbm) instead of LDAP lookups. http://www.sendmail.org/m4/ldap_routing.html FEATURE(`ldap_routing', `hash /etc/mail/mail_host', `hash /etc/mail/mail_routing_address', `bounce') -- [pl>en: Andrew] Andrzej Adam Filip : anfi@priv.onet.pl : anfi@xl.wp.pl Open-Sendmail: http://open-sendmail.sourceforge.net/ The man who has never been flogged has never been taught. -- Menander |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
> [...]
> > You can use FEATURE(`ldap_routing') > It can be used with standard maps (hash,dbm) instead of LDAP lookups.http://www.sendmail.org/m4/ldap_routing.html > > FEATURE(`ldap_routing', `hash /etc/mail/mail_host', > `hash /etc/mail/mail_routing_address', `bounce') > Thanks a lot! Where is it meant to be implemented? I guess on SERVER2? Would you be so kind to give me an example of the syntax? Pardon my stupidity, but I really am not what you could call a sendmail expert ... Cheers, LP |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Late, but though ...
I was able to make everything work with FEATURE(`ldap_routing'). Thanks a lot folks! LP |
|
![]() |
| Outils de la discussion | |
|
|