> 
> Anthony Ercolano wrote:
>> Well I think I might have my own answer to my question.
>> 
>> It *appears* as though the messages that weren't getting graylisted were 
>> sent using tls.
>> 
> 
> Very interesting. Upon what are you basing this observation?
> 

After turning log level up to debug (and redirecting the spamdyke syslog 
messages to a spamdyke specific log file) I waited until I received email that 
didn't show up in the graylist.  I looked at the arrival time of the email.  I 
looked in the log.  For the piece of email that arrived at that time I found:

spamdyke[32690]: TLS_ENCRYPTED from: (unknown) to: (unknown) origin_ip: 
192.223.136.139 origin_rdns: lrtp86-03.fidelity.com auth: (unknown)

I looked up in the documentation for spamdyke and it said:

"spamdyke supports TLS in several ways. First, with no TLS options given, 
spamdyke will .... This prevents some of its filters from functioning, 
including graylisting,"

I had no tls options set.

I have now set tls-level to smtp

However, I haven't received any new mail from a sender who uses tls so we'll 
have to see what happens then. 


> I notice that with the 4.1 release, there is an indication of 
> encryption: in the spamdyke log messages (thank you very much for this, 
> Sam).
> 
> I am seeing some DENIED_GRAYLISTED log messages with encryption: TLS. I 
> haven't checked though to see if there's actually an entry in the 
> graylist tree or not. Are you seeing such messages in your smtp log?
> 

Not sure what you mean.  If you're talking about the log from spamdyke, then 
see above.  If you are talking about the qmail-smtpd logs, then I wouldn't know 
what to look for there.

I am a little hesitant to move up to 4.1  It looks like there is a nasty 
relaying bug mentioned in Vol 38 Issue 12 message 8.  (Unless of course it's in 
4.01 in which case it would be no loss.) 

> -- 
> -Eric 'shubes'

Tony

_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to