Subject: Mailing list problems

From: Joe Pollock <[email-masked]>
Date: Sun, 14 Nov 1993 17:48:59 -0800 (PST)

Pine - rev. 3.07 

We have a user who put a .forward token in his home directory to send mail to
another system that he can access from home as a local call.  Everything
works fine for individual mail.

When, however, his local address on our system is included in a
distribution list, the entire list breaks.  No one on the list seems to
get the mail; individuals included as cc: don't get the mail, no error is
returned to the originator (the mail is appropriately appended to sent-mail).
I have not located any errors in the sendmail logs, although I'm not sure
what I should be looking for.

I didn't see anything obvious in the .pine-debug files, either.

Is this peculiar to 3.07, and fixed in 3.85+?  We've been waiting for Pine
to be stable for a few weeks before upgrading, and planning to do it
during the end-of-quarter break.

Joe Pollock    
The Evergreen State College

---

From: Steve Hubert <[email-masked]>
Date: Sun, 14 Nov 1993 23:59:40 -0800 (PST)

[This is probably more a question that should go to pine-bugs (a small 
group of people at Univ. of Wash.) instead of pine-info (lots of people 
around the world).  So I suggest your reply go only to pine-bugs, unless 
you really wanted the bigger list.]

> works fine for individual mail.

I'd like to understand the details a little more.  You have userA above
with the .forward file.  Then userB has a Pine distribution list which
contains userA as one of the addressees.  If userB sends to that list, no
mail is delivered.  If userB removes userA from that list, it works.  If
userB sends to just userA, that works, too.  This is true for users other
than userB, too.  Does this sound like a correct description of the
problem? 
 
> during the end-of-quarter break.

It is possible that there is some 3.07 bug causing this, though I don't 
remember anyone having a problem similar to this.  If your system is one 
of the common ones we have made a binary version for, it would be useful 
to attempt to reproduce the problem with a newer binary.

Perhaps you could send us a copy of an address book that exhibits the 
problem, too.  And maybe the sendmail syslogging in the neighborhood of 
the time when the message is sent.  Thanks.
 
> The Evergreen State College

Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle