Great Circle Associates Majordomo-Users
(June 1997)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: Apparently-To:-Header and Compuserve
From: Joerg Henne <jh @ brian . softwarezentrum . de>
Date: Tue, 24 Jun 97 17:16:41 +0200
To: Leslie Mikesell <les @ Mcs . Net>
Cc: majordomo-users @ GreatCircle . COM
In-reply-to: <199706232305.SAA20955@Jupiter.Mcs.Net>
References: <199706232305.SAA20955@Jupiter.Mcs.Net>

> > While running a moderated list with users from Compuserve on it I
> > expericed the (famous?) 'Apparently-To' problem. The problem causes lots
> > of Apparently-To headers (one for each Compuserve user on the list) to be
> > generated in the messages, not only disclosing the user's addresses but
> > also inflating the headers massively.
>
> This is done by the mail transport, not majordomo, and usually only happens
> when the message does not have a syntactically correct To: or Cc: header.
Having read the list archives i'm aware of this one (:-), but with  
Compuserve there's another 'Apparently-To'-problem, that causes all  
recipients within Compuserve to appear in multiple Apparently-To headers (in  
contrast to the list name apprearing in a single Apparently-To header with  
the 'classical' problem).
It seems that theese multiple headers are generated by the Compuserve MTA if  
it finds an invalid address in the To:-header. Therefore the (not very  
extensively tested) is to put a valid Compuserve address in the To:-header -  
which may look quite odd sometimes...

Gruesse
Joerg Henne


References:
Indexed By Date Previous: Re: Bug in majordomo (fwd)
From: Michael Brennen <mbrennen@fni.com>
Next: Archiving
From: "Nicole D. Jones" <jones@ceri.memphis.edu>
Indexed By Thread Previous: Re: Apparently-To:-Header and Compuserve
From: Leslie Mikesell <les@Mcs.Net>
Next: majordomo crash under Solaris
From: Stephane Chatre <chatre@COF.ORST.EDU>

Google
 
Search Internet Search www.greatcircle.com