|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: How to match <> ?
From: Wietse Venema (wietse
porcupine.org)Date: Tue Feb 22 2000 - 07:25:58 CST
- Next message: Wietse Venema: "Re: usernames with
's in them."
- Previous message: Thomas Roessler: "Re: SASL"
- In reply to: Michael J. Maravillo: "Re: How to match <> ?"
- Reply: Wietse Venema: "Re: How to match <> ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Postfix lookup tables do not support null string lookup keys.
Wietse
Michael J. Maravillo:
> On Tue, Feb 22, 2000 at 12:40:35PM +0100, Brad Knowles wrote:
> >
> > The address "<>" is the RFC 821 null envelope sender, and by
> > definition is always valid. It is used to prevent bounces of bounces
> > of bounces of bounces, etc....
> >
> > If it wasn't valid (or allowed) users would not be able to get
> > their bounces, and would never know that their mail to "Freid" has
> > never worked and they should instead be sending mail to "Fred".
> >
> > I wouldn't recommend trying to block this address.
>
> Hi Brad,
>
> And that's what I wanted to happen -- allow MAIL FROM:<>. I
> just don't know what's the "magical" regexp syntax to match
> against it to return an OK from the restriction class. Neither
> works:
>
> /^$/ OK
> /^.?$/ OK
>
> Regards,
> Mike
>
>
>
>
- Next message: Wietse Venema: "Re: usernames with
's in them."
- Previous message: Thomas Roessler: "Re: SASL"
- In reply to: Michael J. Maravillo: "Re: How to match <> ?"
- Reply: Wietse Venema: "Re: How to match <> ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]