-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
delivery-whitelist config option does not behave as documented. #5790
Comments
@msteltenpool Thanks for reporting this misleading description. This should indeed be changed. |
Great bug report - thanks for this, it's now fixed! |
Is this back for some reason @weaverryan? We've tried all variations we could find but it seems to be inoperative. It delivery_addresses work perfectly though. |
@ReSpawN What exactly is the behaviour you observe and what did you expect instead? |
@xabbuh Dude, I feel so stupid. After much debugging and checking lines of code, it seems that we we're using a SwiftMailer which was supplied with Symfony 2.8. We've neglected to update it as we then needed to change hundreds of calls to SwiftMailer's Message (used to be newInstance, now anonymous constructed). Thus, it turns out to be a deprecated buggy version. :) |
http://symfony.com/doc/current/reference/configuration/swiftmailer.html#delivery-whitelist
"If set, emails matching any of these patterns will be delivered like normal, instead of being sent to delivery_address."
This is not true, the class Swift_Plugins_RedirectingPlugin sends it to both the white listed recipient address as well as the delivery_address.
You can see that behavior in the previous mentioned class, after it adds the white listed address as recipient, it also adds the default recipient (delivery_address)l.
The text was updated successfully, but these errors were encountered: