Red Hat Bugzilla – Bug 146356
Cannot send over SMTP/TLS
Last modified: 2018-04-11 06:11:39 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0 Description of problem: Evolution is set to send to server.domain.com:25 with ssl enabled (If I do not put the :25 there it will try immediately to use ssl (the old protocol) on 465 without a handshake. I have also tried on other non-standard ports and all fail with the error on the server SMTP protocol violation: syncronization error (input sent without waiting for greeting): rejected connection. On the client I get the error: CamelException.setv(0xb5ef63e0, 2, 'Welcome response error: Connection timed out') It is almost as if evolution does not understand the 2XX message from the server. Version-Release number of selected component (if applicable): evolution-2.0.2-3 How reproducible: Always Steps to Reproduce: 1. Server configuration, Host set to host.domain.com:25 or host.domain.com:1465 ; server requires authentication ticked ; and Use secure connection (SSL) always. 2. send some mail 3. receive error, it is interesting to note that if SSL is set to never mail is sent. Actual Results: Evolution provides an error, and is unable to send using TLS Expected Results: The mail should have been sent on the port specified, using TLS Additional info: The MTA used was exim version 4.42 and 4.34. Similar to this bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131744; however that was without SSL.
Exactly the same behaviour here with a postfix server on the other end.
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
The distribution against which this bug was reported is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as INSUFFICIENT_DATA. Setting status to NEEDINFO, and awaiting information from the reporter. Thanks in advance.
Closing as INSUFFICIENT_DATA.