Re: [courier-users] Starttls Error . . .

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--===============0950184589==
Content-Type: multipart/signed;
boundary="=_mimegpg-commodore.email-scan.com-30477-1162338741-0003";
micalg=pgp-sha1; protocol="application/pgp-signature"

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.
The Internet standard for MIME PGP messages, RFC 2015, was published in 1996.
To open this message correctly you will need to install E-mail or Usenet
software that supports modern Internet standards.

--=_mimegpg-commodore.email-scan.com-30477-1162338741-0003
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Jason Flatt writes:

> I've got an error that I have not been able to find an answer to on this mail
> list's archives or Google. I'm not even sure where to start looking to fix
> it, or if it's my problem to fix.
>
> Oct 31 09:15:33 [courieresmtp]
> id=0016BB45.454784B4.00002CEA,from=<from-address>,addr=<to-address>: 500
> starttls: accept: error:00000000:lib(0):func(0):reason(0)
> Oct 31 09:15:33 [courieresmtp]
> id=0016BB45.454784B4.00002CEA,from=<from-address>,addr=<to-address>,status:
> failure
>
> Messages from the to-address person arrive to the from-address person just
> fine, but when going the other way, I get the above errors in the logs, and
> he gets an undeliverable mail error message back from our mail server, not
> the recipient's mail server.
>
> The server is running an older version of Courier: 0.39.1. Where do I need to
> look to correct this?

This is an ancient version of Courier that nobody looked at for years. I
don't remember if there ever was any known issue or bug in this area, going
back so many years.

Please upgrade to the current version of Courier. You may, as a temporary
workaround, turn off SSL when sending mail. See the courierd configuration
file for more information.




--=_mimegpg-commodore.email-scan.com-30477-1162338741-0003
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iD8DBQBFR+G1x9p3GYHlUOIRAgw/AJ9sD81XgfH/O1XB8YONB3by0bsMxgCfWzhV
bjlE1CCGzazA+W4+qhvt8YI=
=6CJ+
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-30477-1162338741-0003--


--===============0950184589==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=...057&dat=121642
--===============0950184589==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users

--===============0950184589==--