I'd like to create a rule that assigns ie. the red category to all messages
from the domain whatever.com, including all subdomains (so
*@first.whatever.com, *@whatever.com, etc.) I tried to enter "*whatever.com",
but Outlook didn't like it. Can you please help me?

> I'd like to create a rule that assigns ie. the red category to all
> messages from the domain whatever.com, including all subdomains (so
> *@first.whatever.com, *@whatever.com, etc.) I tried to enter
> "*whatever.com", but Outlook didn't like it. Can you please help me?

What didn't it like?

What was the exact text of the rule you created (feel free to redact the
domain name, of course)?

I think you can get away with just putting in whatever.com, but, I'd like
to know what exactly wasn't working.

--
-f.h.

Well, nothing works that's related to wildcard chars. It "did not recognize"
domain.com, *domain.com, and @domain.com. I pressed cancel on the popup, then
finished the rule (it allowed me to create it), but it doesn't work. However,
it accepts your suggestion *@domain.com, but it doesn't work either.
To be able to provide you the exact text of the rule, please tell me how to
do that

"F.H. Muffman" wrote:

> > I'd like to create a rule that assigns ie. the red category to all
> > messages from the domain whatever.com, including all subdomains (so
> > *@first.whatever.com, *@whatever.com, etc.) I tried to enter
> > "*whatever.com", but Outlook didn't like it. Can you please help me?
>
> What didn't it like?
>
> What was the exact text of the rule you created (feel free to redact the
> domain name, of course)?
>
> I think you can get away with just putting in whatever.com, but, I'd like
> to know what exactly wasn't working.
>
> --
> -f.h.
>
>
>

>>> I'd like to create a rule that assigns ie. the red category to all
>>> messages from the domain whatever.com, including all subdomains (so
>>> *@first.whatever.com, *@whatever.com, etc.) I tried to enter
>>> "*whatever.com", but Outlook didn't like it. Can you please help me?
>>>
>> What didn't it like?
>>
>> What was the exact text of the rule you created (feel free to redact
>> the domain name, of course)?
>>
>> I think you can get away with just putting in whatever.com, but, I'd
>> like to know what exactly wasn't working.
>
> Well, nothing works that's related to wildcard chars. It "did not
> recognize" domain.com, *domain.com, and @domain.com. I
> pressed cancel on the popup, then finished the rule (it allowed
> me to create it), but it doesn't work. However,
> it accepts your suggestion *@domain.com, but it doesn't work either.

Strictly speaking, that wasn't my suggestion. My suggestion was simply domain.com.
No @ symbol. No asterisk.

But, taking a look at Outlook, this format should work for you:

Apply this rule after the message arrives
with domain.blah in the sender's address
and on this machine only
move it to the whatever folder.

> To be able to provide you the exact text of the rule, please tell me
> how to do that

Err... type the text that shows up in Rules and Alerts down at the bottom
where it says what the rule is?

--
-f.h.

Entering domain.com as address doesn't work either. But your suggestion to
search for a string in the address helped a bit, now some messages are
categorized as needed, but not all. I think it's because Outlook assigns a
name for ex. John Smith to the address (E-Mail Removed), and when it's searching
for domain.com, it doesn't find it because it sees John Smith. The messages
which doesn't have names assigned, are treated properly. Any workaround?

The rule sounds like this:
Apply this rule after the message arrives with domain.com in the sender's
address, assign it to the blue category.

"F.H. Muffman" wrote:

>
> Strictly speaking, that wasn't my suggestion. My suggestion was simply domain.com.
> No @ symbol. No asterisk.
>
> But, taking a look at Outlook, this format should work for you:
>
> Apply this rule after the message arrives
> with domain.blah in the sender's address
> and on this machine only
> move it to the whatever folder.
>
> > To be able to provide you the exact text of the rule, please tell me
> > how to do that
>
> Err... type the text that shows up in Rules and Alerts down at the bottom
> where it says what the rule is?
>
> --
> -f.h.

Erm.. wait a bit. It works. I just renamed the category, but I didn't update
the rule and therefore I didn't see that it was assigned the category. So the
solution is the "with domain.blah in the sender's address" thing. Thanks for
the help

"F.H. Muffman" wrote:

> >>> I'd like to create a rule that assigns ie. the red category to all
> >>> messages from the domain whatever.com, including all subdomains (so
> >>> *@first.whatever.com, *@whatever.com, etc.) I tried to enter
> >>> "*whatever.com", but Outlook didn't like it. Can you please help me?
> >>>
> >> What didn't it like?
> >>
> >> What was the exact text of the rule you created (feel free to redact
> >> the domain name, of course)?
> >>
> >> I think you can get away with just putting in whatever.com, but, I'd
> >> like to know what exactly wasn't working.
> >
> > Well, nothing works that's related to wildcard chars. It "did not
> > recognize" domain.com, *domain.com, and @domain.com. I
> > pressed cancel on the popup, then finished the rule (it allowed
> > me to create it), but it doesn't work. However,
> > it accepts your suggestion *@domain.com, but it doesn't work either.
>
> Strictly speaking, that wasn't my suggestion. My suggestion was simply domain.com.
> No @ symbol. No asterisk.
>
> But, taking a look at Outlook, this format should work for you:
>
> Apply this rule after the message arrives
> with domain.blah in the sender's address
> and on this machine only
> move it to the whatever folder.
>
> > To be able to provide you the exact text of the rule, please tell me
> > how to do that
>
> Err... type the text that shows up in Rules and Alerts down at the bottom
> where it says what the rule is?
>
> --
> -f.h.
>
>
>