Praedor Atrebates wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have logged directly into my popmail server (yahoo) via the web and find
that the spam message isn't being repeatedly sent - the same message is
causing a problem over and over. Yahoo tagged it as spam and put it in my
On Sunday 19 October 2003 09:17 pm, Praedor Atrebates wrote:
I have receive over 100 of these today alone. Nothing i've tried with
procmail recipes has worked. I cannot stop this nonsense. The from
address is my own fetchmail-daemon:
[EMAIL PROTECTED]
I am considering having all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Here is the syslog entry associated with this repetitive spam (based on the
[EMAIL PROTECTED] message):
^[[B^[[BOct 20 08:57:26 lapdog postfix/smtpd[9542]: connect from
localhost.localdomain[127.0.0.1]
Oct 20 08:57:26 lapdog postfix/smtpd[9542]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have logged directly into my popmail server (yahoo) via the web and find
that the spam message isn't being repeatedly sent - the same message is
causing a problem over and over. Yahoo tagged it as spam and put it in my
bulk mail folder on their
On Monday 20 October 2003 09:11 am, Praedor Atrebates wrote:
snipped
Okay, we don't see the Postfix error code but based upon the text of the
message, my guess is that Postfix is rejecting this message upon the delivery
attempt by Fetchmail, fetchmail is then sending a failure message to let
On Monday 20 October 2003 09:38 am, Praedor Atrebates wrote:
I have logged directly into my popmail server (yahoo) via the web and find
that the spam message isn't being repeatedly sent - the same message is
causing a problem over and over. Yahoo tagged it as spam and put it in my
bulk mail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you, that appears to have done the trick.
I was getting filled up with a new spam, producing the same type of message,
but adding that line to fetchmailrc did the trick. It is gone.
I was getting quite angry and frustrated with this
On Monday 20 October 2003 11:52 am, Praedor Atrebates wrote:
Thank you, that appears to have done the trick.
I was getting filled up with a new spam, producing the same type of
message, but adding that line to fetchmailrc did the trick. It is gone.
I was getting quite angry and frustrated
Praedor Atrebates grabbed a keyboard and wrote:
I have logged directly into my popmail server (yahoo) via the web and find
that the spam message isn't being repeatedly sent - the same message is
causing a problem over and over. Yahoo tagged it as spam and put it in my
bulk mail folder on
Bryan Phinney grabbed a keyboard and wrote:
The fetchmail log should be telling you what the error code is from Postfix
but if I had to guess, I would say it is a 501, fetchmail normally counts 55?
codes as spam rejects by default.
Not on *my* system, it didn't. :-) I had to put it in to
On Monday 20 October 2003 03:23 pm, David Guntner wrote:
Bryan Phinney grabbed a keyboard and wrote:
The fetchmail log should be telling you what the error code is from
Postfix but if I had to guess, I would say it is a 501, fetchmail
normally counts 55? codes as spam rejects by default.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have receive over 100 of these today alone. Nothing i've tried with
procmail recipes has worked. I cannot stop this nonsense. The from address
is my own fetchmail-daemon:
[EMAIL PROTECTED]
I am considering having all fetchmail-daemon emails
I have receive over 100 of these today alone. Nothing i've tried with
procmail recipes has worked. I cannot stop this nonsense. The from
address
is my own fetchmail-daemon:
[EMAIL PROTECTED]
I am considering having all fetchmail-daemon emails sent to dev/null but
fear
the
13 matches
Mail list logo
