Re: [dspam-users] re:*sigh*

John Szakmeister wrote:

> On Thursday 29 December 2005 02:41, Odhiambo Washington wrote:
>> * On 29/12/05 02:37 -0500, John Szakmeister wrote:
> [snip]
>>> I saw a similar issue with postfix and had to use --enable-virtual-users.
>>> I posted a question about when to use virtual users on the list, but
>>> have yet to receive any real responses. I'm sure it's because of the
>>> holidays though.
>>>
>>> Anyways, try passing --enable-virtual-users to your ./configure and try
>>> again. :-)
>> Does the use of --enable-virtual-users tend to deviate from the
>> explanation given in /path/to/dspam-3.6.2/README?
>> If yes, then I suggest you file a bug.
>
> Yes. The README implies that all that is necessary without virtual users is
> that the user has an account on the system. It will then attempt to lookup
> the user on the system with the part of the email address before the '@'
> sign. However, it doesn't really do that. DSPAM was still trying to perform
> the lookup on the whole email address. I found a couple of other instances
> of this same question on the list, but none of them really explained the
> situation well and just steered users towards using --enable-virtual-users.
> So I'm taking another stab at getting a good explanation before attempting to
> file a bug. :-)

The following applies to my setups, Postfix 2.2 passing either to
Amavisd-new as content filter, which passes to dspam daemon, or directly
to dspam daemon as content filter and dspam subsequently handing
localpart@domain back to Postfix unaltered, and using SQL as dspam backend:

localpart@domain is kept intact and dspam can't find localpart@domain as
a user UID (whether it uses the nss libraries for UID determination or
not I don't know, nor do I know why it can't/won't parse
localpart@domain to get the UID; maybe because the philosophy is that
the localpart@domain might not be a local user). Normally, if Postfix
were handing off via a local or virtual Postfix transport (e.g. a
maildrop or dspam transport) or delivering directly via local
transport, the standard thing to do is to strip the domain part off
before handing off.

Using virtual UIDs (dspam will fabricate a UID in the SQL backend for
each separate localpart@domain) solves this.

--Tonni

-- 
Tony Earnshaw
Email: tonni@barlaeus.nl