https://bugs.kde.org/show_bug.cgi?id=388160
Bug ID: 388160
Summary: ksmtp EHLO sends server hostname as domain parameter
by default
Product: kmailtransport
Version: unspecified
Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: kdepim-b...@kde.org
Reporter: k...@snafu.de
Target Milestone: ---
As Fabian Vogt pointed out elsewhere
(https://bugs.kde.org/show_bug.cgi?id=387926#c30), ksmtp sends the server
hostname as the EHLO domain parameter (confirmed via telnet and wireshark):
EHLO mail.snafu.de
550 EHLO/HELO not allowed by local policy.
In this case my Provider rejects the EHLO, which results in failure to
transport the e-mail.
Any other domain will be accepted:
EHLO foo.bar
250-sour.ops.eusc.inter.net Hello ...
Consequently, this can be worked around by specifying an explicit custom
hostname in the SMTP settings e.g. in kmail2. It has been recommended somewhere
that in case the client has no (meaningful) domain, the bracketed IP address
should be sent, such as:
EHLO [nnn.nnn.nnn.nnn]
In my case, this is accepted, too.
I'm not 100% sure this is a bug, but it seems sane client behavior not to tell
the server it ought to talk to itself. It's understandable that the server
would test for this domain and none else.
This issue didn't arise until a couple of days ago. I do not know what the
default EHLO parameter was before that change.
--
You are receiving this mail because:
You are watching all bug changes.
