Note that luser_relay specifies a single local address. ^^^^^^^^ The problem is that these accounts are not local.
Yes - but quite often often you get a case where the guy wants these accounts both on the LAN and on the remote mailserver (say central MX).
Also, if you use luser_relay, you render yourself open to having your mailboxes stuffed up with junk and your mail spool overflowing the next time someone dictionary attacks your domain, trying to send mail to random addresses at your domain.
What I've built before at a previous job is a mailhub sort of setup where all the hubs perform reciprocal backup MX for each other, and route addresses internally using mailertables (because they had two interfaces - a low bandwidth 64kbps internet connection and a much fatter leased line between each of the branches - bombay, pune, cochin, coimbatore).
A central LDAP server was used to provision addresses, so that all branches had a view of the userdb (which also served as an address book, after quite some work to make sure outlook would understand the results returned by the ldap server ... no matter that netscape understood it without that work, and the mailserver understood it too ... a few people used outlook and they'd scream bloody murder.
srs
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
linux-india-help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/linux-india-help
