Rodre Ghorashi-Zadeh wrote:

-
You used a space in the command line.   Don't do that.

OK, I replaced the space with a comma.
The above line must not have any spaces in it. Replace the space between "...mx_access" and "cidr:..." with a "," comma, just like in the example you were given before.
Now it is not erroring, but it doesn't seem to have any effect:

Aug 20 14:33:23 pshqma01 postfix/smtp[2523]: connect to 
clubzone.com.inbound10.mxlogic.net[208.65.144.2]: Connection timed out (port 25)
Aug 20 14:33:53 pshqma01 postfix/smtp[2523]: connect to 
clubzone.com.inbound10.mxlogic.net[208.65.144.3]: Connection timed out (port 25)
Aug 20 14:33:53 pshqma01 postfix/smtp[2523]: 016953B91271: to=, relay=none, 
delay=90, delays=0.01/0.02/90/0, dsn=4.4.1, status=deferred (connect to 
clubzone.com.inbound10.mxlogic.net[208.65.144.3]: Connection timed out)

The above messages are like what I was getting before I implemented the 
transport method. Thoughts? Thanks for the help.

~Rod

This only affects mail when it enters postfix (or more specifically, when it leaves the content_filter). Mail already in the queue will not be affected. Mail that bypasses the content_filter will not be affected.

Why is "to=" logged above? There must be a recipient address to look up the recipient MX.

--
Noel Jones

Reply via email to