>Hello fellow list-owners.
>
>I seem to have encountered a rather strange series of bounces from one
>subscriber's internet service provider.  I contacted them about a week ago
>and got a response at that time saying that they were going to fix the
>problem (something related to their servers refusing to relay among
>themselves as I gather that mail.gelnhausen.net and pop3.main-kinzig.net
>are from this same provider and are used as two seperate mail servers.
>
>Below, you will find my latest correspondance with this provider and also
>the error message which I have received from LISTSERV.  Does the
>suggestion I am being given here make any sense, and if it does, how do I
>tell LISTSERV to not capitalize the domain name by default if it is even
>possible to do that?

I've seen this before.  According to (I think) RFC822 domain names are not
case-sensitive, so their setup violates this standard.

There is no way that I am aware of to get LISTSERV to make the domain names
all lower-case, so until they fix their mailer they're out of luck.

-jwgh


>                                        Date:     16-Oct-1998 03:59am EDT
>                                        From:     Arne Kuhlmann
>                                                  [log in to unmask]
>                                        Dept:
>                                        Tel No:
>
>TO:  Glenn Alperin                        ( [log in to unmask] )
>
>
>Subject: Re: Please help me again.
>
>Hi,
>
>yes I thought we had the problem fixed...
>It seems to be a bug in the mail server.
>Can you please change the users's e-mail address from @POP3.MAIN-KINZIG.NET to
>@pop3.main-kinzig.net (lower case)??
>This should take care of the problem.
>
>Thanks,
>
>Arne Kuhlmann
>
>
>
>Glenn Alperin wrote:
>>
>> Hello there!
>>
>> I contacted you a few days ago to report a similar problem with your
>> server, and to date have had no further problems, but just today, I
>> received two such notices that relaying between mail.gelnhausen.net and
>> pop3.main-kinzig.net is not allowed.  As I discovered a few days ago when
>> I had e-mailed you at that point in time, I was informed that these two
>> servers should not have such difficulties with relaying to each other
>> since you are running both servers.  Please correct this problem again
>> when you have a spare moment as I have a subscriber to my list who is
>> probably wondering where his mail from the list is.  Additionally, to
>> preserve confidentiality of my list, I have removed the user's login name
>> from this error report and replaced it with the characters "x" where his
>> login name would ordinarily go.
>>
>> Sincerely,
>> Glenn Alperin
>> [log in to unmask]
>> list-owner (in name only) of faceblind
>>
>> The header information of the error message appears below for your
>> reference.
>>
>>________________________________________________________________________________
>>
>>                                         Date:     15-Oct-1998 11:12am EDT
>>                                         From:     L-Soft list server at
>>St. John
>>
>>[log in to unmask]
>>                                         Dept:
>>                                         Tel No:
>>
>> TO:  Glenn Alperin                        ( [log in to unmask] )
>>
>> Subject: FACEBLIND: error report from MAELSTROM.STJOHNS.EDU
>>
>> The enclosed message, found in the  FACEBLIND mailbox and shown under
>>the spool
>> ID 12028470 in the system log, has been identified as a possible
>>delivery error
>> notice for the  following reason: "Message/Delivery-Status" body  part
>>found in
>> the message body.
>>
>> ------------------------ Message in error (52 lines)
>>--------------------------
>> Date:       Thu, 15 Oct 1998 12:07:12 -0500
>> Reply-to:   [log in to unmask]
>> From:       "LSMTP for OpenVMS v1.1a" <[log in to unmask]>
>> Subject:    Undelivered mail
>> To:         [log in to unmask]
>> X-Report-Type: Nondelivery; boundary="> Error description:"
>>
>> An error was detected while processing the enclosed message.  A list of
>> the affected recipient follows.   This list is in a special format that
>> allows software like LISTSERV to automatically take action on incorrect
>> addresses; you can safely ignore the numeric codes.
>>
>> --> Error description:
>> Error-for:  [log in to unmask]
>> Error-Code: 3
>> Error-Text: Mailer mail.gelnhausen.net said:
>>             "550 relaying mail to POP3.MAIN-KINZIG.NET is not allowed"
>>
>> Error-End:  One error reported.
>>
>> ------------------------------ Original message
>>------------------------------
>> Received: from maelstrom.stjohns.edu by maelstrom.stjohns.edu (LSMTP for
>>OpenVMS v1.1a) with SMTP id <[log in to unmask]>; Thu, 15
>>Oct 1998 12:07:01 -0500
>> Date:         Thu, 15 Oct 1998 11:52:06 -0500
>> Reply-To:     faceblind The Face Blind Folks
>><[log in to unmask]>
>> Sender:       faceblind The Face Blind Folks
>><[log in to unmask]>
>> From:         xxxxx xxxxxxx <[log in to unmask]>
>> Subject:      Re: Hoplessness???(was Re: psychobabble)
>> To:           [log in to unmask]
>> In-Reply-To:  <[log in to unmask]>
>>
>> <Message text removed to preserve anonimity>