Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
fixed bug with return-path#45545
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
mailer info was ignoring return-path setting more info heresymfony#41322
carsonbot commentedFeb 24, 2022
Hey! I see that this is your first PR. That is great! Welcome! Symfony has acontribution guide which I suggest you to read. In short:
Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change. When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor! I am going to sit back now and wait for the reviews. Cheers! Carsonbot |
fabpot commentedFeb 25, 2022
The change has been done on purpose, see#37888 for the explanation. |
cscrewsandcaptains commentedMar 24, 2022
I'm sorry, but I don't understand why in#37888 this change is made. What is wrong with setting the sender via the return path if it is set? Btw other mailers do it this way. |
cscrewsandcaptains commentedMar 30, 2022
In my opinion this will be correct -- first: "sender", second: "return-path", last: "from" |
mailer info was ignoring return-path setting more info here#41322