From: "Christopher Hilton" <[EMAIL PROTECTED]>
jdow wrote:Spamd does talk to the remote smtp. It does this until it determines that the remote smtp is RFC compliant in the area of retrying mail. On the first delivery attempt it sets up a time window for the delivery tuple: (server, sender, recipient). If it receives another delivery attempt within this time window it modifies a PF table which allows further delivery attempts to bypass spamd and talk directly to your actual smtp daemon. Without this entry remote smtp daemons talk to your spamd.Features aside I see a huge problem with something called spamd. That is the same name as the daemon mode for SpamAssassin. It's not good to have duplicated names that way. It makes life difficult when you want to run both tools on the same system.Agreed. Fortunately in this case Spam Assassin's spamd installs in the wrong part of heir: /usr/local/bin I believe and OpenBSD's spamd installs in ${PREFIX}/libexec.
That does not make it OK. What happens if the SpamAssassin maintainers
setup FreeBSD installs to go to the correct part of the heir instead
of the wrong part.
It's not a good idea. But for the time being its safe. I'd still recommend
a change.
{^_-}
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
