On Tue, 9 Aug 2022, Olaf Hopp (SCC) via Exim-users wrote:
Dear collegues,
we moved some internal domains from "olddomain.org" to "newdomain.org"
we have internal routing for the new and old domain
Now we want to get rid of the routing for "olddomain.org"
and I want to rewrite "olddomain.org" to "newdomain.org"
so "[email protected]" should become "[email protected]"
In my rewrite section of exim I use
^(.*)@(.*)\.olddomain\.org $1@$2.newdomain.org TS
which seems to run fine:
# exim -brw [email protected]
2022-08-09 16:18:28 "[email protected]" from smtp sender rewritten as
"[email protected]" by rule 1
SMTP: [email protected]
sender: [email protected]
from: [email protected]
to: [email protected]
cc: [email protected]
bcc: [email protected]
reply-to: [email protected]
env-from: [email protected]
2022-08-09 16:18:28 "[email protected]" from env-to rewritten as
"[email protected]" by rule 1
env-to: [email protected]
However, when I activate this, I see the following in my logs:
2022-08-09 15:59:22 Rewrite of <[email protected]> yielded unparseable
address: '>' missing at end of address in address <[email protected]
and my routing fails since I have removed the routing for "olddomain.org"
So I modified my rewriting rule to
^(.*)@(.*)\.olddomain\.org $1@$2.newdomain.org> TS
(note the '>') Now it works as expected !?
Anyway with this, I'll get
# exim -brw [email protected]
2022-08-09 16:24:33 Rewrite of [email protected] yielded unparseable
address: malformed address: > may not follow [email protected] in address
[email protected]>
sender: [email protected]
from: [email protected]
to: [email protected]
cc: [email protected]
bcc: [email protected]
reply-to: [email protected]
env-from: [email protected]
2022-08-09 16:24:33 Rewrite of [email protected] yielded unparseable
address: malformed address: > may not follow [email protected] in address
[email protected]>
env-to: [email protected]
What is going wrong here ?
Exim version 4.94.2 under Debian 11 (Bullseye)
You have:
^(.*)@(.*)\.olddomain\.org $1@$2.newdomain.org TS
The examples suggest that:
*@*olddomain.org $1@$2.newdomain.org TS
would be sufficient.
In particular I doubt that you need the anchoring "^".
Perhaps the extending patterns are forcing $1 to include
the opening "<", so that the matching ">" is never removed ?
This does seem like a bug though.
--
Andrew C. Aitchison Kendal, UK
[email protected]
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
