Olivier Sannier wrote:
I would like to confirm a few things:
1. AFAIK, it won't be an open relay for anyone but only for
authenticated STMP users. This behaviour is the default one and nothing
needs to be configured.
Yep.
2. I can use something like SpamHaus to filter by IPs, I've seen the
option in the webadmin interface so I should be able to turn that on if
needed
Yep.
3. I've heard about greylisting where the default answer is to say "come
back later". Initial testing suggests that courier is handling that well
when connecting to a remote server. However, can it be configured to
behave like this when receiving SMTP connections?
You can get third-party software to do that. Once such solution is
pythonfilter, which I wrote:
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/
4. I've seen servers that refuse mails from mine saying that the domain
is not routeable. I've looked around and it seems that's because they
try to contact the MX server for my domain as a way to verify the
originating server and address exist. As my server is not "live" on the
Internet, that does not work yet. Can this kind of behaviour be
configured in Courier? And is it desirable?
You can get that, also, from third-party software, such as pythonfilter.
17 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Last checks befor...
