Subject:
procmail-d Digest Volume 98 : Issue 8
Today's Topics:
Re: Automatic forward [ Michael Ghens
<michael(_at_)spconnect(_dot_)co ]
Re: empty message id [ era eriksson
<era(_at_)iki(_dot_)fi> ]
Re: Verify Mail Has Valid 'From:' Fi [
<jari(_dot_)aalto(_at_)poboxes(_dot_)com> ]
Re: C/Perl modules to delete attachm [
<jari(_dot_)aalto(_at_)poboxes(_dot_)com> ]
Re: Verify Mail Has Valid 'From:' Fi [ era eriksson
<era(_at_)iki(_dot_)fi> ]
Re: PROCESS THE MAIL - TO SCRIPT [
<jari(_dot_)aalto(_at_)poboxes(_dot_)com> ]
Re: Verify Mail Has Valid 'From:' Fi [
jari(_dot_)aalto(_at_)poboxes(_dot_)com ]
Verstaendnisproblem [ Stefan Wintermeyer
<sw(_at_)swr(_dot_)de> ]
Re: Verify Mail Has Valid 'From:' Fi [
jari(_dot_)aalto(_at_)poboxes(_dot_)com ]
'[Resent-]Sender:' headers [ palme(_at_)uni-wuppertal(_dot_)de
(Hubert Palm ]
Re: empty message id [ "Christopher P. Lindsey"
<lindsey(_at_)m ]
Advertisement: Website Hosting [ info(_at_)inexchange(_dot_)net
(Info Desk) ]
Re: '[Resent-]Sender:' headers [ Philip Guenther
<guenther(_at_)gac(_dot_)edu> ]
Re: Juno/hotmail/prodigy filtering [ dattier(_at_)wwa(_dot_)com (David
W. Tamkin) ]
Re: Getting files [ dattier(_at_)wwa(_dot_)com (David
W. Tamkin) ]
Re: '[Resent-]Sender:' headers [ dattier(_at_)wwa(_dot_)com (David
W. Tamkin) ]
Re: empty message id [ Rik Kabel
<rik(_at_)netcom(_dot_)com> ]
Re: empty message id [ "Christopher P. Lindsey"
<lindsey(_at_)m ]
Re: Juno/hotmail/prodigy filtering [ Rik Kabel
<rik(_at_)netcom(_dot_)com> ]
Deferred delivery to a pager [ Mike <Mike(_at_)innosoft(_dot_)com>
]
Re: Junk mail via the Smartlist list [ "Rhett 'Jonzy' Jones"
<jonzy(_at_)cc(_dot_)uta ]
------------------------------------------------------------------------
Subject: Re: Automatic forward
Date: Mon, 12 Jan 1998 22:43:45 -0800 (PST)
From: Michael Ghens <michael(_at_)spconnect(_dot_)com>
To: Oliver Briem <obriem(_at_)csc(_dot_)com>
CC: "procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de"
<procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
This is straight from the Sendmail's CF readme:
procmail An interface to procmail (does not come with sendmail).
This is designed to be used in mailertables. For example,
a common question is "how do I forward all mail for a
given
domain to a single person?". If you have this mailer
defined, you could set up a mailertable reading:
host.com procmail:/etc/procmailrcs/host.com
with the file /etc/procmailrcs/host.com reading:
:0 # forward mail for host.com
! -oi -f $1 person(_at_)other(_dot_)host
This would arrange for (anything)@host.com to be sent
to person(_at_)other(_dot_)host(_dot_) Within the procmail
script, $1 is
the name of the sender and $2 is the name of the
recipient.
If you use this with FEATURE(local_procmail), the FEATURE
should be listed first.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Michael Ghens Small Planet Connections
Internet: michael(_at_)spconnect(_dot_)com Santa Barbara, CA
http://www.spconnect.com/~michael
On Mon, 12 Jan 1998, Oliver Briem wrote:
Date: Mon, 12 Jan 1998 19:13:17 -0500
From: Oliver Briem <obriem(_at_)csc(_dot_)com>
To: "procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de"
<procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Subject: Automatic forward
Resent-Date: Tue, 13 Jan 1998 01:53:59 +0100 (MET)
Resent-From: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Hello,
I've got a problem to solve and I'm trying to find out if I can do
it via procmail. I have to forward mail from one domain to another
(domain1.com to domain2.com) for all my users without having to create
800 .forward files. At the same time sending a message to the sender
saying that this persons e-mail address has changed from
user(_at_)domain1(_dot_)com to user(_at_)domain2(_dot_)com(_dot_) . If
anyone has any suggestions
for me I would really appreciate.
Regards,
Oliver Briem
CSC Index
------------------------------------------------------------------------
Subject: Re: empty message id
Date: Tue, 13 Jan 1998 10:14:31 +0200 (EET)
From: era eriksson <era(_at_)iki(_dot_)fi>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
On Mon, 12 Jan 1998 22:51:59 -0500 (EST), gsutter(_at_)pobox(_dot_)com wrote:
> # An invalid Message-Id: header
> :0
> * !^Message-Id:[ ]*<[^ <>@]+(_at_)[^ <>@]+>[ ]*$
> { SPAMMER="invalid Message-Id: $MATCH" }
> I believe credit for this belongs to Era.
Thank you, thank you. However, as somebody pointed out, it is in fact
valid for a Message-Id to contain spaces (and presumably some other
"magic" characters, perhaps backslash-escaped), iff it is also quoted.
See RFC822 for details, or check the recent thread on this list.
(To be perfectly honest, I still use this recipe, because I never saw
a false match in the mail I receive, but YMMV.)
I also note that you are not using \/ in this recipe, and that $MATCH
will therefore contain whatever some earlier \/ happened to grab. It's
a bit tricky to get any useful logging when checking for a negated
condition, but you could always do something like
:0
* ! ^Message-Id:<... blah blah ...>
{
:0
* ! ^Message-Id:
{ SPAMMER="Ouch: no Message-Id" }
:0E
* ^Message-Id:[ ]*\/[^ ].*
{ SPAMMER="Invalid Message-Id: $MATCH" }
}
Checking for no Message-Id at all is futile if your site uses
Sendmail, because (stock) Sendmail will always add a Message-Id if one
is missing. Other MTA:s (among them Qmail, I hear) act more sensibly,
and leave the headers alone on incoming mail.
Hope this helps,
/* era */
--
Paparazzi of the Net: No matter what you do to protect your privacy,
they'll hunt you down and spam you. <http://www.iki.fi/~era/spam/>
------------------------------------------------------------------------
Subject: Re: Verify Mail Has Valid 'From:' Field?
Date: 13 Jan 1998 10:36:50 +0200
From: <jari(_dot_)aalto(_at_)poboxes(_dot_)com>
To: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Mon 98-01-12 "Mark A. Matthews" <markm(_at_)XMission(_dot_)com> list.procmail
| jari(_dot_)aalto(_at_)ntc(_dot_)nokia(_dot_)com writes:
| >b) It takes lot of time for _each_ mail if you try to do even nslookup,
| > the call may block for several seconds.
|
| However, if the message is destined for something like a closed mailing
| list which is going to attempt to reply to the message anyway, the cost of
| validating the address at the filter stage is cheaper
I agree that there may be cases when it makes sense to use nslookup,
but I wouldn't running it for every message I receive. I already have
in my Emacs Gnus package called TinyGnus, which handles the UBE complaints
for the postmasters by running nslookup for every parsed received field ip
address.
What I have learned (and I love perl), is that do not use perl with procmail
if you can do things with less effort. Just check the OK flag for the
nslookup results. Could someone post their nslookup results to me or
to this group so that I could see how much differencies are there.
I have HP 9 and 10 here.
Can I rely on the regexp used in my recipe to check nslookup?
nslookup always seem to return exitcode 0 regadrless of failure or
success.
jari
% nslookup -querytype=MX geocities.com
Name Server: zeus.tele.nokia.fi
Address: 131.228.134.50
Non-authoritative answer:
geocities.com preference = 0, mail exchanger = mail.geocities.com
Authoritative answers can be found from:
com nameserver = H.ROOT-SERVERS.NET
% nslookup uta.fi
Name Server: zeus.tele.nokia.fi
Address: 131.228.134.50
Non-authoritative answer:
Name: uta.fi
Address: 153.1.1.12
% nslookup foo.com
Name Server: zeus.tele.nokia.fi
Address: 131.228.134.50
Name: foo.com
Address: 209.54.94.60
% nslookup foo.bar.com
pegasus txt nslookup foo.bar.com
Name Server: zeus.tele.nokia.fi
Address: 131.228.134.50
*** No address information is available for "foo.bar.com"
NSLOOKUP = "/usr/bin/nslookup -querytype=MX"
ADDR = `formail -rt`
OK = "no"
:0
* ADDR ?? @\/.*
{
ADDR = $MATCH
STAT = `$NSLOOKUP $ADDR`
# If nslookup succeeds it returns
#
# Non-authoritative answer:
# Name: uta.fi
#
# Or
#
# Non-authoritative answer:
# geocities.com preference = 0, mail exchanger =
mail.geocities.com
#
:0
*$ STAT ?? answer:($)(Name:|$ADDR)|(Name:.*$ADDR)
{ OK = "yes" }
}
:0
* OK ?? no
{
# nslookup failed, whatever the reason might have been
# Name server down?
}
------------------------------------------------------------------------
Subject: Re: C/Perl modules to delete attachments ?
Date: 13 Jan 1998 10:52:28 +0200
From: <jari(_dot_)aalto(_at_)poboxes(_dot_)com>
To: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Mon 98-01-12 Vikas Agnihotri <VikasA(_at_)att(_dot_)com> list.procmail
| Arent there any utilities out there in C/Perl that anyone knows about that
| be easily plugged into Procmail to do the kind of things we are talking
| about? I find that quite unreal being that this is such a common/expected
| request! (sigh)
I think perl CPAN will have MIME tools that let you rip any part of
the message out. I was trained by perl 4, and I haven't have the time
to learn all perl 5 modules and OO features. Best, if you send your
query to the perl newsgroup.
Still, I'd avoid perl if possible with procmail, because it's sooooo
_heavy_. In my opinion we can do simple things with procmail: the
MIME killer recipe is a lightweight compared to any real mime parser
and I tend to think that any heavy tasks which take considerable
amount of effort or time should be left outside of procmail. Like that
your MUA should take care of the message contents: MIME or PGP.
But each of one's own. Maybe I'm just over protective about the load
the procmail may cause if I apply all fancy features for each message.
:-)
------------------------------------------------------------------------
Subject: Re: Verify Mail Has Valid 'From:' Field?
Date: Tue, 13 Jan 1998 11:39:32 +0200 (EET)
From: era eriksson <era(_at_)iki(_dot_)fi>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
On 13 Jan 1998 10:36:50 +0200, <jari(_dot_)aalto(_at_)poboxes(_dot_)com>
wrote:
> nslookup results. Could someone post their nslookup results to me or
> to this group so that I could see how much differencies are there.
An alternative would be to use host(1), which does return a meaningful
error code. (I believe it's shipped with BIND. It's not a standard
program, though.)
/* era */
--
Paparazzi of the Net: No matter what you do to protect your privacy,
they'll hunt you down and spam you. <http://www.iki.fi/~era/spam/>
------------------------------------------------------------------------
Subject: Re: PROCESS THE MAIL - TO SCRIPT
Date: 13 Jan 1998 13:56:08 +0200
From: <jari(_dot_)aalto(_at_)poboxes(_dot_)com>
To: <procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de>
Mon 98-01-12 "Randy A. Katz" <randyk(_at_)ccsales(_dot_)com> list.procmail
|
| :0
| | someperlscript.pl
If I just run something as a side effect, I usually write:
dummy = `someperlscript.pl` # Give the message to perl
| ...correct syntax to use inside the PERL script to receive that PIPE?
Nothing magical, just reading from STDIN as you would do:
while ( <> ) { ... }
jari
------------------------------------------------------------------------
Subject: Re: Verify Mail Has Valid 'From:' Field?
Date: Tue, 13 Jan 1998 16:22:04 +0200
From: jari(_dot_)aalto(_at_)poboxes(_dot_)com
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Tue 98-01-13 era eriksson <era(_at_)iki(_dot_)fi> list.procmail
|
| An alternative would be to use host(1), which does return a meaningful
| error code. (I believe it's shipped with BIND. It's not a standard
| program, though.)
host(1) seems to be fast when the host exists, but if it doesn't, as is
the case in forged domains, ...yikes! 11 seconds per message.
% time host foo.bar.com (not exist)
--> 0.00u 0.03s 0:11.82 0.2%
% time nslookup foo.bar.com
--> 0.01u 0.03s 0:04.06 0.9%
% time host geocities.com (does exist)
0.00u 0.05s 0:00.08 62.5%
% time nslookup geocities.com
--> 0.02u 0.03s 0:00.07 71.4%
jari
------------------------------------------------------------------------
Subject: Verstaendnisproblem
Date: Tue, 13 Jan 1998 15:22:02 +0100
From: Stefan Wintermeyer <sw(_at_)swr(_dot_)de>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Hi,
ich habe folgendes .procmailrc
---cut---
PATH=/bin:/usr/bin
MAILDIR=$HOME/Mail
DEFAULT=$MAILDIR/mbox
LOGFILE=$MAILDIR/from
SHELL=/bin/sh # for other shells, this might need adjustment
# Ein allgemeines Backup von den letzten 500 E-Mails wird erstellt
:0 c
backup
:0 ic
| cd backup && rm -f dummy `ls -t msg.* | sed -e 1,500d`
# Der Rest geht ganz normal an mich.
:0
! -oi -f "$@"
---cut---
Das Backup der e-mail funktioniert sehr gut, aber die e-mail kommt nie
in meiner normalen e-mail an. Die letzte Zeile habe ich einfach aus den
MAN Pages kopiert ohne zu verstehen, was sie bewirkt (bitte keine
bloeden Kommentare). In den MAN Pages stand, dass die e-mail dann ganz
normal an den Benutzter weitergeleitet wird.
Was mache ich falsch? Danke!
--
Stefan Wintermeyer
SWR Reisedienst GmbH
Tel. +49 2631 9600 http://www.swr.de
Fax +49 2631 960-111 mailto:info(_at_)swr(_dot_)de
------------------------------------------------------------------------
Subject: Re: Verify Mail Has Valid 'From:' Field?
Date: Tue, 13 Jan 1998 16:16:02 +0200
From: jari(_dot_)aalto(_at_)poboxes(_dot_)com
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
98-01-13 <jari(_dot_)aalto(_at_)poboxes(_dot_)com> list.procmail
| Mon 98-01-12 "Mark A. Matthews" <markm(_at_)XMission(_dot_)com>
list.procmail
Autch,
| ADDR = `formail -rt`
This shoud have been
ADDR = `formail -rt -X To:`
naturally.
jari
------------------------------------------------------------------------
Subject: '[Resent-]Sender:' headers
Date: Tue, 13 Jan 1998 15:20:52 +0100 (MET)
From: palme(_at_)uni-wuppertal(_dot_)de (Hubert Palme)
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
CC: Hubert Palme <palme(_at_)rz(_dot_)uni-wuppertal(_dot_)de>
Hello,
I suspect procmail of inserting 'Resent-Sender:' resp. 'Sender:'
headers (with an incorrect address in my case) when processing
'! anyone(_at_)anywere(_dot_)de' recipes.
If true: How can I avoid this?
Thanks for any idea!
--
======================================================================
Hubert Palme Bergische Universitaet-Gesamthochschule Wuppertal
Computing Center
D-42097 Wuppertal
Email: palme(_at_)uni-wuppertal(_dot_)de (Germany)
http://www.hrz.uni-wuppertal.de/hrz/personen/h.palme.html
------------------------------------------------------------------------
Subject: Re: empty message id
Date: Tue, 13 Jan 1998 13:00:04 -0600 (CST)
From: "Christopher P. Lindsey" <lindsey(_at_)mallorn(_dot_)com>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Checking for no Message-Id at all is futile if your site uses
Sendmail, because (stock) Sendmail will always add a Message-Id if one
is missing. Other MTA:s (among them Qmail, I hear) act more sensibly,
and leave the headers alone on incoming mail.
I suppose one could check and see if the Message-Id was created at
the local site, then compare the From_ address with a set of known
domains. This could stand some cleaning up, but it's kind of
spontaneous:
FROM=`formail -xFrom: | fgrep -i -f /etc/mail/FromOK`
:0 c:
* ^Message-Id:.*domain\.com>$
* ^From [^(_at_)]+@[^ ]+
* !FROM ?? .
/scratch/spam
pull out From: header, check against file of ok domains
check if your domain name is in the Message-Id:
make sure the address has an @ (otherwise could be local)
did our earlier check agains valid domains fail? If so,
IT MIGHT BE SPAM.
Paparazzi of the Net: No matter what you do to protect your privacy,
they'll hunt you down and spam you. <http://www.iki.fi/~era/spam/>
Ain't that the truth. :(
Chris
------------------------------------------------------------------------
Subject: Advertisement: Website Hosting
Date: Mon, 12 Jan 1998 09:43:32 -0500
From: info(_at_)inexchange(_dot_)net (Info Desk)
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
-----------------------------------------------------------------------------
If you wish to be excluded from any future mailings,
reply with "remove" in the subject header.
-----------------------------------------------------------------------------
http://www.inexchange.net
InExchange would like to introduce our complete Hosting and Promotional
service.
FOR ONLY $29.95 PER MONTH !
* 30 MB (megabytes) of disk space
* 1000 MB = 1 GB (gigabyte) of data transfer per month
* 8 E-mail accounts
* INTERNATIONAL Hosting
* Access to your account anytime via the Web Control Panel
* Full MS Front Page support
* Unlimited FTP updates
* Personal CGI directory for your own scripts (or use ours)
* Comprehensive statistics program shows you everything
* E-mail forwarding, auto responders and vacation reply
* Domain name registration (www.yourname.com)
* FREE registration of your domain with over 250 search engines
* Friendly customer support
* Inquire about our $24.95 plan
* Other plans also available
If for any reason you are not satisfied with InExchange's service after 30
days, we will transfer you back to your original host and pay any transfer
fees.
http://www.inexchange.net
info(_at_)inexchange(_dot_)net
------------------------------------------------------------------------
Subject: Re: '[Resent-]Sender:' headers
Date: Tue, 13 Jan 1998 14:43:19 -0600
From: Philip Guenther <guenther(_at_)gac(_dot_)edu>
To: palme(_at_)uni-wuppertal(_dot_)de (Hubert Palme)
CC: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
palme(_at_)uni-wuppertal(_dot_)de (Hubert Palme) writes:
I suspect procmail of inserting 'Resent-Sender:' resp. 'Sender:'
headers (with an incorrect address in my case) when processing
'! anyone(_at_)anywere(_dot_)de' recipes.
If true: How can I avoid this?
Procmail doesn't, your sendmail (or sendmail-lookalike) may be doing
so. I've never heard of sendmail doing this, so I would suspect that
either sendmail was hacked to do this locally, or it's not really
sendmail but rather smail or something like that. Your local sysadmins
may be able to tell you whether or not this can be disabled. You can
confirm this is the situation by doing something like:
(echo ""; echo "kjdfaskjfd") | /usr/lib/sendmail
palme(_at_)uni-wuppertal(_dot_)de
then examine the headers on the message you get. If there's a Sender:
header, then it's the MTAs fault (and it's broken).
The only workaround I can think of, otherwise, would be to generate a
correct Sender: header before feeding messages into sendmail. Try
replacing
! some(_at_)addresses(_dot_)here
with
| formail -I"Sender: palme(_at_)uni-wuppertal(_dot_)de" | \
$SENDMAIL $SENDMAILFLAGS
some(_at_)addresses(_dot_)here
Philip Guenther
------------------------------------------------------------------------
Subject: Re: Juno/hotmail/prodigy filtering
Date: Tue, 13 Jan 1998 15:13:14 -0600 (CST)
From: dattier(_at_)wwa(_dot_)com (David W. Tamkin)
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de (Procmail Mailing
List)
Jari Aalto quoted W. Wesley Groleau from a post of Wesley's that I don't
remember:
| | :0
| | * ^From.*$FORGED_DOMAIN
| | * ! ^Received.*$FORGED_DOMAIN
| | * ! ^X-Loop: noloops_<personalized_unique_string>
| | $SPAMFOLDER
| |
| | :0
| | * ^Received.*$FORGED_DOMAIN
| | * ! ^From.*$FORGED_DOMAIN
| | * ! ^X-Loop: noloops_<personalized_unique_string>
| | $SPAMFOLDER
Whatever the goal there was, I'm sure that $FORGED_DOMAIN is supposed to
be a variable that needs substitution, not the static string
"<newline>FORGED<underscore>DOMAIN". Therefore the ^From and ^Received
conditions need the "$" modifier:
:0
* ! ^X-Loop: noloops_<personalized_unique_string>
{
:0: # if you care about a lockfile on $SPAMFOLDER
* $ ^From.*$FORGED_DOMAIN
* $ ! ^Received.*$FORGED_DOMAIN
$SPAMFOLDER
:0:
* $ ^Received.*$FORGED_DOMAIN
* $ ! ^From.*$FORGED_DOMAIN
$SPAMFOLDER
}
------------------------------------------------------------------------
Subject: Re: Getting files
Date: Tue, 13 Jan 1998 15:19:29 -0600 (CST)
From: dattier(_at_)wwa(_dot_)com (David W. Tamkin)
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de (Procmail Mailing
List)
Era Eriksson wrote,
| Jari's pm-tips contains a trick for canonicalizing case in variable
| matches, originally due to David Tamkin. It's a nice trick, but it
| requires you to have a list of all requestable files in the recipe.
That's because it wasn't intended for requestable files but rather for
a single user's mailing list subscriptions; the advantage of the trick
was that it worked within procmail instead of running a shell and tr.
To honor case-insensitive requests for files from a large library, it
doesn't pay to adapt that trick and to have to keep changing the list
for the recipe every time you add a file. Use tr as Era suggested,
FILE=`echo "$MATCH" | tr A-Z a-z`
or better yet, use it only if it is needed:
:0Di
* MATCH ?? [A-Z]
FILE=| echo "$MATCH" | tr A-Z a-z
------------------------------------------------------------------------
Subject: Re: '[Resent-]Sender:' headers
Date: Tue, 13 Jan 1998 15:25:37 -0600 (CST)
From: dattier(_at_)wwa(_dot_)com (David W. Tamkin)
To: palme(_at_)uni-wuppertal(_dot_)de (Hubert Palme)
CC: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Hubert Palme wrote,
| I suspect procmail of inserting 'Resent-Sender:' resp. 'Sender:'
| headers (with an incorrect address in my case) when processing
| '! anyone(_at_)anywere(_dot_)de' recipes.
|
| If true: How can I avoid this?
Procmail doesn't add them: your MTA does. If there is any Resent- header
present, the MTA has to add the rest of those that are required on mail
with Resent- headers, including Resent-Sender:.
If they create a problem, defuse them before the MTA sees them.
:0
* conditions
| formail -i Resent- | $SENDMAIL -oi anyone(_at_)anywhere(_dot_)de
------------------------------------------------------------------------
Subject: Re: empty message id
Date: Tue, 13 Jan 1998 17:42:57 -0500 (EST)
From: Rik Kabel <rik(_at_)netcom(_dot_)com>
To: lindsey(_at_)mallorn(_dot_)com (Christopher P. Lindsey)
CC: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de (procmail list)
Chris,
Have you tried your method on the procmail list? The message-id for
list mail is <"quoted string"@campino>, and the only other place that
campino appears is as a host name in a received header.
The message-id needs to uniquely identify a specific message within a
domain (although some mailers recently cited produce constant strings
which do not accomplish this). In particular, it does not need to
identify the domain.
A message-id does need to follow the format "<" + "local part" + "@" +
"domain part + ">". There is a lot of variation allowed within that.
The local part can include quoted strings with spaces and other strange
characters. The domain part contains one or more sub-domains. A
sub-domain may be a domain reference or a domain literal. White space,
including quoted CRs, is allowed all over.
If you want to be thorough, you will have to build a parser. If you can
settle for "almost there," try Era's recipe or mine (below) or have at
it yourself.
## Note: this recipe must be modified before use. Each '\t' should be
## converted to a tab.
## MID is the message-id, previously extracted. LF is a newline.
:0 ## attempt "<"word *("." word) "@" sub-domain *("." sub-domain)">"
* ! MID ?? ^^<([^][()<>,;:\" \t]+(\.[^][()<>,;:\" \t]+)*|\"[^"]+\")\
@((\[.*\]|[^][()<>,;:\" \t]+)(\.(\[.*\]|[^][()<>,;:\" \t]+))*\
)>[ \t]*^^
{ LOG="Message-id probably violates RFS822$LF $MID$LF" }
--
Rik Kabel Old enough to be an adult
rik(_at_)netcom(_dot_)com
------------------------------------------------------------------------
Subject: Re: empty message id
Date: Tue, 13 Jan 1998 17:19:18 -0600 (CST)
From: "Christopher P. Lindsey" <lindsey(_at_)mallorn(_dot_)com>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Have you tried your method on the procmail list? The message-id for
list mail is <"quoted string"@campino>, and the only other place that
campino appears is as a host name in a received header.
I plugged it in this morning to see what I could catch, but nothing
has shown up yet except for a few false matches. With a little more
fine-tuning it will probably work fine for my site, but I don't
know how extensible it is.
I use this recipe to check Messsage-Id: headers:
#Incorrect or failed Message-Ids:
:0:
* !^Message-Id:.*<[^<>@]+(_at_)[^<>]+>
/scratch/spam
but I still have problems with <"text<132125(_at_)adfa>"@domain.com> -- the
quoted @ and <> get me. I'll have to look at yours more closely...
Chris
------------------------------------------------------------------------
Subject: Re: Juno/hotmail/prodigy filtering
Date: Tue, 13 Jan 1998 18:28:37 -0500 (EST)
From: Rik Kabel <rik(_at_)netcom(_dot_)com>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de (procmail list)
David wrote:
Jari Aalto quoted W. Wesley Groleau from a post of Wesley's that I don't
remember:
| | :0
| | * ^From.*$FORGED_DOMAIN
| | * ! ^Received.*$FORGED_DOMAIN
| | * ! ^X-Loop: noloops_<personalized_unique_string>
| | $SPAMFOLDER
| |
| | :0
| | * ^Received.*$FORGED_DOMAIN
| | * ! ^From.*$FORGED_DOMAIN
| | * ! ^X-Loop: noloops_<personalized_unique_string>
| | $SPAMFOLDER
Whatever the goal there was, I'm sure that $FORGED_DOMAIN is supposed to
be a variable that needs substitution, not the static string
"<newline>FORGED<underscore>DOMAIN". Therefore the ^From and ^Received
conditions need the "$" modifier:
:0
* ! ^X-Loop: noloops_<personalized_unique_string>
{
:0: # if you care about a lockfile on $SPAMFOLDER
* $ ^From.*$FORGED_DOMAIN
* $ ! ^Received.*$FORGED_DOMAIN
$SPAMFOLDER
:0:
* $ ^Received.*$FORGED_DOMAIN
* $ ! ^From.*$FORGED_DOMAIN
$SPAMFOLDER
}
And if FORGED_DOMAIN is a list of domains, such as
((aol|juno|(hot|rocket)mail).\com|usa\.net) then you probably want to
do a match. (You may also want to check Reply-To: headers, and maybe
To: and Cc: as well, when you test From headers.) I get a few hits on
the first ordering below. I haven't ever had a hit on the second. Maybe
in time....
:0
* ! ^X-Loop: noloops_<personalized_unique_string>
{
:0: # if you care about a lockfile on $SPAMFOLDER
* $ ^From.*\/$FORGED_DOMAIN
* $ ! ^Received.*$\MATCH
$SPAMFOLDER
:0:
* $ ^Received.*\/$FORGED_DOMAIN
* $ ! ^From.*$\MATCH
$SPAMFOLDER
}
--
Rik Kabel Old enough to be an adult
rik(_at_)netcom(_dot_)com
------------------------------------------------------------------------
Subject: Deferred delivery to a pager
Date: Tue, 13 Jan 1998 15:57:22 -0800
From: Mike <Mike(_at_)innosoft(_dot_)com>
To: procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
Hi
I recall recently reading (on a FAQ, I think) a method of having
procmail forward a message to a pager, if the current time was in
between two limits. I've searched most of the FAQs, without success;
does anybody recall which FAQ or where it may be?
Thanks
Mike
--
Mike de Laine Technical Support, Innosoft International, Inc.
"Each success only buys an admission ticket
to a more difficult problem" - HAK
------------------------------------------------------------------------
Subject: Re: Junk mail via the Smartlist list
Date: Tue, 13 Jan 1998 21:25:13 -0700 (MST)
From: "Rhett 'Jonzy' Jones" <jonzy(_at_)cc(_dot_)utah(_dot_)edu>
To: wr(_at_)tribe(_dot_)ping(_dot_)de
CC: Rob Lingelbach <rob(_at_)alegria(_dot_)com>, BillLee(_at_)cleaf(_dot_)com,
SmartList(_at_)informatik(_dot_)rwth-aachen(_dot_)de,
Procmail(_at_)informatik(_dot_)rwth-aachen(_dot_)de
On Wed, 14 Jan 1998 wr(_at_)tribe(_dot_)ping(_dot_)de wrote:
On Tue, Jan 13, 1998 at 11:16:57AM -0800, schrieb Rob Lingelbach:
I agree, and also propose postings from known UCE/SPAM sites
be denied. I currently have a list/script which filters some
2858 domains and 1363 users.
But I agree that it's paradoxical the SmartList mailinglist can't
control its own output at even the minimal level of foreign_submit =
no.
I am wondering why I never heard any comments from the Smartlist/Procmail
list maintainer. Or isn't there a maintainer?
Okay folks, I have had it with all the UCE/SPAM coming through
the current Procmail/SmartList mailing lists, so ....
I have just created two new mailing lists, which are Procmail/SmartList
supported, along with my modifications to prevent UCE/SPAM. These
mailing lists are called:
smartlist(_at_)lists(_dot_)utah(_dot_)edu
procmail(_at_)lists(_dot_)utah(_dot_)edu
To subscribe to these mailing lists send the Subject: subscribe
to:
smartlist-request(_at_)lists(_dot_)utah(_dot_)edu
procmail-request(_at_)lists(_dot_)utah(_dot_)edu
NOTE - You will not be able to post to these mailing until your
address has been verified. Furthermore, you will NOT
be able to subscribe to either one of these mailing lists
if your domain is one of the 2850+ domain which I deny
both subscription and postings from.
Please be aware some UCE/SPAM might slip through, but I assure
you steps will be taken to prevent future postings from that
user and possibly the entire domain.
Neither of these lists are currently available in digest form.
However, if you want them available in digest form, please
send your request to the appropriate
-request(_at_)lists(_dot_)utah(_dot_)edu
address.
----------------------------------------------------------------
Rhett 'Jonzy' Jones | jonzy(_at_)cc(_dot_)utah(_dot_)edu
SysAdmin, postmaster, Gopher, PH, ... | (801) 581-8810
----------------------------------------------------------------