Bug 303109 - Message-ID: field of kmail 4.8.4 exposes hostname
Summary: Message-ID: field of kmail 4.8.4 exposes hostname
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.8.4
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-06 13:46 UTC by Klaus Layer
Modified: 2023-10-06 12:11 UTC (History)
6 users (show)

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 Klaus Layer 2012-07-06 13:46:43 UTC
I am using kubuntu and upgraded recently to KDE 4.8.4. Kmail included in SC 4.8.4 exposes the hostname of the machine where kmail is running via the Message-ID field. In earlier versions of Kmail Message-ID was i.e.

Message-Id: <201102190733.46500.myemailaddress>

with KDE 4.8.4 Message-ID is

Message-ID: <4657529.D6e2SancXH@myhostname>

I found that the Message-ID can be configured, but a default that does not expose internal data would be better.

Regards,

Klaus


Reproducible: Always

Steps to Reproduce:
1. create message
2. send message 
3. lookup message-id in header
Comment 1 regi.hops 2012-12-19 01:09:12 UTC
(In reply to comment #0)
> I found that the Message-ID can be configured, but a default that does not
> expose internal data would be better.

Hi,
I have the problem that some servers flag my messages as spam, because of that local domain part.
How and where can it be configured?

Regards
Regi
Comment 2 regi.hops 2012-12-19 02:52:45 UTC
OK - Found it at last :-)
Looked in every place but certainly not in the "Editor-Configuration".
Sometimes I think the configuration of KMail is made by the help of a random generator, and maybe not everything that could be translated should be.

But I agree the default value should be something else than the local host name.
Using the standard domain of the send options would be more plausible, or the configurable host name in the extended send options.

Cheers
Regi
Comment 3 Rolf Eike Beer 2013-06-11 19:40:46 UTC
Using the email address is problematic as many people do not own the domain that would be used for that. So by default using the hostname is a better idea.
Comment 4 Laurent Montel 2013-06-12 06:22:52 UTC
For me too. Using hostname is better.
Comment 5 kolAflash 2015-06-07 13:36:58 UTC
But the hostname will expose some private information about you, which you might don't want to share with everyone you're writing emails to.

Other mail-clients like Thunderbird or K9Mail also use the E-Mail domainname. E.g. writing from john@example.com will give you a message-id *@example.com
Comment 6 tusooa 2023-10-06 10:56:39 UTC
Bumping this. In 23.08.1, I don't find any way to configure the msgid of my outgoing emails. The message ID will ALWAYS contain my local hostname no matter what settings I give.

This is a *security concern* as it can probably cause identity leaks.
Comment 7 Jonathan Marten 2023-10-06 11:51:34 UTC
The message-ID suffix is configurable (globally for all messages):  Configure KMail - Composer - Headers
Check the "Use custom message-ID suffix" box and enter anything in the text box below.
Then all outgoing message will use that setting, for example:

Message-ID: <13646269.uLZWGnKmhe@mycustommessageidsuffix>
Comment 8 tusooa 2023-10-06 11:54:42 UTC
(In reply to Jonathan Marten from comment #7)
> The message-ID suffix is configurable (globally for all messages): 
> Configure KMail - Composer - Headers
> Check the "Use custom message-ID suffix" box and enter anything in the text
> box below.
> Then all outgoing message will use that setting, for example:
> 
> Message-ID: <13646269.uLZWGnKmhe@mycustommessageidsuffix>

Thank you. Do you know if there is a way to set this differently for different accounts?
Comment 9 Jonathan Marten 2023-10-06 12:11:03 UTC
Sorry, no, that does not appear to be possible.