--- Charlie Summers wrote:
..
> ratio), I'd suggest instead of pointing us to a website archive that
> can't possibly be of any help whatsoever, you show us in
> PLAIN TEXT (no HTML) the complete original header fields
> from a submitted message (a simple procmail recipe at the
> head of rc.local.s00 to write a copy of all submitted
> email to an external mbox should be sufficient), and
> the SmartList-distributed header fields from that same message.
Thanks for this idea, Charlie. I have added a recipe to rc.local.s00 to
save a copy of the message.
I have also disabled a recipe that was handling uuencoded messages. It
probably didn't matter but I will see if it makes a difference.
As you said, I will probably figure out the problem by examining and
'before' and the 'after' messages. If not, I will post the headers (or
links to them) to the list.
Thanks,
- Harshal
__________________________________
Do you Yahoo!?
Make Yahoo! your home page
http://www.yahoo.com/r/hs
Hi,
I have some members on a Smartlist mailing list that send emails with
UTF-8 characters in them. These emails are base64 encoded which seems
to trip Smartlist. If the messages go through Smartlist, the list gets
only the encoded email. It seems that some header or something is
stripped out and the mail clients cannot automatically decode the
email. If the email is sent directly, the mail clients can auto-decode
the message and display it correctly. Look at
http://www.mumbai-central.com/nukkad/may2005/msg00107.html to see an
example of a mangled email.
Has anyone seen this behavior? How do I get Smartlist to play nice with
base64 encoded emails?
Thanks,
- Harshal
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
