After about 2 weeks of this not happening the queues are full again.
This time a different address is the problem.  Why is it that
listserv when it finds an undeliverable email address it doesn't
continue on with the remaining recipients on the list but instead
sticks the file in the spool directory and tries repeatedly to
deliver to the one bad recipient?

I realize this shouldn't be happening and my idea of what appears to
be happening is probably wrong but if anyone has any suggestions on
what settings to check or can tell me what information to provide
that would help resolve this I'd be most appreciative.

Thanks.

-steve

On Tue, Dec 23, 2003 at 09:25:24AM -0600, Steve Price wrote:
> Lately I've noticed that posts to the lists that I support have
> been getting stuck in the spool directory.  Here's some examples
> of what I see in the logs repeatedly while those messages are
> stuck in the queue.
>
> -> RCPT TO:<[log in to unmask]>
> 450 <[log in to unmask]>: Recipient address rejected: Domain not found
>
> Its as if a post is held in the spool directory because a recipient
> somewhere in the middle of the list is undeliverable.  In order to
> clear it up I can either tell my MTA to return a 550 error code
> instead of 450 or I can manually edit the .mail file and remove
> the offending email address[1].  I'd rather not have to do either
> one but by doing either one the rest of the recipients of the stuck
> post finally get their copy.
>
> At first I thought it might help to add the following to my go.user
> script and restart listserv.
>
> SMTP_FORWARD_1="2*MY.HOST.NAME"
>
> This didn't work as I found several posts from over the past
> few days stuck in the spool again this morning.  Is there anyway
> to tell listserv to not queue posts itself but rather send the
> messages to my MTA and let it take care of them?
>
> Thanks.
>
> -steve
>
> [1] The bad email addresses are also either removed from the lists
> or set to not receive posts to keep them from doing the same thing
> on the next post.