I have now gotten seven e-mails from Fetchmail Daemon with the following text,
therein:
Received: from lists.suse.de (195.135.221.131)
by mail01j.rapidsite.net (RS ver 1.0.94vs) with SMTP id 4-0350368368
for
* C Hamel
I have now gotten seven e-mails from Fetchmail Daemon with the following text, therein: Received: from lists.suse.de (195.135.221.131) by mail01j.rapidsite.net (RS ver 1.0.94vs) with SMTP id 4-0350368368 for
; Fri, 30 Jul 2004 18:59:28 -0400 (EDT)
as root edit /etc/postfix/header_checks, add: /^From:.*FETCHMAIL-DAEMON@ovoplus.com/ REJECT then as root, run: /usr/sbin/postmap /etc/postfix/header_checks and: /sbin/rcpostfix restart and they will not be accepted by your machine. This *assumes* you are running your own mail server. If not, procmail :0 * ^From.*FETCHMAIL-DAEMON@ovoplus.com /dev/null -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
* C Hamel
[07-30-04 18:32]: I have now gotten seven e-mails from Fetchmail Daemon with the following text, therein: Received: from lists.suse.de (195.135.221.131) by mail01j.rapidsite.net (RS ver 1.0.94vs) with SMTP id 4-0350368368 for
; Fri, 30 Jul 2004 18:59:28 -0400 (EDT) as root edit /etc/postfix/header_checks, add: /^From:.*FETCHMAIL-DAEMON@ovoplus.com/ REJECT
then as root, run: /usr/sbin/postmap /etc/postfix/header_checks and: /sbin/rcpostfix restart
and they will not be accepted by your machine.
This *assumes* you are running your own mail server.
If not, procmail
:0
* ^From.*FETCHMAIL-DAEMON@ovoplus.com /dev/null
-- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos Sorry... forgot to mention this is what is coming into my personal account. Seems to be from suse-linux-e. -- ...CH "The more they over-think the plumbing,
On Friday 30 July 2004 18:48, Patrick Shanahan wrote: the easier it is to stop up the drain." Scotty
The Friday 2004-07-30 at 19:18 -0500, C Hamel wrote:
Sorry... forgot to mention this is what is coming into my personal account. Seems to be from suse-linux-e.
Exactly. That's why Patrick sugests you block them, they are not originating from your fetchmail, but from somebody else's fetchmail - at least, as far as we can guess, because you have not posted the full headers of the message (no From/To/received). They seem to come from @ovoplus.com -- Cheers, Carlos Robinson
Please trim your posts.
* C Hamel
Sorry... forgot to mention this is what is coming into my personal account. Seems to be from suse-linux-e.
no, read the headers. the mx, mail01j.rapidsite.net], is getting a
rejection of mail to sist.mex@ovoplus.com delivered by lists.suse.de with
your 'From:' address:
<quote> [from your previous post]
Received: from lists.suse.de (195.135.221.131)
by mail01j.rapidsite.net (RS ver 1.0.94vs) with SMTP id 4-0350368368
for
On Friday 30 July 2004 21:03, Patrick Shanahan wrote:
Please trim your posts. <SNIP> Gotcha. <G> That enough? ;-)
Realized I'd mis-typed just after I sent. Everything is well in hand. Thanks. -- ...CH "The more they over-think the plumbing, the easier it is to stop up the drain." Scotty
The Friday 2004-07-30 at 21:03 -0500, Patrick Shanahan wrote:
so, if you are fetching your mail from your ip, use the procmail recipe. If you are running your own server with postfix, use the header_checks solution.
You can use the headers_checks in either case, with a trick. Or, better, I think, the "access" file (less cpu, acts earlier): # rules to reject unwanted email Mailer-Daemon@orinoco.dattaorinoco.com REJECT Blocking backscatter mail from virus scanners # This rule redirects email sent by _my_ fetchmail. If I don't do this, # for every reject (above) fetchmail will send another email explaining # the reject. FETCHMAIL-DAEMON@nimrodel.valinor REDIRECT virusalert@localhost I also have script to process email sent to virusalert and create logs instead. -- Cheers, Carlos Robinson
* Carlos E. R.
You can use the headers_checks in either case, with a trick. Or, better, I think, the "access" file (less cpu, acts earlier):
agree that 'access' is probably a better choice for the reason you present. Header_checks would be better for a string in 'subject' or other part of the header other than a 'From:' address.
# rules to reject unwanted email Mailer-Daemon@orinoco.dattaorinoco.com REJECT Blocking backscatter mail from virus scanners
the chars after REJECT are comments ??
# This rule redirects email sent by _my_ fetchmail. If I don't do this, # for every reject (above) fetchmail will send another email explaining # the reject. FETCHMAIL-DAEMON@nimrodel.valinor REDIRECT virusalert@localhost
You do this in 'access' ?? or in virtual ????
I also have script to process email sent to virusalert and create logs instead.
Procmail ?? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos
The Saturday 2004-07-31 at 20:05 -0500, Patrick Shanahan wrote:
You can use the headers_checks in either case, with a trick. Or, better, I think, the "access" file (less cpu, acts earlier):
agree that 'access' is probably a better choice for the reason you present. Header_checks would be better for a string in 'subject' or other part of the header other than a 'From:' address.
Exactly. But previously I also used header-checks.
# rules to reject unwanted email Mailer-Daemon@orinoco.dattaorinoco.com REJECT Blocking backscatter mail from virus scanners
the chars after REJECT are comments ??
No, they are given back as a reject reason in the smtp dialog - in my
case, to fetchmail, otherwise, to whatever is at the other side. See the
logs:
Jun 18 12:02:09 nimrodel fetchmail[4865]: SMTP> MAIL FROM:
# This rule redirects email sent by _my_ fetchmail. If I don't do this, # for every reject (above) fetchmail will send another email explaining # the reject. FETCHMAIL-DAEMON@nimrodel.valinor REDIRECT virusalert@localhost
You do this in 'access' ?? or in virtual ????
In access as well, yes. Redirect is a new addition, I wanted to use it. Virtual... well, perhaps :-? Ah, no, I used it because an "access" rule works even for a match on the "From" part, thus triggering when fetchmail sends email. I forgot to document it O:-)
I also have script to process email sent to virusalert and create logs instead.
Procmail ??
Right. :-) A quick hack: :0 * ^From.*FETCHMAIL-DAEMON@nimrodel.valinor { :0 c $HOME/Mail/root/in_fetchmail :0 | cat > $HOME/bin/pfb.input ; $HOME/bin/pfb } Then I parse that email using the script HOME/bin/pfb. I don't like that 'cat' there, but it works. That reminds me, I have to revise it, something has changed when I upgraded and some info is missing from the log I generate. -- Cheers, Carlos Robinson
participants (3)
-
C Hamel
-
Carlos E. R.
-
Patrick Shanahan