Bug 84430 - New Message to Mailing List doesn't work
Summary: New Message to Mailing List doesn't work
Status: RESOLVED DUPLICATE of bug 78626
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-03 21:39 UTC by David Jarvie
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Jarvie 2004-07-03 21:39:20 UTC
Version:           1.6.82 (CVS HEAD) (using KDE KDE 3.2.3)
Installed from:    Compiled From Sources
OS:                Linux

I have configured KMail apparently correctly to set up a folder as holding a mailing list. (The configuration was done using a previous version of KMail before I updated to the CVS version.) But the New Message to Mailing List button does nothing.

This appears to be because there is no "mailto:" prefix to the mailing list posting address in the folder's configuration. However, there is nothing to indicate that this is wrong, and the upgrade to the CVS version didn't insert "mailto:" in the config file.

I tried clicking the "Detect Automatically" button for one of my mailing list folders (for kde-devel), but it displayed the error message "KMail was unable to detect a mailing list in this folder. Please fill the addresses by hand.". (The posting address for this folder is configured as kde-devel@mail.kde.org, so I don't know why it couldn't detect it.) So even clicking the Detect Automatically button didn't fix the problem.

This needs to be fixed for KDE 3.3 so that people can upgrade without problems.
Comment 1 David Jarvie 2004-07-03 21:43:40 UTC
There should also be validation to ensure that posting addresses entered manually have the "mailto:" prefix. It should not be possible to enter the address without this prefix, click OK and then find that it doesn't work.
Comment 2 Stephan Binner 2004-07-06 13:07:01 UTC

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