* Sam Clippinger <[email protected]> [2010-02-13]: > Messages with an empty sender address are legal -- they are typically > used for bounce messages. Because of that, spamdyke will allow them. > > However, messages with empty usernames (e.g. "@example.com") are not > legal and should not be allowed. This could indicate a bug in > spamdyke... is there any chance you still have the mail log entries that > correspond to those addresses? It would be very handy to see what was > actually sent with those messages.
I didn't have the a log entry for the example I posted, but I ran the config test again and looked for some newer problems. I looked at the following error. ERROR(graylist-level): Unable to read graylist sender directory /var/spamdyke/graylist/kompakt.no/modulonet.fr/ezewuehuuw1728:irectory ERROR(graylist-level): Failed to create file in directory: /var/spamdyke/graylist/kompakt.no/gvt.net.br/vuaqanipos2110/spamdyk266176143_28737: Not a directory The corresponding entry in the SMTP log: 02-02 21:07:44 spamdyke[31368]: DENIED_GRAYLISTED from: [email protected] to: @kompakt.no origin_ip: 85.68.111.68 origin_rdns: abo-68-111-68.mrs.modulonet.fr auth: (unknown) So it seems this might be a bug in Spamdyke or? > The incorrect directories are not a problem, they're just out of place. > No legitimate deliveries will match those paths, so they won't get in > the way. You can delete them or ignore them as you wish. OK. Just a thought: Is this something that could be added to the prune script that was posted on the list some days ago? Regards, Hans > On 2/12/10 7:32 AM, Hans F. Nordhaug wrote: > > Hi! > > > > Today I decied to run a config test of my spamdyke. Don't know why - > > it seems to have been running quite nicely on it's own. Anyway: > > ======================================================================== > > [r...@post ~]# /usr/local/bin/spamdyke --log-level=debug \ > > --run-as-user vpopmail --config-test \ > > --config-file /etc/spamdyke/spamdyke.conf /var/qmail/bin/qmail-smtpd > > > > spamdyke 4.0.10+TLS+CONFIGTEST+DEBUG (C)2008 Sam Clippinger, samc (at) > > silence (dot) org > > http://www.spamdyke.org/ > > > > Use -h for an option summary or see README.html for complete option details. > > > > SUCCESS: Running tests as user vpopmail(89), group root(0). > > SUCCESS: /var/qmail/bin/qmail-smtpd appears to offer TLS support but > > spamdyke will intercept and decrypt the TLS traffic so all of its filters > > can operate. > > SUCCESS: /var/qmail/bin/qmail-smtpd appears to offer SMTP AUTH support. > > spamdyke will observe any authentication and trust its response. > > SUCCESS(config-file): Opened for reading: /etc/spamdyke/spamdyke.conf > > > > ERROR(graylist-level): Failed to create file in directory: > > /var/spamdyke/graylist/kompakt.no/belgacom.be/yvurem6825/spamdyke-test_1265980207_18181: > > Not a directory > > ERROR(graylist-level): Unable to read graylist sender directory > > /var/spamdyke/graylist/kompakt.no/belgacom.be/yvurem6825: Not a directory > > [....] > > > > [r...@post ~]# ls -l > > /var/spamdyke/graylist/kompakt.no/belgacom.be/yvurem6825 > > -rw------- 1 vpopmail vchkpw 0 jan 21 15:24 > > /var/spamdyke/graylist/kompakt.no/belgacom.be/yvurem6825 > > [r...@post ~]# cat /var/spamdyke/graylist/kompakt.no/belgacom.be/yvurem6825 > > [r...@post ~]# > > > > ======================================================================== > > > > It seems as if SpamDyke has received a message to<NOTHING>@kompakt.no > > from [email protected]. I have some questions: > > > > 1) Is an e-mail with an empty local part illegal (according to > > RFC XYZ)? Should SpamDyke even accept it? > > 2) If is it legal, I think SpamDyke should stop it anyway. Or? > > 3) Is these files that should have been directories really a problem? > > > > Thx for your time (and effort on SpamDyke). > > > > Regards, > > Hans _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
