I apologize, I was in a hurry and I miss this sometimes with Gmail - their
system doesn't display the subject by default. I didn't think about the
message ID, that's interesting... I've not seen messages thread based on
message ID before.
Anyway, I appreciate the reponse. This is what I thought and I've been
telling the customer that the other mail servers are busted, however,
they're getting e-mail from other servers - just not this particular Courier
system.
I'm wondering if there's a way to tell Courier to NEVER use STARTTLS, even
when its advertised?
Thanks,
D
On 6/28/06, Arno <ar...@disconnect.de> wrote:
Hi,
First of all, please don't reply to messages, replace the entire content
and
dont change the subject at least... It's still not the best way to reply
to
something while replacing the subject, because many mail clients thread
messages by their message id, but that's another part of the netiquette...
I have an installation of Courier that is a "bit" old, and while talking
to
serveral different mail servers, I'm getting messages like:
454 TLS not available
and then the message is deferred, forever.
I have looked at the settings in esmtp-ssl and checked to make sure the
I'm venturing a guess here: It has nothing to do with your own mail
server. It
is the other mailserver advertising STARTTLS capabilities, but not really
supporting it. So your mailserver gets an error when trying the STARTTLS
command. In other words: the other mailservers are broken and you should
get
the admin of those servers to fix theirs...
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=lnk&kid=120709&bid=263057&dat=121642
3 messages in net.sourceforge.lists.courier-users[courier-users] 454 TLS not available.
