David Koski wrote:
On Tuesday 27 January 2009, Sahil Tandon wrote:
450 4.1.1 <e...@mytestdomain.com>: Recipient address rejected:
undeliverable address: host cuda2.myrelayhost.com[65.183.202.16] said:
550 Blocked (in reply to RCPT TO command)
Careful when munging! You forgot to obfuscate xx.xxx.xxx.xx. :-)
Is it not permitted to use recipient verification through a relay server?
So cuda2.cascadenetworks.com does not believe e...@mytestdomain.com is a
valid recipient.
That seems to be the case when doing recipient verification. But without it
accepts the email to e...@mytestdomain.com happily.
Wild guess of the day is that the barracuda doesn't like the
sender address used with the verification probes.
Use the address_verify_sender parameter to control the sender
address postfix uses. If you have postfix earlier than 2.5,
set the following in your main.cf:
address_verify_sender = $double_bounce_sender
Or try some other valid user name until you find something the
barracuda likes.
http://www.postfix.org/postconf.5.html#address_verify_sender
If that just doesn't work, you may need to direct your address
probes directly at the mail server behind the barracuda. See
the following to control routing of address probes:
http://www.postfix.org/ADDRESS_VERIFICATION_README.html#probe_routing
Note that rejecting the null sender address is a very poor
anti-spam choice. Some sites also reject mail from
"postmas...@..." which is not much better.
http://rfc-ignorant.org/policy-dsn.php
--
Noel Jones
