Unfortunately we didn't fix it yesterday :)
But now it seems to work with this regex:
\N^(.*)@tmn_00.telchoi.alcatel.be(.*)$\N $1@???$2 S
Note that it didn't work out with leading and trailing <> only.
What I don't understand is that when I put the following regex:
\N^(.*)@tmn00.telchoi.alcatel.be$\N $1@??? S
the address is correctly rewritten (with "RCPT TO: <ddts@???>" of course)
Anyway, it's solved now, much thanks
On Thu, 22 Jun 2006 09:17:00 +0100 (BST)
Philip Hazel <ph10@???> wrote:
> On Thu, 22 Jun 2006, Renaud Allard wrote:
>
> > Well, as it seems the rewriting doesn't take place before the syntax check
> > Here is the log with -d+all
> >
> > rcpt to: <ddts@tmn_00.telchoi.alcatel.be>
> > 09:35:55 23708 SMTP<< rcpt to: <ddts@tmn_00.telchoi.alcatel.be>
> > 09:35:55 23708 expanding: \N^(.*)@tmn_00.telchoi.alcatel.be$\N
>
> I thought we fixed this yesterday? You need to include the < and > in
> the pattern. And in the test you have given, you might need to include a
> leading space as well. Note that the standard for the RCPT command is
>
> RCPT TO:<xxx@yyy>
>
> with no space between : and < (though many programs, including Exim,
> allow it). I can't remember whether the S rewriter strips leading
> whitespace or not.
>
> --
> Philip Hazel University of Cambridge Computing Service
> Get the Exim 4 book: http://www.uit.co.uk/exim-book
--
.O.
..O
OOO
PGP key:
http://www.llorien.org/gnupg/key.pub
Insanity: doing the same thing over and over again and expecting different results.
- Albert Einstein
