<p>That's irritating for my clients - isn't it? Should be fixed! Most people are not IT-specialists. They need simple, clear answers - even by maiser! </p><p>Mercury/NLM didn't have that bug! Errormails have been FROM maiser and with informative text. </p><p>bye   Olaf</p><p> </p>

<p>Have some mailinglists on Mercury/32 V4.73.</p><p>Somebody tried to unsubscribe from a mailinglist while he is not subscribed at the list. Syntax is korrekt (it's a webform with script) - nevertheless checked that with one of my addresses: </p><blockquote><p>subscribe list   -> OK unsubscribe list  -> OK unsubscribe list  -> errormessage to postmaster and FROM </p></blockquote><p> Have a look at the errormessage to FROM:</p><blockquote><p>With reference to your message with the subject:    "unsubscribe LISTE" The local mail transport system has reported the following problems it encountered while trying to deliver your message: ------------------------------------------------------------------- *** <maiser@domain.de> <maiser@domain.de> Not a current subscriber. ------------------------------------------------------------------- Your mail message is being returned to you in the next part of this message. Should you need assistance, please mail postmaster@domain.de.  </p></blockquote><p> Nearly the same to Postmaster:</p><blockquote><p>The attached message has failed delivery and has been referred to you as postmaster. The following error report or reports were given to explain the problem:    *** <maiser@domain.de>    <maiser@domain.de>    Not a current subscriber. </p></blockquote><p>For shure the only appearance of "maiser@domain.de" is in the TO-Field of unsubscribe-mail. I had expected an errormessage where used mailaddress in FROM of unsubscribe-mail and listname is reported (if there were no subject in unsubscribe-mail, there were no hint on that). Example:</p><blockquote><p>    *** <maiser@domain.de> says:    <somebody@domain.anywhere>    Not a current subscriber of list LISTNAME. </p></blockquote><p>Is it a bug or is something misconfigured? </p><p>bye   Olaf</p><p> </p>

<p>Mercury uses a standard template for nondelivery notifications, and in some circumstances the information contained in it may not be what would be the best in that special case. A message generated by the list server (maiser) itself would presumably be more informative, but this was actually a failed delivery message created by Mercury core. As the sender wan't a list member the unsubscribe request was refused by maiser and handled by Mercury core as any other failed delivery.</p><p>/Rolf </p>