Darrin Chandler wrote:
On Thu, Aug 10, 2006 at 09:39:56AM -0400, Will H. Backman wrote:
Am I correct in assuming that spamd and TLS on port 25 don't get along?
-- Will
Remember that you get *either* spamd *or* your MTA. So there's no
getting along to deal with.
However, if the connecting party *requires* TLS then it would have a
problem with spamd. Is that the trouble you're having?
Yes. I'm protecting a Microsoft Exchange server with spamd on an
openbsd bridge. Because Microsoft Outlook uses Microsoft's way of
having MUAs talk to MTAs, there is no problem there.
I also enabled IMAPS (port 993) and SMTP-TLS (port 25) on the Exchange
Server so that normal mail clients like Thunderbird can play along.
Because I require TLS and SMTP-AUTH for relaying purposes, I'm in a
bind. My real problem is getting Exchange to do SMTP-TLS on a different
port, so this is really a non-openbsd issue. I guess I was just asking
to make sure, and also to see if people had dealt with situation like
this. I can imagine that openbsd and spamd are used to protect all
kinds of pesky MTAs.
By the way, I just have to keep saying thanks for openbsd and spamd.
Greylisting has been really effective for my organization. I've been
running it for 6 days and it has done a great job.
