On Mon, Apr 27, 2009 at 10:32 AM, Jim Hall <jh...@freedos.org> wrote: > On Mon, Apr 27, 2009 at 9:59 AM, Carl Spitzer <cw...@myrealbox.com> wrote: >> I do not know why the return path is munged in place of the real senders >> message. >> I would like to know if there is a corrective and if I can get an mbox >> version of the last few months messages to import to correct my archive. >> > > You & I exchanged emails about this just 2 days ago, so not sure why > you're asking again on the lists. I said I had submitted this as a > request to SourceForge about the list behavior: > > [sourceforge] #347: mail lists forwarding from "bounces" address? [...]
I can guess why Carl is getting these emails from "bounces". I think it's a reattempt. My email (above) on Apr 27 cc'd Carl directly ... and ever since I have been getting these messages indicating temporary failure: >>>> The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720 [smtp-in.myrealbox.com. (10): Connection timed out] [blade3.myrealbox.com. (20): Connection timed out] <<<< So if emails to myrealbox addresses are bouncing, I can see why an eventual delivery might come from a "bounces" handler at SF. Unless anyone else on the list is experiencing a similar problem, I'm going to assume this is caused by delivery failure at myrealbox's end. -jh ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
