Sylvain Garcia wrote:
> Hi, I 'm working always on integration of dspam into OBM 
> (http://www.obm.org)
>
> I had install Dspam in my production environment to make some test 
> with OBM. And I have some problem, i don't understand.
>
> I use dspam git with debian package on kirya.net 
> (http://packages.kirya.net/dspam-community)
> Dspam use postgresql 8.3 backend on debian Etch.
>
> dspam is configured with LMTP and postfix and also amavis ( with no 
> relation with dspam ):
>
> Postfix --LMTP--> DSPAM --SMTP--> Postfix --SMTP--> 
> Amavis(SA)--SMTP-->Postfix ---LMTP---Cyrus
>
>
> I configured dspam to check user on ldap:
> ExtLookup                       on
> ExtLookupMode           strict
> ExtLookupDriver ldap
> ExtLookupServer localhost
> ExtLookupPort           389
> ExtLookupDB             "dc=local"
> ExtLookupQuery 
> "(&(|(objectclass=obmuser)(objectclass=obmMailShare))(mailBox=%u))"
> ExtLookupLDAPAttribute  "mailBox"
> ExtLookupLDAPScope              sub
> ExtLookupLDAPVersion    3
>
>
> The problem is that i have some user which are create in dspam, but 
> they don't exist on ldap....
>
> for exemple:
> dspam_stat:
> [email protected]  TP:     3 TN:     2 FP:     0 FN:     0 SC:     0 
> NC:     0
>
> there is no user whith this mail adress in my ldap, But i have one 
> user which ave sieve script on cyrus which bounce mail at this adress,
> and in log we can see:
> "External lookup verification of [email protected] failed: not adding 
> user"
> and:
> SELECT * from dspam_virtual_uids where username = 
> '[email protected]'; return:
>  uid |           username
> -----+-------------------------------
>  110 | [email protected]
>
>
> [email protected] is an example on my dspam database but i 
> have 30 users which doesn't exist on my ldap, and i have 78 real user 
> on dspam.


Hello Sylvain,

First things first. Why would you have a user in your database with the 
domain gmail.com? Are you accepting mail for that domain? I believe 
you're using DSPAM in your outbound mail too. Are you sure you want to 
do this?

Second, what you describe doesn't mean that it's not working as it 
should. Although the user doesn't exist in LDAP, DSPAM still processes 
the message. It just doesn't polute the dspam virtual user table, but it 
will still write statistical message processing information into its 
data directory (That's not handled in by the database yet). dspam_stats 
only prints out the users statistical data that resides in ~dspam/data.

Also note that the select you perform isn't quite correct. The user that 
failed to verify is [email protected]. I doubt you'll get any entry if 
you do

SELECT * from dspam_virtual_uids where username = '[email protected]';

The external lookup procedure is rather new in DSPAM and as such DSPAM 
behaviour is to continue operation, even if the user doesn't verify and 
it's operating in strict mode. Surely that can be changed. It's just a 
matter of debate and weighting the pros and cons.

In the meantime, i would advise you review why you have DSPAM checking 
outbound email (if i did understood things correctly).


Best regards,

Hugo Monteiro.

-- 
ci.fct.unl.pt:~# cat .signature

Hugo Monteiro
Email    : [email protected]
Telefone : +351 212948300 Ext.15307
Web      : http://hmonteiro.net

Centro de Informática
Faculdade de Ciências e Tecnologia da
                   Universidade Nova de Lisboa
Quinta da Torre   2829-516 Caparica   Portugal
Telefone: +351 212948596   Fax: +351 212948548
www.ci.fct.unl.pt             [email protected]

ci.fct.unl.pt:~# _


------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Dspam-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-devel

Reply via email to