On Monday 08 July 2002 13:11, Derrick 'dman' Hudson wrote:
> FYI, =20 is the quoted-printable encoding of a space character.
>
> If I was in your place, I would keep a copy of all mails (for a while)
> and next time you get a customer complaint, ask them what the
> Message-ID: header is (you'll be on the phone with them so you can
> walk them through it, as a one-time thing they'll never have to do on
> their own) so that you can inspect the raw message yourself. Then you
> can track down the source of the bad formatting.
As I was remarking to Bart Schaefer, I suspected that it had something to do
with an encoding of a space; because %20 is the URLencoding of a space. I'm
keeping a copy of all mails currently via a procmail recipe; for each user,
it copies the message to a file based on the username.
My procmail looks like this:
------------
ARCHIVEDIR=/var/mail/mail_archive
DATEDIR=`date +%Y/%m/%d`
SAVEAT=$ARCHIVEDIR/$DATEDIR/$LOGNAME
VERBOSE=yeah
SHELL=/bin/sh
:0
* ? test -d $ARCHIVEDIR/$DATEDIR || mkdir -p --mode=750 $ARCHIVEDIR/$DATEDIR
{ }
:0 c
$SAVEAT
:0fw
| spamc
-------------
The bad emails occurs in the archive files too.
-Russ
(And thanks for sticking with this, even though it's not a SA problem!)
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
