Fail with message not working.
I have two domains each hosted by a different hosting company but both on cPanel. Both domains fail in the same way.
I have Global Email Filters -> Subject reject with bounce
message. Subject Contains: Latest investment Actions: Fail with message
"Your email has been detected as SPAM and deleted without being seen.
Should you feel that this is incorrect please resend your email to
='whitelisted1@loades.net'>whitelisted1@redacted. Thank you."
Same rule in each instance of cPanel.
Track delivery on both servers reports incoming mail matching the filter as in this example:
Event: failure error
User: -remote-
Domain:
From Address: ='jordan@krystal.co.uk'>jordan@redacted
Sender:
Sent Time: May 30, 2020, 1:09:13 PM
Sender Host: mxserverxxxxxl.co.uk
Sender IP: Redacted
Authentication: localdelivery
Spam Score:
Recipient: ='malcolm@loades.net'>malcolm@redacted
Delivery User: ecaxxxxxx
Delivery Domain: redacted
Delivered To:
Router: central_filter
Transport: fail
Out Time: May 30, 2020, 1:09:13 PM
ID: 1jf0IU-007d87-RS
Delivery Host:
Delivery IP: A valid dotted quad
Size: 4.3 KB
Result: Your email has been detected as SPAM and deleted without being
seen. Should you feel that this is incorrect please resend your email to
='whitelisted1@loades.net'>whitelisted1@redacted. Thank you.
So the rule catches matching emails. It's just that the sender never receives the failure message. Both domains have been tested multiple times from friends on other domains, gmail, gmx etc etc. The failure message is not going into junk/spam or any other folder.
-
Can you show me the filter exactly as it's created?. It should be at /etc/vfilters/domain.tld0 -
Can you show me the filter exactly as it's created?. It should be at
/etc/vfilters/domain.tld
Ah, you got me there :-( I'm a user whose domain is hosted by a hosting company using cPanel. I'm no techie :-( Where and how can I find what you want? If it is of any help here's a screenshot of it in my Global Filters0 -
No worries, this is fine. This shows the filter portions that I need. So based on this and the Track Delivery report it's functioning as intended, I added the failure message to a test filter to make sure I received a bounceback with that text and confirmed it was received. I'd wager that the hosting provider may be able to answer the question on why the bounceback isn't being sent. It seems like there may be some other configuration at play stopping it. 0 -
Thank you, you are spot on! Hosting company number one had an open ticket for this problem for nearly 3 weeks, kept coming back saying to delete and recreate the rule, then claiming it was fixed etc. etc. Finally their 'fix' caused ALL incoming mail to be rejected. I jumped ship and migrated to hosting company number 2 a couple of hours later and mail flowed again. Set up the same rule on hosting company number 2 and still no fail messages received. Raised a ticket with them at same times as raising the issue here. Almost within minutes of your last post they wrote "The reason the bouncebacks are not sending is due to a security rule we have in place that prevents Backskatter Attacks on the mail server." They then made a suggestion "I do have an untested workaround though, set the global filter to forward to another address (bounce@ for example) and set up an autoresponder on that mail address to then send an auto-response to the sender." Hope this may help someone else and thanks for your personal input. Kind Regards 0 -
"The reason the bouncebacks are not sending is due to a security rule we have in place that prevents Backskatter Attacks on the mail server."
I understand this and wanting to avoid Backscatter, but there in my opinion are better ways to manage this. It is not RFC Compliant to *NOT* send bouncebacks to legitimate senders.They then made a suggestion "I do have an untested workaround though, set the global filter to forward to another address (bounce@ for example) and set up an autoresponder on that mail address to then send an auto-response to the sender."
That's a pretty interesting suggestion - I suppose it would work but it could reintroduce the problem they're attempting to avoid, none the less it would serve your purposes I guess. I'm glad they at least provided you with an option.0 -
I understand this and wanting to avoid Backscatter, but there in my opinion are better ways to manage this. It is not RFC Compliant to *NOT* send bouncebacks to legitimate senders. That's a pretty interesting suggestion - I suppose it would work but it could reintroduce the problem they're attempting to avoid, none the less it would serve your purposes I guess. I'm glad they at least provided you with an option.
The suggestion didn't work 'Redirect to email' responded with "To prevent recursive email delivery issues, you cannot use a recipient from a controlling domain in a global delivery filter". Are you able to give me some idea of the better ways to manage this? Something which I may relay to my ISP. Also which RFC covers not sending bouncebacks? Thanks again for your knowledgeable input. I'm learning lots!0 -
I'm sorry to hear it didn't work. I'm not aware of any other workaround you could implement - the RFC's that go over this are as follows: Simple Mail Transfer Protocol Delivery Status/Disposition Notifications including message delivery failure: There are some threads that go over this in detail and while everyone has their own opinions you'll see that I default to RFC Compliance dictates that bounces are sent to valid senders but rejection at SMTP time is preferrable: Ultimately though, none of this you'd really be able to change on your own without root access to the server. 0 -
I'm sorry to hear it didn't work. I'm not aware of any other workaround you could implement - the RFC's that go over this are as follows: Simple Mail Transfer Protocol Delivery Status/Disposition Notifications including message delivery failure: There are some threads that go over this in detail and while everyone has their own opinions you'll see that I default to RFC Compliance dictates that bounces are sent to valid senders but rejection at SMTP time is preferrable: Ultimately though, none of this you'd really be able to change on your own without root access to the server.
Thank you. I may refer my hosting company to this thread.0
Please sign in to leave a comment.
Comments
8 comments