<pre>> ><i> Some of this may be related to the fact that I am using<br></i>> ><i> fetchmail to get mail from outside servers and hand it off to my<br></i>> ><i> exim4.. but I don't understand *how* it's related (or what I'm
<br></i><br>> Ahaha, now you fess up :)<br><br> um.. yup.. mea culpa ;-}<br><br>> SA-Exim is mostly useless if you use fetchmail.<br>> Greylisting cannot work if you already accepted the Email.<br>> SMTP time filtering is irrelevant if you're feeding the mail from fetchmail.
<br><br>OK. I can understand that once the mail is received somewhere, <br>you can't treat it the same as if you were receiving it<br>directly from the sender.. I'm doing about 1/2 and 1/2 right now..<br>My own domain/server is new, so I'm still getting stuff at old addresses..
<br>and most of the spam is going to the old addys.. <br><br>But I still don't understand what is causing perl to do so much whining..<br>I'm no guru, but I do use perl quite a bit, and I'm having a helluva time
<br>understanding what's going on here.. <br><br>> If you don't have access to your outside MX to run SA-Exim there, you should<br>> drop SA-Exim and just use spamassassin.<br>> Sorry, SA-Exim cannot do much of anything useful in your situation.
<br><br>Too bad.. cuz apart from these perl complaints, it *feels* like sa-exim<br>is doing what I want -- the spam is gone and the good mail is getting in! <br><br>But, ok, I'll remove sa-exim from my config, and see if I can just
<br>get SA working alone.. Thanks for the help.<br><br><br>cheers,<br><br>John<br><br><br><br><br><br><br></pre>