Date: Tue, 19 Dec 2006 18:00:32 -0800 From: "jdow" <jdow@earthlink.net> To: <freebsd-stable@FreeBSD.ORG> Subject: Re: OpenBSD's spamd. Message-ID: <013001c723da$a1fb1d60$0225a8c0@wednesday> References: <200612191227.kBJCRRLJ054427@lurza.secnetix.de> <4587D1B6.6060500@andric.com><200612191146.45521.joao@matik.com.br> <45882572.7040707@vindaloo.com> <00b801c723be$106ce980$0225a8c0@wednesday> <45887CAF.6010007@vindaloo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Christopher Hilton" <chris@vindaloo.com>
> 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.
{^_-}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?013001c723da$a1fb1d60$0225a8c0>