allowing relay is the same as connect without auth. An auth'd user is granted the ability to relay, so allowing an IP to relay is effectively the same.
Ok, except that I don't want this ip to be able to relay.
I want my users to connect to my Courier box to send email via authenticated smtp. Unauthenticated users or Internet MTAs should not be allowed to connect. General email from the Internet comes through a filtering server. This server needs to be able to deliver to the Courier box, but it is unable to authenticate itself.
So... - The filtering server should be able to connect without authentication - The filtering server should NOT be able to relay - Everyone else should be required to authenticate
It sounds like the mail from the filtering server will all be destined for your user server, so you should not need any special setup. Courier will accept mail for addresses that it is configured to accept mail for. Just don't put your user server in DNS as an MX, that's easy.
The filtering server will have to be configured to accept mail for your domains so that it can filter the messages and then forward the good messages onto your user server. Is this where you need help?
/etc/courier/smtpaccess/ should at this point only allow 127.0.0.1 to relay, just so your scripts and whatnot can mail you, etc.
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
