Elliot Foster wrote:
Bob Dodds wrote:
Eye candy. http://perlq.org/filter.png
check_earlytalker and require_resolvable_from_host
and spf, and qpsmtpd in general, are doing a fine job.
Thanks to Matt Sergeant for recommending a longer
check_earlytalker wait time.
-Bob
Which leads me to ask:
1.) What was the longer check_earlytalker wait time?
2.) Are you rejecting on soft spf failures, or just hard?
3.) What generated the graph?
-Elliot
check_earlytalker wait 13 action deny
sender_permitted_from spf_deny 1
GD::Graph3d, hacking the code from dspam's webui
admingraph.cgi so it works with the output of half a
dozen perl scripts. I use qpsmtpd loglevel 7|8, so I
can grep message id's and compare those with dspam
system.log to see if mail delivered to/through dspam
was classified as spam. I don't see dspam retrains
in my chart so I think I have to hack my sendmail
script to save message id's on retrains. dspam retrains
"corpus" and I don't think it all goes into system.log or
it's not in there as "S"--I'm grepping the "S" lines and
then taking message id's and when dspam hits on
enough spam, it should show up in the chart as if
it was a plugin. I think dspam is just being "honest"
and not claiming credit if it had to be told, but for
my chart I would like to add dspam's catch to
retrains so I know what got past qpsmtpd and av.
My electricity just went off, on ups now. I was
going to look up what Matt S said, was it 12 to
33 seconds for check_earlytalker? I'm at 13.
Let's see if the dslam's diesel generator is on.
-Bob
