Mike wrote:
> James Newton wrote:
> > Since there doesn't seem to be a clear link between the email client and
> > this problem (some people with the same version of the program have the
> > problem and others don't) and since it started a few weeks ago, and is not
> > consistent, I'm guessing its an ISP / server routing issue. That being the
> > case, it might help if we had headers from each person affected, one from a
> > message that had the problem and one from a message that doesn't.
>
> Same thing I would have asked for.  Or even just for the folks having this
> problem to look and see if the offending messages have any sort of pattern
> to them - perhaps all of the problem messages are coming from a certain
> group of senders.  Like perhaps a particular ISP's outgoing mail server is
> going a bit wacked.
>
> If any of the folks having this trouble can identify some of the messages
> that were causing this trouble, let me know a few of them - off list
> preferably - and I'll take a look at the message here and see if I can find
> anything odd.  To pin down the message, the best info for me would probably
> be the sender, the date / time stamp, and the subject line.
>
> Another thing I'd like to ask is about the error message mentioned.  Does
> this message come from Eudora?  Or is it coming from the server that Eudora
> is getting the mail from?

Been thinking on this;  Same idea here - Nothing much to contribute,
seems like a path-created problem?  So scanning paths in the headers of
many GOOD and BAD messages is probably THE way to figure this one out...

  Mark

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.