Why is my dialup collect from pop action using Received: * for * not correctly sorting mail received through a Content Technologies SMTPRS 4.2.5 firewall?
I have set up my dialup rules to collect mail from my pop domain. This domain mail comes into the mail server at my ISP through a Content Technologies SMTPRS 4.2.5 firewall which adds a header clause to indicate this. When I use the Dialup Action "Received: *for*" to collect my pop domain mail GMS is not picking up on the correct address.
For example, when the Received: *for* rule is used, a message containing this header field:
Received: from internetserver1.sender.dom by novirushere.companyISP.dom
(Content Technologies SMTPRS 4.2.5) with ESMTP id
Shows in the SMTP log that the message RCPT is T5901b775040a20080b120@novirushere.companyISP.dom which is incorrect. The correct RCPT clause should be firstname.lastname@example.org which appears after the "for" in the Received: header.
What was happening in the question was that GMS was picking up on the first entry that seemed to be an email address in the header and treating it as though it was a legitimate email address.
We have now modified the processing GMS does when collecting mail through actions set under Dialup > Schedule > Next > Edit Action to look after the "for" in the Received: line for the email address. If no email address is found after the "for" in the Received: line, the system will look for the first email address in the header. This means that the above mentioned problem should no longer happen.
If you experience problems collecting your email from a pop domain account and the above mentioned change has not helped, please contact Gordano Support for further help. Please have your contract number ready when calling through to technical support.
Keywords:firewall dialup actions Content Technologies