Derrick T. Woolworth wrote: > On 4/5/06, Gordon Messmer <[EMAIL PROTECTED]> wrote: > > Derrick T. Woolworth wrote: > > > I'm strongly considering writing a courierfilter that will do the > > > following: > > > > > > 1. For routed domains/hosts, check a database for valid users and > > > reject if the incoming message isn't to a valid user. Make the > > > filter > > > logs the rejection in a way I can parse it from the logs. > > > > You don't need a courierfilter for that. Use the database of valid > > addresses, and build an alias file that redirects them to their > > destinations. Make those routed domains "hosteddomains". Courier > > will reject invalid recipients immediately, and presumably, you are > > already looking at those messages in the logs, so you don't need to > > extend what you're already doing. > > Unfortunately, I'm not that familiar with MS Exchange server. I'm > just wondering if it works more like Sendmail where the domain name > is irrelevant to the username - so an e-mail sent to the alias > [EMAIL PROTECTED] will actually be deposited into the [EMAIL PROTECTED] > account - or if domain must match? > > I'm positive the customers doing this won't want to hear that their > e-mail address on their Exchange box has to be different than their > "real" e-mail address.
The users don't need to know anything about it. This is similar to what we do here. Courier accepts the mail, scans it, and then forwards it to Exchange. The Exchange configuration for each user has two email addresses defined for them. I can use the secondary address to do the forwarding from Courier and the users never see it. So... Courier accepts mail for [EMAIL PROTECTED] and forwards to [EMAIL PROTECTED] Exchange knows about and will accept both. [EMAIL PROTECTED] is set as the default email address, so that is what Exchange uses when the user sends mail. The only person who needs to know about the extra address is the Exchange admin. > The reason we use Courier as an e-mail gateway is due to the filters > that work much better than anything Exchange has to offer - which, > again, I don't know Exchange so that might not be correct. Either > way, its a nice scenario where the users that want to take advantage > of Courier's filtering capabilities create valid accounts on the > Courier box. The folks that don't want their e-mail filtered don't > need accounts because Courier automatically routes e-mail to the > Exchange box, untouched. This is why I'm suggesting one small filter > that checks to see if an account is valid - and the ldap idea sounds > like a really good one. We let SA scan and put header tags in all of the mail. Users who want to take advantage of it create rules in their mail reader to sort the mail based on the SA markup. Those who don't want it can just ignore it. We are also considering dropping the Exchange server entirely and just using IMAP on the Courier box. This would simplify the configuration considerably. -- Bowie ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
