You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eg this affects the way the sender headers get written on outbound emails
This will be a core tracker
The text was updated successfully, but these errors were encountered:
brendanheywood
changed the title
Investigate the shape of an 'inbounce' email sending class
Investigate the shape of an 'inbound' email sending class
Nov 21, 2024
When $CFG->handlebounces is enabled, core does set $mail->Sender = generate_email_processing_address(0, $modargs);
This is showing up in the logs on bounces as the send address (i.e. something like [email protected]), but from what I've seen this isn't making it to the inbound email headers.
This would usually appear in the Return Path, but it seems to be getting replaced somewhere in the chain (most likely by SES) and ending up as 010301433b1eb9ce-9b9edeee-56bb-4c54-86ba-63f45d0e0cfd-000000@example.com. This happens regardless of whether the Sender is the handlebounces address or noreply.
This is good enough for right now, as we are not breaking anything when the inbounce system is not configured. We'll come back to this when we tackle the inbound emails
eg this affects the way the sender headers get written on outbound emails
This will be a core tracker
The text was updated successfully, but these errors were encountered: