After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 356464 - correlate/assign known mailinglist address with own sender address
correlate/assign known mailinglist address with own sender address
Status: RESOLVED DUPLICATE of bug 356245
Product: evolution
Classification: Applications
Component: Mailer
3.2.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[composer] evolution[addr_mail]
Depends on:
Blocks:
 
 
Reported: 2006-09-17 22:34 UTC by Sven J.
Modified: 2012-06-20 12:41 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement



Description Sven J. 2006-09-17 22:34:23 UTC
i read some mailinglists and i have got several mail accounts. I would like to request a feature that evolution allows me to store mailinglist-adresses in my adressbook. From then evolution should keep care i use the correct account with the mailinglist. If i override the default setting, evolution sould pop up a warning dialog Do you want to override the default sender adress for this mailinglist? [cancel, proceed]
Comment 1 Sven J. 2007-05-26 19:30:39 UTC
Evolution already has the feature to use the correct FROM account when you reply a normal email.

This does not work for mailing lists, i suppose its because the TO field contains the lists adress and not the accounts adress.

Evolution could resolve the correct FROM adres either automatically from the header in the delivered to field.
Or it could resolve the adress from the adressbook. I would appreciate if the evolution-data-server could handle entries of a special type "mailinglist". It could help to set some reply-options.


Comment 2 André Klapper 2012-06-20 12:41:45 UTC
This is a duplicate of bug 356245, could also be solved by fixing bug 215115.

*** This bug has been marked as a duplicate of bug 356245 ***