After changing the client certificate request to 'no' we get a little
further in the negotiation but it still fails:
. . .
Jul 19 09:31:37 mx32 postgrey[29869]: action=pass, reason=triplet
found, client_name=mail.rosedale.ca, client_address=66.135.118.147,
sender=jtho...@connectrans.com, recipient=expo...@harte-lyne.ca
Jul 19 09:31:37 mx32 policyd-spf[15740]: prepend Received-SPF: Pass
(mailfrom) identity=mailfrom; client-ip=66.135.118.147;
helo=mail.rosedale.ca; envelope-from=jtho...@connectrans.com;
receiver=<UNKNOWN>
Jul 19 09:31:37 mx32 postfix-p25/smtpd[44981]: NOQUEUE:
client=mail.rosedale.ca[66.135.118.147]
Jul 19 09:31:37 mx32 postfix-p25/smtpd[44981]: lost connection after
DATA (0 bytes) from mail.rosedale.ca[66.135.118.147]
Jul 19 09:31:37 mx32 postfix-p25/smtpd[44981]: disconnect from
mail.rosedale.ca[66.135.118.147] ehlo=1 mail=1 rcpt=1 data=0/1
commands=3/4
. . .
The internal mail server for this organisation is MX Exchange.
However, the MTA relay is a Barracuda firewall appliance:
PORT STATE SERVICE VERSION
25/tcp open smtp Barracuda Networks Spam Firewall smtpd
Service Info: CPE: cpe:/h:barracudanetworks:spam_%26_virus_firewall_600:-
They are reporting a timeout error when trying to transmit to our
Postfix-3.3.1 MX. All we see is the above in our maillog.
Their DSN says:
. . . conversation with mx32.harte-lyne.ca[216.185.71.32]:25 timed out
while sending MAIL FROM . . .
We have only seen this type of problem (client disconnect with 0 data
transferred) with a very few of our correspondents. As it coincides
with moving from Postfix-2.11 to 3.3 we are concerned that we have
introduced some sort of compatibility issue.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:byrn...@harte-lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
