wietse:
A. Schulze:
wietse:
/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
the regex above don't match on 'RCPT TO: ' ( SPACE
after colon )
That is invalid syntax. What software (other than home-grown
scripts) sends commands like that?
Andr
A. Schulze:
>
> wietse:
> > /^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > /^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE
> after colon )
That is invalid syntax. What software (other than home-grown
scripts) sends commands like that?
Viktor Dukhovni:
> On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
> >
> > wietse:
> > >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
> >
> > the regex above don't match on 'RCPT TO: ' ( SPACE after
> > colon )
>
> Note the extra spac
On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
>
> wietse:
> >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE after
> colon )
Note the extra space violates RFCs 5321, 2821, 821. How
wietse:
/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
the regex above don't match on 'RCPT TO: ' ( SPACE
after colon )
I use now:
/^(RCPT\s+TO:\s*<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:\s*<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
Andreas
Wietse Venema:
> There is a problem with your patch: it turns off forced DSN for all
> SMTP clients that are serviced by the same SMTP daemon process.
Oh, yes, now I see it too. var_force_dsn_on_success is global per process?
My usecases never trigger that situation.
One point more to use your su
Wietse Venema:
> Andreas Schulze:
> >
> > Hello,
> >
> > DSN for successfully deliveries are not enabled by default. They have
> > to be requested
> > by an smtp client using extra parameter on RFC5321.MAILFROM an
> > RFC5321.RCPTTO
> >
> > But not every MUA has the ability to do this. Some y
Andreas Schulze:
>
> Hello,
>
> DSN for successfully deliveries are not enabled by default. They have
> to be requested
> by an smtp client using extra parameter on RFC5321.MAILFROM an RFC5321.RCPTTO
>
> But not every MUA has the ability to do this. Some years ago I had a
> requirement to
>
Hello,
DSN for successfully deliveries are not enabled by default. They have
to be requested
by an smtp client using extra parameter on RFC5321.MAILFROM an RFC5321.RCPTTO
But not every MUA has the ability to do this. Some years ago I had a
requirement to
force DSN on successfully deliverie
