Other mail software
and specially designed bounces
from ISPs


There is other mail delivery software that is becoming more widely used, eg. QMAIL, and the error messages explanations for that are still in their infancy.  There is also a number of ISPs who have developed their own error messages and as these come attention we will add these too (you can help with this by bringing them to our notice).

Some ISPs have redesigned their error messages so they are more reader friendly (well they are meant to be anyway).  Note that sometimes due to their ministrations the SmartList software of RootsWeb cannot fathom to whom the returned mail was originally sent, so they will not be auto-unsubscribed. Here list admins will need to do some of their own investigation and manually have to fix up such problems.  As examples of some of these come to hand we will be adding examples.

QMAIL problems


Specials


Qmail
From:      MAILER-DAEMON@enterprise.powerup.com.au

To: <GENANZ-L-request@rootsweb.com> 
Subject: failure notice
Hi. This is the qmail-send program at enterprise.powerup.com.au. I'm afraid I wasn't able to deliver your message to
the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.
<electricity@powerup.com.au>:
Sorry, no mailbox here by that name. (#5.1.1)
A number of options here, either the address is wrong and the account does not exist, the account has expired and does not exist, or they have internal problems and their servers are not talking to each other. Note that there are other responses and interpretations of Qmail errors following.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES, otherwise you may wish to see if it resolves itself.

Tim the Guru says:- This isn't a customized response.  It's the stock response from the `qmail'system, which is an increasingly popular alternative to the `sendmail'Unix mail server software.

Does SmartList have problems with this format? I've never noticed it, but if folks have ongoing difficulty with this bounce format, I can try to do something to fix it.

As this software becomes more popular there will be an increase in the number of different error messages that are unique to Qmail, as people come across new error messages they should be posted (annotated) to the Webmaster so that they can be added to this list. Here are some further errors that have been submitted.

This account has been disabled
- Exactly that, the account is disabled.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES, otherwise you may wish to see if it resolves itself.



Specials
From:      Mailer-Daemon@chemek.cc.or.us

To: <BIRD-L-request@rootsweb.com>
Subject: Message status - opened
The message that you sent was opened by the following:
joe.bloggs
--------------------Information about your message--------------------
Subject: Re: Testing

Here good old
joe.bloggshas got a special setting on his email software that replies to the sender (in this case the mailing list) notifying them that he has read their mail.  Very soon this person is unsubscribed due to bounces.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES

Mail System Error - Returned Mail    (three examples)

To:       <RIGENWEB-L-request@rootsweb.com>

From: Mail Administrator <Postmaster@postoffice.bellatlantic.net>
Subject: Mail System Error - Returned Mail
This Message was undeliverable due to the following reason:
Your message was not delivered because the DNS records for the destination computer could not be found.
Carefully check that the address was spelled correctly, and try sending it again if there were any mistakes. It is also possible that a network problem caused this situation, so if you are sure the address is correct you might want to try to send it again. If the problem continues, contact your friendly system administrator.

The following recipients did not receive your message:
<bunyip@bellatlantic.net>
Please reply to Postmaster@postoffice.bellatlantic.net if you feel this message to be in error.
The reasons here are just as they explained either a wrong address or they have internal configurations problems.  If it is a long term subscriber of yours then it is pretty surely the latter reason, if it is a new subscriber then it could be either.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES

And another example of a similar message

Subj:      Mail System Error - Returned Mail

From: Postmaster@worldnet.att.net (Mail Administrator)
Reply-to: Postmaster@worldnet.att.net (Mail Administrator)
This Message was undeliverable due to the following reason:
The user(s) account is disabled:
<freddo.frog@worldnet.att.net>
Please reply to Postmaster@worldnet.att.net if you feel this message to be in error.
--------------------
Received: from imo20.mx.aol.com ([198.81.17.42])
by mtiwgwc03.worldnet.att.net (Intermail v3.1 117 241) with ESMTP id <19980329130853.JYC28431@imo20.mx.aol.com>
[snipped]
This is supposedly a typical sort of error that you would get from AT&T.
To:         <GENANZ-L-request@rootsweb.com>

From: Mail Administrator <Postmaster@two.net.au%gt;
Subject: Mail System Error - Returned Mail
This Message was undeliverable due to the following reason:
A message was not delivered to one or more recipients because of the following reason(s):
Couldn't link message file: /var/spool/mailbox/godzilla/inbox/19980619050422.AAA.77299d25
Please reply to Postmaster@two.net.au if you feel this message to be in error.
Guess what? They have somehow broken their configuration and cannot deliver their mail internally.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES



Subject:   cc:Mail Link to SMTP Undeliverable Message

From: "bill & ben" <flower_pot_men@pb.com>
To: <RIGENWEB-L@rootsweb.com>
Message is undeliverable.
Reason: Too many file attachments.
Please send separate messages with less than 20 attachments.
Original text follows:---------------------[snipped]
Here a DIGEST has been received by an ISP whouses cc: Mail as their mail distributing software (more common for people receiving mail as employees of companies with internet access).  Unfortunately the ISP has got their software setup so as to reject anything with more than X attachments (in this case X=20).  The MIME digests (-D) that RootsWeb sends commonly have 20-30 messages in a full digest and they are seen as attachments by some software.

Do you remove them manually? Well YES and NO.  In this case there is no real way to remedy the problem so generally in this case it is better to unsubscribe the sender from the digest form (-D) and subscribe them to the list form (-L).  Usually with an explanatory note either before or after your actions of course.


From:       	<MAILER-DAEMON@new-kyoko.mpx.com.au>

To: GENANZ-D-request@rootsweb.com
Subject: mail failed, returning to sender
|------------------------- Failed addresses follow: ---------------------|
<pagep@rint.com.au> ... loop detection: maximum hop count exceeded
<sp@rint.com.au> ... loop detection: maximum hop count exceeded
|------------------------- Message text follows: ------------------------|

Another example of an error message where there is an internal configuration problem at the receiving ISP. They are basically looping there mail until it says ENOUGH, I cannot cope!. I am out of here! Hence the receiving server sends it back whence it came, to RootsWeb, then on to you. An interesting thing about this bounced message is that also demonstrates that there is a virtual domain in action here. The bouncing server (mpx.com.au) is reporting on the bounced mail of a virtual domain within that ISP (rint.com.au).

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES


To:        "SOOTH-L-request@rootsweb.com" <SOOTH-L-request@rootsweb.com>

From: MAILER-DAEMON@telcomplus.net
Subject: Message rejected by system
------------ Transcript of session follows ------------
Reason: User snorfok@telcomplus.com is unknown.
-----------------First 8192 bytes of-------------------
[snipped]

There a number of possibilities. They range through that the address existed, there is an internal problem, dah-di-dah. The full gamut of has been explained regularly, it is one of the regular causes just a different way to be expressed.

Do you remove them manually? If SmartList is not going to do it and it is a continuing problem, YES. What had happened in this case was that the email address had already been unsubscribed for whatever reason, and there had been a myriad of bounced posts afterwards. The list admin had missed the Removed: ... post and could not find the address on the list. This reinforces the need to be aware and think of all the eventualities.


From:      postmaster@postmaster

To: <RIGENWEB-L-request@rootsweb.com>
Subject: Nondeliverable mail
------Transcript of session follows -------
Connection to de-inc.com failed.
No Ip address found from odyssey.de-inc.com-207.22.16.7
King_kong@de-inc.com
Server received Winsock error Host not found.
Basically as previously stated, there is an internal configuration problem at the receiving ISP.  It may be temporary, it may not.

Do you remove them manually?  If SmartList is not going to do it, YES, as this problem is not necessarily going to resolve itself.
From:      postmaster@postmaster

To: <CHANNEL-ISLANDS-L-request>
Subject: Nondeliverable mail
------Transcript of session follows -------
w_churchill@cigarsmoker.co.uk
500 Host server does not support 8 bit mime
The ISP of the person receiving the mail does not accept MIME messages, in this day and age this is probably considered unusual, but hey we are only the slaves here. In list (-L) mode this message occurs when one of the subscribers decides to send their messages in MIME format which is generally discouraged anyway, or if in digest (-D) mode possibly for just getting the digest.

Do you remove them manually?  If they are in digest mode, YES, and subscribe them to list mode as the problem is going to be permanent (remember that digests get sent in MIME form). If they are in list mode then just leave it, as hopefully your list does not get many messages sent in MIME. It is probably worth you even sending an email to the sender of the MIME message, if you can identify them, asking them to just send mail in plain form, ie. NOT MIME.


Subject:   Delivery failure

From: postmaster@postoffice.microtech.com.au
To: <GENANZ-L-request@rootsweb.com>
Copies to: postmaster@postoffice.microtech.com.au
Your message has encountered delivery problems to old.macdonald@microtech.com.au.
Message file missing - message not delivered
Your message reads (in part):
Original message not available.
[I am running out of excuses by now <g>] There were problems somewhere along the delivery line so that only the header of the message has got through and not the body.  The receiving ISP has not liked what it has seen `curled its virtual lip' and sent it back to you. Now this is more likely to be either a `one-off' or temporary problem

Do you remove them manually? Well you could if it is not being registered but otherwise leave it and see if it resolves itself.



From:      PMDF e-Mail Interconnect <postmaster@muwayb.ucs.unimelb.edu.au>

Subject: Delivery Notification: Delivery has failed
To: GENANZ-L-request@rootsweb.com
Your message cannot be delivered to the following recipients:
Recipient address: redmond_barry@ariel.ucs.unimelb.edu.au
Original address: redmond_barry@ariel.its.unimelb.edu.au
Reason: Remote SMTP server has rejected address
Diagnostic code: smtp; 550 <redmond_barry@ariel.ucs.unimelb.edu.au>... User unknown

You never would guess here either, but there has been an internal configuration problem (just for something different) at the receiving ISP.

Do you remove them manually? Again. Well you could if it is not being registered but otherwise leave it and see if it resolves itself.



To:        <GENANZ-L-request@rootsweb.com>

Subject: Failed mail
From: NTMail <PostMaster@internet.blookau.govt.nz>
---------------------------------------------------------------------
Could not resolve the address "blookau.govt.nz"
Please check you have entered the email address correctly.
---------------------------------------------------------------------

This one is simple. They have got an internal configuration problem.

Do you remove them manually? Well you could, if it is not being registered, but otherwise leave it and see if it resolves itself.


From:        POSTMASTER@wallyland.com

To: <GENANZ-D-request@rootsweb.com>
Subject: Undeliverable message
------- Failure Reasons --------
MIME parse error: Multipart must specify boundary

You will ONLY see this message with a bounced digest post, with this being one of the few errors where the RootsWeb servers are at fault. What has happened, is that during the construction of the digest there has been a glitch (technical term <g>) and the MIME construction has not been proper. The receiving ISP has found the MIME problem and rejected the message.

Do you remove them manually? No, it is not necessary. Note: If your subscribers now go and retrieve this digest via email from the archives it will be retrieved successfully. This is because the archive server hides the MIME during delivery.



How can you help?

If you get an error message that is not listed, please forward the bounced message with annotations to the webmaster so that it can be added to this list.