.forward does not work

I have installed ISPConfig 2.2.11 . It seems that the .forward function does not work. I also do not see errors in /var/log/mail.err

The .forward is as follows (and as expected): "|/usr/bin/procmail -f-", [email protected]

I'm hosting another domain where this same user is forwarded to this particular account. Maybe it's because it's on the same ISPConfig server, but the .forward for that account points to [email protected]

Update: the forward from the secondary account to the primary account (and then to the external account) also does not work.

Any ideas what may be the problem?

 

What's in the mail log when you send an email to one of these accounts where .forward isn't working?

 

Here's the section on this. Interestingly enough it seems that their relay server will not accept messages from my server. My server does not use a relay server by the way.

Mar 27 17:14:46 mailserver postfix/qmgr[9359]: E1EC8CC029F: removed
Mar 27 17:14:46 mailserver postfix/smtp[31657]: 650FACC02A1: host smtp-telenet.telenet-ops.be[195.130.132.50] refused to talk to me: 450 Client host rejected: cannot find your hostname, [193.141.13
3.107]
Mar 27 17:14:46 mailserver postfix/smtp[31657]: 650FACC02A1: host smtp-telenet.telenet-ops.be[195.130.132.41] refused to talk to me: 450 Client host rejected: cannot find your hostname, [xxx.xxx.xxx.xxx]
Mar 27 17:14:46 mailserver postfix/smtp[31657]: 650FACC02A1: host smtp-telenet.telenet-ops.be[195.130.132.52] refused to talk to me: 450 Client host rejected: cannot find your hostname, [xxx.xxx.xxx.xxx]
Mar 27 17:14:50 mailserver postfix/smtp[31657]: 650FACC02A1: to=<[email protected]>, orig_to=<[email protected]>, relay=smtp-telenet.telenet-ops.be[195.130.132.51]:25, delay=4.7, delays=0.01/0.01
/4.4/0.27, dsn=2.0.0, status=sent (250 Ok: queued as 2A5D333E97)
Mar 27 17:14:50 mailserver postfix/qmgr[9359]: 650FACC02A1: removed

 

It's a fixed IP address and I double checked - the server is not blacklisted. I did a bit more research and I think it has something to do with reverse DNS not being set up for my public IP addresses. I have a ticket open with my ISP and expect that they'll be able to explain how to get that solved.

 

Yes, that's possible.

 

many email servers when receiving messages are checking with reverse DNS. if this fails they refuse to receive messages from that host...