On Saturday 14 April 2007, Bart Schaefer wrote:
>On 4/13/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
>> Now, I *think* I have that X-Originating-Ip: 193.93.97.195 in my
>> .procmailrc, but it didn't fire. Odd...
>
>Is that rule before or after the point at which you run the message
>through spamas
On 4/13/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
Now, I *think* I have that X-Originating-Ip: 193.93.97.195 in my .procmailrc,
but it didn't fire. Odd...
Is that rule before or after the point at which you run the message
through spamassassin?
If after, it probably ddin't fire because spam
On Friday 13 April 2007, Bart Schaefer wrote:
>On 4/13/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
>> The trail starts at localhost! HTF did they do that?
>
>You're looking at the header of the wrapper message created by
>spamassassin, not at the header of the actual spam (which will be
>inside a
On 4/13/07, Gene Heskett <[EMAIL PROTECTED]> wrote:
The trail starts at localhost! HTF did they do that?
You're looking at the header of the wrapper message created by
spamassassin, not at the header of the actual spam (which will be
inside a message/rfc822 body part of the message created by
Hi;
I use fetchmail, sucking from 3 accounts, piped thru by procmail spamc before
procmail puits it in the local 'gene' file in /var/spool/mail, so this was
spam, but where the heck did it come from?
(header only by copy-paste)
==
Received: from localhost by coyote.coyote.den
with SpamAs
