Bug 321041 - Generated Message-id doesn't use FQDN
Summary: Generated Message-id doesn't use FQDN
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: 4.10.4
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-11 19:44 UTC by Rolf Eike Beer
Modified: 2017-01-07 22:23 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Eike Beer 2013-06-11 19:44:22 UTC
The Message-Id field uses only the hostname, not the FQDN. The hostname itself is very likely not unique (think of all that OEMCOMPUTER XP machines), so the FQDN should be used instead.

Reproducible: Always
Comment 1 Laurent Montel 2013-06-12 06:31:31 UTC
For the moment we use : "QHostInfo::localHostName()" which returns a value all the time.
but try to get all information about fqdn will take time and not sure that it's really possible.

Don't know a method to do it easily.
Comment 2 Rolf Eike Beer 2013-06-12 06:57:53 UTC
QHostInfo::localDomainName()?

Btw, I think this is the code in messagecomposer/job/skeletonmessagejob.cpp. When the FQDN getting fails it shows a message that it will use localhost.localdomain, but instead it uses local.domain.
Comment 3 Laurent Montel 2013-06-12 08:12:34 UTC
QHostInfo::localDomainName() I tested it, it returns QString() for me.
Comment 4 Denis Kurz 2016-09-24 18:16:58 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 5 Denis Kurz 2017-01-07 22:23:25 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.