On Thu, 6 Nov 2003, Philip Hazel wrote:
> A little while ago, on Thu, 6 Nov 2003, I wrote:
>
> > > I want to use a rewrite rule like
> > >
> > > postmaster@??? <> F
> > >
> > > i.e. mail sent with a postmaster@??? address should be regarded as
> > > a bounce message with null sender, subject to ignore_bounce_errors_after,
> > > for example.
> > >
> > > However, if I do this, then exim dies (core dump) after the To: address
> > > in the SMTP conversation.
> >
> > I cannot reproduce this problem with Exim 4.24. Are you using 4.24? If
> > so, please can you send me more details of exactly what you do to cause
> > the error.
>
> Ooops. Apologies. You had previously sent me more details - namely that
> it was during a sender verify that this crash happens. I just hadn't
> remembered that when I was working my way through the Exim work list.
>
> Time to take a break and go home, I think....
Aha! I'm not mad! Someone else is seeing this problem as well. It took
me 3 weeks to figure out why mailman wasnt able to send mail that
catches a rewrite rule with flags FS set, that was rewriting to null
sender.
I was about to send the below. Hoping this can be fixed soon in a 4.25
release, as I will have to wait for the 'control panel' vendor we use
(which micromanages the entire server) to update the exim version they
use before I will see it on the relevant servers.
--
-
- I seem to have found a bug in 4.24
-
- Im trying to use the following rule (Ive tried variations as well) to
- force a null
- envelope sender in certain conditions:
-
- ^<.*@$primary_hostname> "<>" FS
-
- partial transcript of exim -bh session:
-
- LOG: Rewrite of <xxx@???> yielded unparseable address:
- missing or
- malformed local part in address <>
- 250 OK
-
- (After the RCPT TO, exim segfaults)
-
--
