I'm thinking of adding this email filer, but could someone please
explain how to interpret {@?.+\.no} ?
--------------------
Example 1: You might use the following expression to automatically file
known mailing lists and company domains addressed specifically to you.

[>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}

Everything else from the abroad or domestic not specifically addressed
to you remains in >Unfiltered, which might be the default Inbox.
--------------------

Terry

On Sun, 04 Jul 2021 15:04:49 +0100, Terry Pinnell
<me@somewhere.invalid> wrote:

>I'm thinking of adding this email filer, but could someone please
>explain how to interpret {@?.+\.no} ?

The expression will match a sequence of
one or zero '@' characters
followed by a sequence of
one or more characters (any characters)
followed by the sequence (not case sensitive)
'.no'

The above sequence can be anywhere in the address (or whichever field
it is applied to). It need not be at the beginning or end.

So things like
abc.no
and
@1234567890.NO
as well as
John Smith esq.notary

--
Remove del for email

Barry Schwarz <schwarzb@delq.com> wrote:

>On Sun, 04 Jul 2021 15:04:49 +0100, Terry Pinnell
><me@somewhere.invalid> wrote:
>
>>I'm thinking of adding this email filer, but could someone please
>>explain how to interpret {@?.+\.no} ?
>
>The expression will match a sequence of
> one or zero '@' characters
>followed by a sequence of
> one or more characters (any characters)
>followed by the sequence (not case sensitive)
> '.no'
>
>The above sequence can be anywhere in the address (or whichever field
>it is applied to). It need not be at the beginning or end.
>
>So things like
> abc.no
>and
> @1234567890.NO
>as well as
> John Smith esq.notary

Thanks Barry, understood.

Terry

On Sun, 04 Jul 2021 15:04:49 +0100, Terry Pinnell wrote:

> I'm thinking of adding this email filer, but could someone please
> explain how to interpret {@?.+\.no} ?
> --------------------
> Example 1: You might use the following expression to automatically file
> known mailing lists and company domains addressed specifically to you.
>
> [>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}
>
> Everything else from the abroad or domestic not specifically addressed
> to you remains in >Unfiltered, which might be the default Inbox.
> --------------------
>
> Terry

It will match a string containing ‘.no’, except when the ‘.no’ only occurs
at the very beginning of the string. It is also case-insensitive, so it
will (for example) match the string <Chuck.Norris@hollywood.invalid>.

The Any-Sender: will look for a match in any of these headers:
From
Apparently-From
Sender
Reply-To
X-Sender

The ‘@?’ is worthless in this filter, and the ‘.+’ might as well be ‘.’.
That is,

Any-Sender: {@?.+\.no}

will match the same as

Any-Sender: {.\.no}

--
Kind regards
Ralph

Terry Pinnell schrieb:

> I'm thinking of adding this email filer, but could someone please
> explain how to interpret {@?.+\.no} ?

I don't think that expression makes much sense.

It will match a (sender) header containing "\.no" somewhere with at
least one, but possibly many characters before that, and before them
an "@" sign - or no "@" sign.

Ralph Fox <-rf-nz-@-.invalid> wrote:

>On Sun, 04 Jul 2021 15:04:49 +0100, Terry Pinnell wrote:
>
>> I'm thinking of adding this email filer, but could someone please
>> explain how to interpret {@?.+\.no} ?
>> --------------------
>> Example 1: You might use the following expression to automatically file
>> known mailing lists and company domains addressed specifically to you.
>>
>> [>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}
>>
>> Everything else from the abroad or domestic not specifically addressed
>> to you remains in >Unfiltered, which might be the default Inbox.
>> --------------------
>>
>> Terry
>
>
>It will match a string containing ‘.no’, except when the ‘.no’ only occurs
>at the very beginning of the string. It is also case-insensitive, so it
>will (for example) match the string <Chuck.Norris@hollywood.invalid>.
>
>
>The Any-Sender: will look for a match in any of these headers:
> From
> Apparently-From
> Sender
> Reply-To
> X-Sender
>
>
>The ‘@?’ is worthless in this filter, and the ‘.+’ might as well be ‘.’.
>That is,
>
> Any-Sender: {@?.+\.no}
>
>will match the same as
>
> Any-Sender: {.\.no}

A very odd example IMO, from

Help > Email filters > Expression Example Help

"Example 1: You might use the following expression to automatically file
known mailing lists and company domains addressed specifically to you.

[>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}

Everything else from the abroad or domestic not specifically addressed
to you remains in >Unfiltered, which might be the default Inbox.

Red part: This means "match if there is an @ (at symbol), or even if
there isn't one".

Terry

On Sun, 04 Jul 2021 22:17:09 +0100, Terry Pinnell wrote:

> A very odd example IMO, from
>
> Help > Email filters > Expression Example Help
>
> "Example 1: You might use the following expression to automatically file
> known mailing lists and company domains addressed specifically to you.
>
> [>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}
>
> Everything else from the abroad or domestic not specifically addressed
> to you remains in >Unfiltered, which might be the default Inbox.
>
> Red part: This means "match if there is an @ (at symbol), or even if
> there isn't one".
>
> Terry

That is only an outline. The key point is the boolean logic.
You still need to configure it for your specific mailing list.

Let us suppose emails forwarded to you from your mailing list all have
headers like these

To: <tpinnell@somewhere.invalid>
Sender: Ecky Thump Mailing List <lists@eckythump.uk>
Reply-To: Ecky Thump Mailing List <lists@eckythump.uk>

then you could use the following filter expression:

To: tpinnell AND Any-Sender: <lists@eckythump.uk>

But if emails forwarded to you from your mailing list all have
headers like these:

To: <lists@eckythump.uk>
Sender: Ecky Thump Mailing List <lists@eckythump.uk>
Reply-To: Ecky Thump Mailing List <lists@eckythump.uk>

then the above filter expression is not going to work because the
filter expression doesn't match the "To:" field.

--
Kind regards
Ralph

Ralph Fox <-rf-nz-@-.invalid> wrote:

>On Sun, 04 Jul 2021 22:17:09 +0100, Terry Pinnell wrote:
>
>> A very odd example IMO, from
>>
>> Help > Email filters > Expression Example Help
>>
>> "Example 1: You might use the following expression to automatically file
>> known mailing lists and company domains addressed specifically to you.
>>
>> [>Inbox] To: jsmith AND Any-Sender: {@?.+\.no}
>>
>> Everything else from the abroad or domestic not specifically addressed
>> to you remains in >Unfiltered, which might be the default Inbox.
>>
>> Red part: This means "match if there is an @ (at symbol), or even if
>> there isn't one".
>>
>> Terry
>
>
>That is only an outline. The key point is the boolean logic.
>You still need to configure it for your specific mailing list.
>
>Let us suppose emails forwarded to you from your mailing list all have
>headers like these
>
> To: <tpinnell@somewhere.invalid>
> Sender: Ecky Thump Mailing List <lists@eckythump.uk>
> Reply-To: Ecky Thump Mailing List <lists@eckythump.uk>
>
>then you could use the following filter expression:
>
> To: tpinnell AND Any-Sender: <lists@eckythump.uk>
>
>
>But if emails forwarded to you from your mailing list all have
>headers like these:
>
> To: <lists@eckythump.uk>
> Sender: Ecky Thump Mailing List <lists@eckythump.uk>
> Reply-To: Ecky Thump Mailing List <lists@eckythump.uk>
>
>then the above filter expression is not going to work because the
>filter expression doesn't match the "To:" field.

Thanks Ralph, that's going to be very helpful.

Terry

On Sun, 04 Jul 2021 18:54:06 +0200, in
<auof.20210704185403.1658@scatha.ancalagon.de>, Thomas Hochstein
<thh@thh.name> wrote:

>Terry Pinnell schrieb:
>
>> I'm thinking of adding this email filer, but could someone please
>> explain how to interpret {@?.+\.no} ?
>
>I don't think that expression makes much sense.

Neither do I.

>It will match a (sender) header containing "\.no" somewhere with at
>least one, but possibly many characters before that, and before them
>an "@" sign - or no "@" sign.

Assuming it's meant to delete all mail from
anyone@howevermanycharacters.no
meaning everything from an email address ending with the ".no" TLD,
I'd change it to the following

{@.+\.no$}

--
Jim H