atom feed21 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Mail Server Inter...
FromSent OnAttachments
Derrick T. WoolworthApr 5, 2006 11:38 am 
Bowie BaileyApr 5, 2006 12:25 pm 
Gordon MessmerApr 5, 2006 12:36 pm 
Sam VarshavchikApr 5, 2006 3:41 pm 
Derrick T. WoolworthApr 5, 2006 10:17 pm 
Bowie BaileyApr 6, 2006 6:57 am 
Gordon MessmerApr 7, 2006 12:08 am 
Derrick T. WoolworthApr 7, 2006 1:31 am 
Ricardo KleemannJun 22, 2006 8:30 am 
Sam VarshavchikJun 22, 2006 2:38 pm 
Ricardo KleemannJun 23, 2006 7:27 am 
Binand SethumadhavanJun 23, 2006 7:39 am 
Jerry AmundsonJun 23, 2006 8:03 am 
Alessandro VeselyJun 23, 2006 8:13 am 
Ricardo KleemannJun 23, 2006 8:23 am 
Alessandro VeselyJun 23, 2006 8:39 am 
Alexei Batyr'Jun 23, 2006 8:41 am 
Mark BucciarelliJun 23, 2006 8:46 am 
Ricardo KleemannJun 23, 2006 9:48 am 
Alessandro VeselyJun 23, 2006 10:16 am 
Sam VarshavchikJun 23, 2006 3:55 pm 
Subject:RE: [courier-users] Mail Server Interrogation
From:Bowie Bailey (Bowi@BUC.com)
Date:Apr 5, 2006 12:25:40 pm
List:net.sourceforge.lists.courier-users

Derrick T. Woolworth wrote:

As for my routed hosts - where some customers to use our mail system as a filter and then deliver the scanned and cleaned messages to their MS Exchange server (ick), we have real problems with that because as a router, our system will accept ALL e-mail destined for the final host and our system doesn't reject based on a valid user. Of course, when the system finds out the e-mail address is invalid, it can't return the message because its come from no where or an invalid address.

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.

I haven't tried it myself, but I have been told that Exchange can act as an LDAP server. So you can use LDAP to verify users for your hosted domains.