postal: Return Path detection for "system" domain doesn't work
when I create new domains in postal the DNS check detects if there is a return path. This doesn’t work for the domain that postal has in the dns settings of the postal.yml. Below are the DNS query answers (in redacted form) for different domains.
This is a return path that postal detects:
;QUESTION psrp.someotherdomain.com. IN MX ;ANSWER psrp.someotherdomain.com. 299 IN CNAME rp.postal.service.systemdomain.com. rp.postal.service.systemdomain.com. 299 IN MX 10 mx.postal.service.systemdomain.com.
This is a return path that postal doesn’t detect:
;QUESTION psrp.systemdomain.com. IN MX ;ANSWER psrp.systemdomain.com. 299 IN CNAME rp.postal.service.systemdomain.com. rp.postal.service.systemdomain.com. 299 IN MX 10 mx.postal.service.systemdomain.com.
This is the dns config in my postal.yml:
mx_records: - mx.postal.service.systemdomain.com smtp_server_hostname: postal.service.systemdomain.com spf_include: spf.postal.service.systemdomain.com return_path: rp.postal.service.systemdomain.com route_domain: routes.postal.service.systemdomain.com track_domain: track.postal.service.systemdomain.com helo_hostname: # By default, this will be the same as the
smtp_server_hostnamedkim_identifier: postal domain_verify_prefix: postal-verification custom_return_path_prefix: psrp
my postal is on commit 9a76538f
Is this behavior in postal a problem, or is this just a minor bug? Did I made something wrong in the postal.yml?
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Reactions: 1
- Comments: 39 (20 by maintainers)
Everything should work, it’s just the verification that’ll be broken. Hopefully CloudFlare will fix that soon.
I used “postal auto-upgrade” and for the moment my return path setting is still grey.
Config: dns:
Specifies the DNS record that you have configured. Refer to the documentation at
https://github.com/atech/postal/wiki/Domains-&-DNS-Configuration for further
information about these.
mx_records: - mx.postal.borezo.info smtp_server_hostname: postal.borezo.info spf_include: spf.postal.borezo.info return_path: rp.postal.borezo.info route_domain: routes.postal.borezo.info track_domain: track.postal.borezo.info dkim_identifier: postal domain_verify_prefix: postal-verification custom_return_path_prefix: psrp
Messages sent to a return path can only be linked back to an original message if the bounce includes the message ID of the original message. Linking actual bounces back to their original message is a little tricky and the current method isn’t ideal. An alternative is sending every message from it’s own address but this can cause delays with greylisting.