forwardings to multiple addresses being treated as a single address with a comma
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postfix |
New
|
Undecided
|
Unassigned |
Bug Description
In postfix 2.9.6, we used hundreds of multiple forwardings with wildcards
as the first component, such as "@theidsp-
We are seeing these forwards being treated as a single address.
See these log snippets which show the lookup of the forward
and then the to= being generated with a comma in the address.
Apr 14 10:45:17 mail7-057 sslmx/smtpd[8640]: mail_addr_find: <email address hidden> -> @theidsp-
...
Apr 14 10:45:17 mail7-057 postfix/smtp[8669]: 55E65C895: to=<"<email address hidden>,<email address hidden>>, orig_to=
p.net>, relay=mail7-
A882)
I originally posted this issue about a year ago at https:/
A workaround was amazingly-to-me found by user anx that we could change the first items in our forwards to a single email from a wildcard, so I changed all forwards to use specific addresses such as "<email address hidden>,<email address hidden>" and things worked fine with that workaround.
I intended to post the issue upstream and never got that far since the workaround was working.
So now I am finally doing the right thing.
The workaround does not work for wildcard redirects. For example, I was forwarding "@theidsp.net" to "@theidsp- network. inter-realm. net,<email address hidden>" so Jim would get a copy of any catch-all emails also forwarded to @theidsp- network. inter-realm. net. There is no real workaround in this case because the first component must remain a wildcard to handle catchall emails. So I had to just change to a single address @theidsp- network. inter-realm. net" and Jim just doesn't get a copy.