Ok, will do. I'm not trying to be cryptic. I've been around long
enough to know that error messages themselves are sometimes not
particularly helpful and in the best case can often, only, indicate a
general cause.

----- Original Message -----
From: "Dan Robinson" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, August 16, 2004 08:46
Subject: Re: Daily report: error 553


Christine, while you may want to x out the subscriber's name, posting
the real domain that is causing a problem is the only way to get a
useful answer. The folks here are very good, but can't give a good
answer unless they have real data to work with.

Dan Robinson
[log in to unmask]

> -----Original Message-----
> From: LISTSERV list owners' forum
> [mailto:[log in to unmask]]On Behalf Of Christine Quiriy
> Sent: Saturday, August 14, 2004 10:38 AM
> To: [log in to unmask]
> Subject: Re: Daily report: error 553
>
>
> OK, sorry. I wouldn't reveal a subscriber's email address in a
public
> forum like this. In future, if I use bogus names, I'll be sure to
> alert the readers or use generics that absolutely can't be mistaken.
>
> Christine
>
> ----- Original Message -----
> From: "Ben Parker" <[log in to unmask]>
> To: <[log in to unmask]>
> Sent: Saturday, August 14, 2004 10:13
> Subject: Re: Daily report: error 553
>
>
> > On Sat, 14 Aug 2004 10:06:20 -0400, Christine Quiriy
> <[log in to unmask]>
> > wrote:
> >
> > >but I don't know why you say the domain is
> > >dead, because it's not.
> >
> > By 'dead' I mean pitts.com isn't able to accept email
> (WSAECONNREFUSED error).
> >
> > >Pitts.com is just one I made up
> >
> > Ah.  OK, next time you ask for help, don't use bogus domains, as
it
> distorts
> > the possible answers.
>