On 01:03 Thu 07 May , Ion-Mihai Tetcu wrote: > On Tue, 17 Mar 2009 12:09:06 +0100 (CET) > "Mate Gabri" <mailingl...@modernbiztonsag.org> wrote: > > > > > > > -------- Original-Nachricht -------- > > >> Datum: Mon, 16 Mar 2009 20:55:26 +0100 > > >> Von: Gabri Mate <mailingl...@modernbiztonsag.org> > > >> An: dspam-devel@lists.sourceforge.net > > >> Betreff: [Dspam-devel] forged from header - not scanning > > > > > >> Hey there! > > >> > > > Hello. > > > > > > > > >> I've recently noticed that if i recieve a spam with a forged > > >> header, so it appears that i have sent it that mail to myself from > > >> the address in question, then dspam won't process it. > > >> > > >> I have an account which i check with fetchmail and i pass the > > >> message to dspam through procmail: > > >> > > >> #dspam > > >> :0fw > > >> | /usr/local/bin/dspam --stdout --deliver=innocent,spam --mode=teft > > >> --feature=noise --user dotty > > >> > > >> but if the sender is the same as the recipient, then dspam won't > > >> analyze it. I haven't found a configuration option for this issue > > >> yet. > > >> > > >> Do You have any advice? > > >> > > > 1) Can you post the full header of the message dspam does deliver > > > after not scanning the message? > > So? :-)
Ah sorry. I got totally distracted from this problem. I've made a not so nice "if the from is the same as the recipient then go to /dev/hell" rule in the user's procmailrc, so you could say that this is solved. Anyway, the account is not a real e-mail account. It fetches the mails with fetchmail from the remote server then i use dspam to do some processing. > > > I'm not in front of that machine, but i can tell that there were not a > > single header from dspam. So the message wasn't through dspam. > > > > > > 2) Could you post some log entries showing that dspam did not or did > > > processed the message? > > > > I can't see anything in the logs, even in the procmail log files. > > > > Maybe somehow the procmail filter won't process a message from > > 'myself'? > > > > > > > > > btw: There is no such switch in the dsapm configuration to disable > > > complete scanning of messages. Every message get's tagged in the > > > headers by dspam. So if it is processed by dspam, then there must > > > be a entry in the headers. If there is no entry in the headers, > > > then you have not processed the message with dspam. > > > > Yes, that's what i thought. Maybe i have to look around procmail to > > figure out the problem. > > This is a local, non-dspam problem for sure. > > -- > IOnut - Un^d^dregistered ;) FreeBSD "user" > "Intellectual Property" is nowhere near as valuable as "Intellect" > FreeBSD committer -> ite...@freebsd.org, PGP Key ID 057E9F8B493A297B > !DSPAM:117,4a020ae483011028019401! -- Gabri Mate ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ Dspam-devel mailing list Dspam-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-devel
