Per Jessen wrote:
Medwinz, I know you're trying to be helpful, but do you really think I have not done so already? I have (obviously) checked the log, I'm running full debug on that particular client and I've captured tcpdump for further analysis.
For example some email server restrict the envelope or do reverse checking and unintentionally reject the good email.
In which case I would have a perfectly good SMTP-level error message, and I would have had no reason to start looking at the tcp level data.
From what I saw in the dump your server resent the last "200 2.1.5" message sereval times after the rcpt to. It seems as if the protocol went out of sync.
The one thing you can try is to restrict possible options for the remote system how it can mess up the communication. Try not to offer pipelining to the trouble system. I suspect that the other system doesn't support pipelining correctly. /etc/postfix/main.cf: smtpd_discard_ehlo_keyword_address_maps = hash:/etc/postfix/dumb_down_idiots /etc/postfix/dumb_down_idiots: 195.65.248.162 pipelining, silent-discard If have little hope that you will find a competent admin on the other end if the system uses an internal name for helo. Good luck! -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org