[courier-users] Incoming ESMTPD via SSL

I bet im forgetting something simple, but how do i remove incoming SSL
as a requirement for SMTP?

We have a few companies we deal with with SMTP servers so old it looks
like they cannot handle it. We get the following in the logs:
May 16 01:00:55 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
couriertls: accept: error:140EC0AF:SSL routines:SSL2_READ_INTERNAL:non
sslv2 initial packet
or
May 16 00:56:11 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
DEBUG: Unexpected SSL connection shutdown.

Thanks

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

Glenn R. Martin writes:

> I bet im forgetting something simple, but how do i remove incoming SSL
> as a requirement for SMTP?

SSL is not required for SMTP, unless you explicitly set the configuration,
as such.

> We have a few companies we deal with with SMTP servers so old it looks
> like they cannot handle it. We get the following in the logs:
> May 16 01:00:55 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
> couriertls: accept: error:140EC0AF:SSL routines:SSL2_READ_INTERNAL:non
> sslv2 initial packet
> or
> May 16 00:56:11 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
> DEBUG: Unexpected SSL connection shutdown.

This would be a different question -- how to disable SSL, period.

Remove the COURIERTLS setting from the esmtpd-ssl configuration file.



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQBILiD8x9p3GYHlUOIRAnx8AJ9gPGgqrX1RrP9u4dmHw+ cd0SfG8QCdH/5Y
tBTjMc5qqegMbJDOnTwpKvU=
=7vGD
-----END PGP SIGNATURE-----

Glenn R. Martin wrote:
> We have a few companies we deal with with SMTP servers so old it looks
> like they cannot handle it. We get the following in the logs:
> May 16 01:00:55 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
> couriertls: accept: error:140EC0AF:SSL routines:SSL2_READ_INTERNAL:non
> sslv2 initial packe

Try updating to the latest release of Courier, and removing all of the
TLS_PROTOCOL and TLS_STARTTLS_PROTOCOL settings from all of your
configuration files.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

On 16 May 2008, at 23:09 , Gordon Messmer wrote:

> Glenn R. Martin wrote:
>> We have a few companies we deal with with SMTP servers so old it
>> looks
>> like they cannot handle it. We get the following in the logs:
>> May 16 01:00:55 gibson courieresmtpd: courieresmtpd: STARTTLS failed:
>> couriertls: accept: error:140EC0AF:SSL
>> routines:SSL2_READ_INTERNAL:non
>> sslv2 initial packe
>
> Try updating to the latest release of Courier, and removing all of the
> TLS_PROTOCOL and TLS_STARTTLS_PROTOCOL settings from all of your
> configuration files.
>

Sam's suggestion didnt work on either end. Gordon yours may have,
however it stops us from sending mail out as we are ALL configured to
use SSL, and weve got a bunch of devices. So changing the settings
would just anger people.

How can i set this up so that both the SSL version and the plain port
25 one are running in tandem?

> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-
> users


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

Glenn R. Martin wrote:
> On 16 May 2008, at 23:09 , Gordon Messmer wrote:
>
>> Try updating to the latest release of Courier, and removing all of the
>> TLS_PROTOCOL and TLS_STARTTLS_PROTOCOL settings from all of your
>> configuration files.
>>
>
> Sam's suggestion didnt work on either end. Gordon yours may have,
> however it stops us from sending mail out as we are ALL configured to
> use SSL, and weve got a bunch of devices. So changing the settings
> would just anger people.
>

No, it won't stop you from using SSL. Removing the TLS_PROTOCOL and
TLS_STARTTLS_PROTOCOL settings from the configuration files under the
current version of Courier will cause courier to use the default
settings. The defaults use an interoperable SSL handshake.

You should also make sure that TLS_CIPHER_LIST is set to the default in
all of your configuration files.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

On 17 May 2008, at 02:03 , Gordon Messmer wrote:

> Glenn R. Martin wrote:
>> On 16 May 2008, at 23:09 , Gordon Messmer wrote:
>>
>>> Try updating to the latest release of Courier, and removing all of
>>> the
>>> TLS_PROTOCOL and TLS_STARTTLS_PROTOCOL settings from all of your
>>> configuration files.
>>>
>>
>> Sam's suggestion didnt work on either end. Gordon yours may have,
>> however it stops us from sending mail out as we are ALL configured to
>> use SSL, and weve got a bunch of devices. So changing the settings
>> would just anger people.
>>
>
> No, it won't stop you from using SSL. Removing the TLS_PROTOCOL and
> TLS_STARTTLS_PROTOCOL settings from the configuration files under the
> current version of Courier will cause courier to use the default
> settings. The defaults use an interoperable SSL handshake.
>
> You should also make sure that TLS_CIPHER_LIST is set to the default
> in
> all of your configuration files.
>

Ill schedule it with my crew and upgrade, thanks Gordon.

>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-
> users


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users