Hi all
I have added a transport rule for one domain to send mail to a seperate server than our default relay, this is actually the same IP as our normal mailserver but an alternative port.
I have two issues;
- PMG shows " Recipient address rejected: unverified address: connect to 192.168.222.253[192.168.222.253]:40025: Connection refused;" although we never see PMG make a connection to our mailserver (192.168.222.253) and this is possible via telnet from the PMG VM.
- When I try to change the transport rule, the old rule continues to be used, for example I want to now test this transport rule against our other server which is on port 25, but PMG keeps trying to send to 40025. We see the /etc/pmg/transport file updated with the new information but it seems as though this is not used and PMG is working off a cache or similar.
Can anyone confirm similar issues / advise me on what next steps may be?
Thanks in advance
I have added a transport rule for one domain to send mail to a seperate server than our default relay, this is actually the same IP as our normal mailserver but an alternative port.
I have two issues;
- PMG shows " Recipient address rejected: unverified address: connect to 192.168.222.253[192.168.222.253]:40025: Connection refused;" although we never see PMG make a connection to our mailserver (192.168.222.253) and this is possible via telnet from the PMG VM.
- When I try to change the transport rule, the old rule continues to be used, for example I want to now test this transport rule against our other server which is on port 25, but PMG keeps trying to send to 40025. We see the /etc/pmg/transport file updated with the new information but it seems as though this is not used and PMG is working off a cache or similar.
Can anyone confirm similar issues / advise me on what next steps may be?
Thanks in advance