From: Tyler Nally (no email)
Date: Mon Jan 23 2006 - 18:53:17 EST
Hello,
Right now, I've got a well working Postfix/Amavis-new/Clamd/Spamassassin
on a Fedora Core 4 machine.
Question 1: what should the order be if I put DomainKey checking into
the smtp stream somewhere? The documentation for DKFILTER suggests a
pre-queue smtp proxy. Is that wise? Is it better to check DKeys
first before e-viri or vice-versa. What is smarter to do first? Get
rid of the bad bugs or process for domain verification?
I believe the Amavis-new (daemon) receives the e-mail via lmtp and does
it's magic before it hands it off to a Spamassassin content filter.
Amavis uses ports 10024 inbound and 10025 outbound.
DomainKey processing (dkfilter) uses a smtp proxy recommended in
documentation to receive it at port 10025 and output 10026 for
incoming e-mail into the machine
I completely understand how to change the ports around to whatever
I want. What I don't know is how to tell postfix how to send the
message to be received next by Amavis-new so that it can continue
it's merry way onto Spamassassin and then delivery.
Is it enough to just change the ports of dkfilter to listen at another
port (like 10030) and output to yet another port (like 10031)? I
don't quite understand what orders the flow of messages through
postfix. I've read the different content filter faq's, and smtp
proxy faq's, smtp faq's, cleanup, pickup, etc. and many of the others
at postfix.org.
Eventually, this server will have an "outbound only" instance of
postfix that will do the DomainKeys signing for the users of the
machine. I'm not to that hurdle yet.
Any help would be appreciated if someone would aim me in
the right direction..
-- Tyler Nally
|
|
|