Closed Bug 230247 Opened 22 years ago Closed 14 years ago

Make identity picker work for mailing lists

Categories

(MailNews Core :: Composition, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 461669

People

(Reporter: BenB, Unassigned)

References

(Blocks 1 open bug)

Details

If you want to post to a mailing list, you usually have to use the subscribed address (spam blocking). This may not be your primary address (again e.g. spam prevention). If you hit reply, the email address over which you received the mailing list post should be preselected as identity (if listed at all). Bug 230230 tried to fix that in some cases (your own email address domain matches the mailing list's domain), but not the majority of cases where the mailing list belongs to a third party. Suggestion, quoted from the other bug: Usually, the email address which is subscribed to the mailing list is hidden in the Received headers somewhere *, unfortuantely that's not strictly formatted. You might want to plaintext-search those headers, if (and only if) you noticed that it's a mailing list post. There are standard headers establishing for mailing lists, e.g. List-Post, and other clients such as mutt use these to offer mailing list specific functions. I don't know the details, but it may be worth checking what these clients do, if they had any better ideas. *Example Received: ... Received: from mozdev.mozdev.org (mozdev.org [167.206.76.23]) by firespit.beonex.com (Postfix) with SMTP id 02F93CC104D3 for <ben.bucksch.news@beonex.com>; Tue, 6 Jan 2004 08:21:32 -0600 (CST) Received: ...
Component: Mail Window Front End → Composition
Summary: Make identify picker work for mailing lists → Make identity picker work for mailing lists
Searching Received: headers will work for many users, although it'll likely fail for local aliases/mailing lists, and some MTAs or MTA configurations don't put the destination in the header. If you do search for these, you'll want to stop at the first match with an identity, since there could be several forwardings done each with a different destination. Other possible headers: Delivered-To: X-Delivered-To: X-Original-To: Envelope-To: X-Envelope-To: X-Delivered-To: X-Rcpt-To: X-Real-To: There's discussion of the various headers (in the context of Procmail filtering at http://www.ii.com/internet/robots/procmail/qs/#envelope
Blocks: 228980
(In reply to comment #0) > Usually, the email address which is subscribed to the mailing list is hidden in > the Received headers somewhere *, unfortuantely that's not strictly formatted. > You might want to plaintext-search those headers, if (and only if) you noticed > that it's a mailing list post. Why do we want to know exactly that it's a mailing list? What we can do is try to search Received and other headers that were suggested iff To and CC both do not contain any of our identities. There is no reason we should care if it is a mailing list or not. (I.e. if (!identityFound) then {searchReceived()}.)
What about "Original-Recipient"? I get "Original-Recipient: rfc822;xxx@xxx.xx" in my mailing lists.
Product: MailNews → Core
Bug 264770 describes a cleaner way to implement the requested feature here.
Same issue. My mailing lists show the list's address in the "Delivered-To:" field and my actual address as the "Envelope-to:". The "Envelope-to:" address matches one of my identities, but when I reply, the correct identity is never selected. Nothing else in the headers matches an identity.
Assignee: mscott → nobody
QA Contact: esther → composition
Product: Core → MailNews Core
xref Bug 499080 - nice/easy UI for mailing list filtering using message headers
This was fixed by bug 461669, taking Delivered-To into account.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
No longer blocks: 228980
You need to log in before you can comment on or make changes to this bug.