Thus spake Sam Varshavchik on Wed, Dec 15, 2004 at 05:26:50PM CST
Jerry Amundson writes:
On Wednesday 15 December 2004 06:14 am, Sam Varshavchik wrote:
Jerry Amundson writes:
250 Ok
data
354 Feed me
testing
.
...and just sits there (thus the eventual timeout from courier).
But, if I specifically end data with Enter.^V^M :
.^M
250 Thanks
So I still cannot determine if it's Courier's or Postini's issue?
Courier terminates a message by sending .CRLF, so the above doesn't
really determine anything.
Why would "addcr | TLS_VERIFYPEER=NONE couriertls -host=64.18.7.10
-port=25 -protocol=smtp"
behave differently than a courieresmtp/couriertls delivery, which times
out to the same IP?
Right now, I resolve the MX record for psknet.com to 64.18.4.10.
That's correct, and the MX records for blazenet.net, blazenet.com,
scrtc.com, cableone.net, suscom.net and countless others resolve likewise.
I just spent half an hour setting up TLS exemptions for these domains in
esmtproutes and deleting undeliverable email from my mail queue.
Does anyone know if this problem is being seen by people running TLS-capable
MTAs other than courier?
26 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Postini probl...
