Great Circle Associates List-Managers
(April 2001)
 

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

Subject: Re: Digest From: message header (was: Digest MIME types...)
From: Tim Pierce <twp @ rootsweb . com>
Date: Tue, 10 Apr 2001 13:20:38 -0400
To: James M Galvin <galvin @ acm . org>
Cc: Roger Fajman <RAF @ CU . NIH . GOV>, List-Managers @ GreatCircle . COM
In-reply-to: <Pine.BSF.4.21.0104091236450.33374-100000@two.elistx.com>; from galvin@acm.org on Mon, Apr 09, 2001 at 12:45:04PM -0400
References: <200104090417.AAA49412@mail.acm.org> <Pine.BSF.4.21.0104091236450.33374-100000@two.elistx.com>
User-agent: Mutt/1.2.5i

On Mon, Apr 09, 2001 at 12:45:04PM -0400, James M Galvin wrote:
> What does LISTSERV set the From: message header to when sending out
> digests?
> 
> This is something for which there is no guidance anywhere.  When you're
> sending out content based digests it seems reasonable to set the From:
> message header to the address of the moderator.  But what do you do when
> the digest is size or time-based?
> 
> Setting it to the address of the list is problematic because there are
> so many "broken" mailers out there that will send failed mail notices
> and vacation notices and various other things to the From: message
> header.
> 
> Setting it to the failed mail processor is better but there's always
> people who reply to a digest and don't reset the To: header.

Good questions.

SmartList uses `listname@listhost'.  It's pretty good at catching most
bounces and failure notices that are sent to the submission address, so
that doesn't tend to be an issue.

This might be a good solution, in principle:

  From: mumble-request@listhost (or "Majordomo", or "listname-bounces", etc.)
  Subject: Mumble Digest Vol. 6, #4
  To: mumble@listhost
  Content-Type: multipart/digest; boundary="--- digest marker ---"
  
  ----- digest marker ---
  
  From: joe@foo.com
  Subject: Message #1
  Message-ID: <sdjfls@foo.com>
  To: mumble@listhost
  
  MESSAGE BODY
  
  ----- digest marker ---
  
  From: sue@bar.net
  Subject: Message #2
  Message-ID: <kjhksht@bar.net>
  To: mumble@listhost 
  
  MESSAGE BODY

  etc.

Each enclosed message includes a `To:' header that points back to
the list submission address.  It also includes the original
Message-Id.  A reply to the enclosing multipart/digest message
itself will go back to mumble-request.  If the digest is exploded
and the user performs "reply to all" on one of the enclosed messages,
the reply will be copied to mumble@listhost and have a good Subject
header, In-Reply-To, and so on.

SmartList tries hard to recognize bounces, unsubscribe requests,
etc. that are sent to the list submission address, so using the
list submission address for the digest return address is not so
bad.  But not all lists have that advantage.




Follow-Ups:
References:
Indexed By Date Previous: Re: Digest MIME types...
From: "Peter Galbavy" <peter.galbavy@knowledge.com>
Next: Re: Digest MIME types...
From: Tim Pierce <twp@rootsweb.com>
Indexed By Thread Previous: Re:Digest From: message header (was: Digest MIME types...)
From: Charlie Summers <charlie@lofcom.com>
Next: Re: Digest From: message header (was: Digest MIME types...)
From: Charlie Summers <charlie@lofcom.com>

Google
 
Search Internet Search www.greatcircle.com