At 11:45 PM 4/14/02 -0800, Lee Ross wrote the following: >At 06:02 AM 4/10/02, you wrote: > >Hi Marlene and List, > >I think I've found Cyberspace! Tonight I received 3 messages like the one >I've copied below. I'm not real sure how to read all of the header but it >looks like my server was holding all of the messages and for some reason, >they were unable to deliver. Can anyone explain why this is happening. >Gerry suggested that my mime converter was possibly working intermittently. >Does that have anything to do with my server not delivering the message? > >Here is one of the three return messages and thanks for the help: > >Return-Path: <> >Received: from mta-2.gci.net ([208.138.130.83]) by snowy.gci.net > (Netscape Messaging Server 4.15 snowy Jan 17 2002 00:23:08) with > ESMTP id GULGIB01.RGC for <[EMAIL PROTECTED]>; Sun, 14 Apr 2002 > 21:27:47 -0800 >To: [EMAIL PROTECTED] >From: Mail Administrator <[EMAIL PROTECTED]> >Reply-To: Mail Administrator <[EMAIL PROTECTED]> >Subject: Mail System Error - Returned Mail >Date: Sun, 14 Apr 2002 21:27:46 -0800 >Message-Id: <[EMAIL PROTECTED]> >MIME-Version: 1.0 >Content-Type: multipart/report; report-type=delivery-status; > Boundary="===========================_ _= >4639282(16979+6076564)" > > >This Message was undeliverable due to the following reason: > >Your message was not delivered because the destination computer was >not reachable within the allowed queue period. The amount of time >a message is queued before it is returned depends on local configura- >tion parameters. > >Most likely there is a network problem that prevented delivery, but >it is also possible that the computer is turned off, or does not >have a mail system running right now. > >The queue containing messages destined for imagicomm.com >was expired by the Postmaster of mta-2.gci.net. >The following recipients did not receive your message: > <[EMAIL PROTECTED]> > >Please reply to <[EMAIL PROTECTED]> >if you feel this message to be in error. > > >Reporting-MTA: dns; mta-2.gci.net >Received-From-MTA:dns; mmp-1.gci.net (208.138.130.80) >Arrival-Date: Mon, 8 Apr 2002 09:39:05 -0800 > >Remote-Recipient: rfc822;<[EMAIL PROTECTED]> >Diagnostic-Code: smtp;447 SMTP-Deliver:QueuedTooLong >Action: failed >Status: 4.2.0 >Remote-MTA: DNS;imagicomm.com >Last-Attempt-Date: Sun, 14 Apr 2002 21:27:46 -0800 > > >Return-Path: <[EMAIL PROTECTED]> >Received: from mmp-1.gci.net ([208.138.130.80]) by mta-2.gci.net > (Netscape Messaging Server 4.15) with ESMTP id GU9FP502.BM8 for > <[EMAIL PROTECTED]>; Mon, 8 Apr 2002 09:39:05 -0800 >Received: from leeross.gci.net ([24.237.200.138]) by > mmp-1.gci.net (Netscape Messaging Server 4.15) with ESMTP id > GU9FP403.529 for <[EMAIL PROTECTED]>; Mon, 8 Apr 2002 >09:39:04 -0800 >Message-Id: <[EMAIL PROTECTED]> >X-Sender: [EMAIL PROTECTED] >X-Mailer: QUALCOMM Windows Eudora Version 5.1 >Date: Mon, 08 Apr 2002 09:39:16 -0800 >To: pcworks <[EMAIL PROTECTED]> >From: Lee Ross <[EMAIL PROTECTED]> >Subject: posting messages >Mime-Version: 1.0 >Content-Type: multipart/mixed; x-avg-checked=avg-ok-164547A4; >boundary="=======1A983AF9======="
[snip actual message and Marlene's reply] First off, this message itself has been demimed according to the headers: >X-Converted-To-Plain-Text: from multipart/mixed by demime 0.98b >X-Converted-To-Plain-Text: Alternative section used was text/plain You are still sending multipart messages, so please configure your Eudora to send plain text messages. See http://www.expita.com/nomime.html for instructions. Secondly, the original message sent probably caused multipart to be activated because of AVG. See the header above: > Content-Type: multipart/mixed; x-avg-checked=avg-ok-164547A4; Make sure you set AVG scanner to NOT insert special text at the end of your e-mail messages informing your mail recipients that your mail and its attachments are certified v*rus free by AVG. Now to answer the specific question of why the e-mail was delayed and returned. Sometimes a host (domain) cannot handle a message immediately. For example, it may be down or overloaded, causing it to refuse connections. The sending host is then expected to save this message in its mail queue and attempt to deliver it later. This is what your ISP (mta-2.gci.net) did or I should say this is what the mailer daemon did. It saved the messages (in a mail queue) to deliver later to pcworks. Under normal conditions the mail queue will be processed transparently after a series of retries that de-escalate in time. That is, the first of the retries may be every 5 minutes for the first hour, then every 30 minutes for remainder of that first day, then every hour on the second day, then once a day on days 3 through 5. All of these retry times are setup in the configuration of the mail delivery agent (MDA) or mailer daemon. Every ISP sets up their MDA to try to deliver mail. However, after some point the mailer daemon has to give up and "bounce" (return) the message back to the sender. Generally speaking, most mailer daemons will give up after 5 days and send a message back to the sender telling them of the problem. In this case, failure to deliver mail to pcworks after 5 days (Arrival-Date: Mon, 8 Apr 2002 09:39:05 -0800 through Last-Attempt-Date: Sun, 14 Apr 2002 21:27:46 -0800). Now we all know that PCworks (or I should say the mailer daemon at imagicomm.com) has not been down for 5 days. It may be down for weekly maintenance for several hours or some such but not for 5 solid days. Therefore, the problem lies elsewhere. Either the first time the message was bounced from pcworks back to gci.net in went to a queue that didn't have a retry or was a mis-configured queue or the message kept bouncing from PCworks. You can't tell from the bounce message. Marlene specifically indicated that she didn't see the message. Normally, improperly configured messages end up being held until she can fix or reject them. So I'd guess other possibilities. Because you have previously sent messages that had to be "demimed" then either the demine program didn't work in which case your message bounced back to gci.net and was held or the pcworks mailer was down when the message was bounced or you message bounced for some other reason and the queue at gci.net is incorrectly formed. I'd bet it was because the message had to be demimed and something occurred or occurs that cause the message to be re-queued back at gci.net and for some reason they never get delivered. So make sure you configure Eudora to sent plain text e-mail and make sure AVG doesn't have a footer added to your outgoing messages. -- Gerry Boyd ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
