LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (19 lines)
Print Reply
Content-Transfer-Encoding:
7bit
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
From:
Karen Reznek <[log in to unmask]>
Date:
Tue, 31 Aug 1999 06:40:38 -0400
Content-Type:
text/plain; charset=us-ascii
MIME-Version:
1.0
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
I've found that this can be an error when the receiver will accept the
address after the "@" only in lower case. I'm dealing with one of these
now, @TALK21.COM, and I've tried sending identical messages to the
subscriber with the only change being whether the address is in upper or
lower case. The lower case ones get through without a problem, and the
uppercase ones always bounce with the relay message. Because internet
conventions specify that the portion of the address after the @ should
not be case sensitive, this is an issue to take up with the bouncing
ISP. Listserv stores addresses with the portion after the @ in upper
case.

J. R. Lankford wrote:
> Hi, can anyone explain to me what the "we don't relay" errors mean
> that show up in the daily monitoring report now and then.

--
Karen Reznek
[log in to unmask], [log in to unmask]

ATOM RSS1 RSS2