procmail
[Top] [All Lists]

Re: Suppressing processing of UU/BASE64 encoded attachments

1998-07-19 20:27:58
My 02...

        I run a mailing list. And I have literally done everything that
I possibly can to insure that the list remains completely voluntary. The
only avenue I have ever used for promoting the list is via a web site
through which anyone can easy subscribe or unsubcribe to the list with the
knowledge that their information will not be used for any other purpse.
I've gone so far as to refuse to add anyone to the list who does not
actually subscribe via the online form - and that includes those who have
trouble using the form.

        All of that is simply to insure that no one receives my mailings
except those who really want them.

        In two years of running the list I have not received one single
complaint regarding an unsolicited reception of my mailings. And yet many
of our subscribers have trouble recieving the mailings as their ISP's spam
filters seem to be eating them.

        My style of writing is rather flamboyant... I tend to use lots of
!!! and ... and CAPS. And so there is no one to blame but my self. At the
very same time however, as someone who does not spam, but who manages a
high quality mailing list, I personally have a bit of a problem with
this kind of stuff...

        Brent Sims 

        

On Sun, 19 Jul 1998, John D. Hardin wrote:

It would be nice if there was a way to tell procmail to process the body
of the message, skipping over the encoded portions of any encoded
attachments (i.e. the UUE or base64 sections).

Some of my rules for spam trapping (such as, for example, three or more
exclamation points in a row) have hit in the body of an encoded
attachment, bouncing an otherwise-acceptable piece of mail. 

Does this capability currently exist? If not, is it planned? Does anybody
have any arguments against implementing this restriction on body
processing?

I searched the archives briefly but couldn't find anything addressing this
idea - the hits on "base64" and/or "uuencode" were on questions about how
to have procmail do the bursting.

--
 John Hardin KA7OHZ                               
jhardin(_at_)wolfenet(_dot_)com
 pgpk -a finger://gonzo.wolfenet.com/jhardin    PGP key ID: 0x41EA94F5
 PGP key fingerprint: A3 0C 5B C2 EF 0D 2C E5  E9 BF C8 33 A7 A9 CE 76 
-----------------------------------------------------------------------
  Your mouse has moved. Windows NT must be restarted for the change
  to take effect. Reboot now?  [ OK ]
-----------------------------------------------------------------------
   Today: Thirdspace