(*** This bug was imported into bugs.kde.org ***) Package: kmail Version: kMail 1.3.2 (using KDE 2.2.1 ) Severity: normal Installed from: Debian Packages Compiler: gcc 2.95.4 OS: Linux OS/Compiler notes: Not Specified Kmail is not able to send mail via my postfix server since i have the server check the hostname that MUA sends in HELO/EHLO smtp handshake. If hostname is not resolvable or not in FQDN format Postfix rejects mail. Here is the exact error message from my maillog: postfix/smtpd[7142]: reject: RCPT from pip-1.hitbox.com[209.75.20.72]: 450 <there>: Helo command rejected: Host not found; So from this you can see that kMail sends HELO there to initiate an SMTP connection. But since 'there' is not a valid resolvable hostname nor in FQDN format Postfix rejects mail. I would assume that kmail has to send HELO real.host.name.in.fqdn.format to the SMTP server or at least has an ability to let user set the hostname... igor (Submitted via bugs.kde.org) (Called from KBugReport dialog. Fields Application KDE Version OS Compiler manually changed)
On Friday 02 November 2001 23:48 igor@linuxinside.com wrote: > > Kmail is not able to send mail via my postfix server since i have the > server check the hostname that MUA sends in HELO/EHLO smtp handshake. If > hostname is not resolvable or not in FQDN format Postfix rejects mail. > > Here is the exact error message from my maillog: > postfix/smtpd[7142]: reject: RCPT from pip-1.hitbox.com[209.75.20.72]: 450 > <there>: Helo command rejected: Host not found; > > So from this you can see that kMail sends > > HELO there > > to initiate an SMTP connection. But since 'there' is not a valid resolvable > hostname nor in FQDN format Postfix rejects mail. I would assume that kmail > has to send > > HELO real.host.name.in.fqdn.format > to the SMTP server or at least has an ability to let user set the > hostname... I actually wonder why only admins complain about this and up to now no normal user. All servers besides postfix seem to ignore the value since they anyway know where the connection comes from. Nevertheless we use gethostname now which is probably the correct way of doing this but in most cases that also doesn't give a much better result than "linux.local" or "localhost.localdomain". In the case someone is on a local network behind a firewall and has only a 192.168.x.x IP address then it's anyway not possible to comply with this. Regards Michael Haeckel
Meldung des Servers: Parameter to HELO does not conform to RFC syntax. This is the message, that I get in KMail. I can pick up my mail but not send. Whats wrong?? Thanks for any help in advance Tom gayartist@t-online.de
This bug is still present and annoys the admins, because checking these kind of details is the best way to block spam. To cite http://tools.ietf.org/html/rfc2821: "The argument field contains the fully-qualified domain name of the SMTP client if one is available. In situations in which the SMTP client system does not have a meaningful domain name, the client SHOULD send an address literal" So if gethostname does not return a FQDN then please use the current IP as an address literal. (Even if that results in "EHLO [192.168.1.1]".) The point in checking this field is not to get additional information, but to distinguish decent mail clients from spambots.
Reopening... The SMTP slave in KDE4 can currently not detect the FQDN or a meaningful IP Address.
*** Bug 166061 has been marked as a duplicate of this bug. ***
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!