Hi Tom,
Thanks for your reply.
As a full email address hits dspam I have these options set:
ParseToHeaders on
ChangeModeOnParse on
ChangeUserOnParse full
The description for these options:
----------------------------------------------
# ParseToHeader: Parse the To: headers of an incoming message. This must be
# set to 'on' to use either of the following features.
#
# ChangeModeOnParse: Automatically change the class (to spam or innocent)
# depending on whether spam- or notspam- was specified, and change the source
# to 'error'. This is convenient if you're not using aliases at all, but
# are delivering via LMTP.
#
# ChangeUserOnParse: Automatically change the username to match that specified
# in the To: header. For example, spam-...@domain.tld will set the username
# to bob, ignoring any --user passed in. This may not always be desirable if
# you are using virtual email addresses as usernames. Options:
# on or user take the portion before the @ sign only
# full take everything after the initial {spam,notspam}-.
#
----------------------------------------------
Dspam will take email address "b...@example.com" (or
{spam,notspam}-b...@example.com) and rename it to just "bob".
This is then used as an unique id. Using the extlookup.conf (in
/etc/dspam/dspam.d), Ldap looks up all email address and returns a valid
matching id('uid') that dspam uses to store training data/retrieve preferences
in/from its mysql db(or whatever backend you're using). This is a sure method
of finding all email aliases and addresses associated with one user (in ldap)
and storing all training data against that user. Also when logging into the
dspam webfrontend I use the standard apache ldap auth mod and it uses the same
ldap 'uid' to auth which then gives me all the relevant info for that specific
user with all its associated email address/aliases.
You do make a point though that I could use the full email address.
If I go for this method and still use ldap to check for valid users I'll need
to append my domain on the ldap result (which I don't see as an option in
extlookup.conf) and also do some similar magic on the apache auth mod
mechanism. Of course, I'm open to suggestions.
Cheers,
----- Original Message -----
From: "Tom Hendrikx" <t...@whyscream.net>
To: dspam-user@lists.sourceforge.net
Sent: Thursday, June 6, 2013 9:20:41 AM
Subject: Re: [Dspam-user] Releasing quarantined mail uses 'username' instead of
original rcpt
On 06/05/2013 01:36 PM, Garith Dugmore wrote:
> Hi All,
>
> When releasing a quarantined email via the webfrontend Dspam releases
> it to, what I assume is, the 'username' in the 'dspam_virtual_uids'
> rather than the original "rcpt to".
>
Why don't you make dspam use the e-mail addfress as the username? When
checking your config files, it seems to me that you should already be
doing that. Where does the e-mail address => username translation
currently happen?
--
Garith Dugmore
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
