Bug Tracker item #2981066, was opened at 2010-04-02 15:05
Message generated for change (Tracker Item Submitted) made by ls999
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=2981066&group_id=250683

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: daemon
Group: v3.9.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By:  LS999 (ls999)
Assigned to: Nobody/Anonymous (nobody)
Summary: email-addr upper|lower case 

Initial Comment:
I'm use now hash_drv for testing dspam & found next problem: 'To' & 'From' mail 
fields can use uppper & lower case symbols (it not impotant for smtp). As 
result DB can contain some info for one email (a...@mydomain.no, 
a...@mydomain.no and more more, more...). 

Result: 
- DB contain all versions of a...@mydomain.no in all variantes in five days in 
my case  (Oo-disk space is not rubber!)
- if mail send to a...@myemail.no i can't retrain DB when send message later 
from a...@myemail.no to s...@mydomain.no. will see:

"Apr  2 13:37:37 main dspam[26224]: Unable to open file for reading: 
/var/local/dspam/data/mydomain.no/aa/aa.sig/4bb554fb268827715621127.sig: No   
such file or directory
Apr  2 13:37:37 main dspam[26224]: Signature retrieval for 
'4bb554fb268827715621127' failed
Apr  2 13:37:37 main dspam[26224]: Unable to find a valid signature. Aborting.
Apr  2 13:37:37 main dspam[26224]: process_message returned error -5.  dropping 
message."

but real signature is present in the 
/var/local/dspam/data/MyEmail.NO/Aa/Aa.sig/ directory

IMHO it some smtp-server depended & realy possibility limits when use another 
processing what described in README (i realy can rewrite this data using 
smtp-server abilites, but it will global for all another processes after dspam. 
and it not bes way for me as example. it MUST work internally)

one-side: all email-addr must processed as is
another-side: subsequent analysis must be case-insensitive

IMHO daemon CAN (&mb must) process incoming email-addr as is, for collect data, 
but database processing (exactly - signatures find) must be 
case-insensitive|config options regulated

PS as add: require to future 'opt-in' 'opt-out' domain based checks when 
compuled with --enable-domain-scale options  (global l level is, user level is, 
where is domain level?)

PSS Oooo and more: custom queries to DB  in conf. I think not only me already 
have & use self user+servises databases. Another DB from U & permanent synk on 
every UID  change not show best (therefore i try hash_drv engine for testing 
now).

TY & Best regards.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1126467&aid=2981066&group_id=250683

------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Dspam-devel mailing list
Dspam-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-devel

Reply via email to