allow sender

Hi

Why does this program keep putting up allow or delete sender on received
posts, even when I've allowed and added them to contacts before?
Just an annoyance.


Regards
p.mc

Posts ? As in newsgroup messages ?
- not seeing that at this end with version 2011 for any message on this or
other nttp servers

If 'posts' means email messages
- Does it appear at the top of the message (message window or preview pane)
?
- Is it Yellow(Unknown Sender) or Reddish-Pink(Suspicous) ?
- Does the message contain Html or links ?


--
....winston
msft mvp mail

"p.mc" wrote in message news:ii7m25$h1s$...

Hi

Why does this program keep putting up allow or delete sender on received
posts, even when I've allowed and added them to contacts before?
Just an annoyance.


Regards
p.mc

Hi Winston

Yes.
Windows live mail
File version 15.3502.922
unknown sender...Delete and block / Allow sender (in yellow)

The thing is I'll "Allow" posts from people I know, and add them to my
"Contact" list but still I get the same message above.
Surely this should know not to bug me again. Give me Outlook Express any
day. I suppose they wanted to bundle mail, messenger
and other crap services together. I know much of the layout is like like OE,
but it's also slower on send and receive requests or mail arrival.

Regards
p.mc


"...winston" wrote in message
news:ii7vmm$mdb$...

Posts ? As in newsgroup messages ?
- not seeing that at this end with version 2011 for any message on this or
other nttp servers

If 'posts' means email messages
- Does it appear at the top of the message (message window or preview pane)
?
- Is it Yellow(Unknown Sender) or Reddish-Pink(Suspicous) ?
- Does the message contain Html or links ?


--
....winston
msft mvp mail

"p.mc" wrote in message news:ii7m25$h1s$...

Hi

Why does this program keep putting up allow or delete sender on received
posts, even when I've allowed and added them to contacts before?
Just an annoyance.


Regards
p.mc

On Tue, 1 Feb 2011 12:05:02 -0000, p.mc wrote:

> The thing is I'll "Allow" posts from people I know, and add them to my
> "Contact" list but still I get the same message above.
> Surely this should know not to bug me again. Give me Outlook Express any
> day. I suppose they wanted to bundle mail, messenger
> and other crap services together. I know much of the layout is like like OE,
> but it's also slower on send and receive requests or mail arrival.

Is this related to a Windows Live Hotmail account accessed through Windows
Live Mail? I recall some issue with "Sender Policy Framework" ("SPF"), where
an SPF "fail" will prevent the "Allowed Sender" from sticking. I tested this
with an account which allowed me to "Send as" a different email domain than
the service (i.e., sending "From: ******@excite.com" through Yahoo!
servers). Because Yahoo! is not an "authorized sender" for the domain,
'excite.com', SPF will fail. And the SPF "fail" overrides anything else that
you can do. However, I can't seem to find the proof from the past, when I
was playing with this, and trying to understand it.

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

This is certainly part of it. If you have a programmer's bent, have a look at the SAS.Rule file in the store folder (SAS = 'Spam and
Safety'). It's an XML file that dictates how to deal with the various flags that mail servers attach, including those indicating
failure to pass authentication tests. This is, I think, new to WLMail 2011 and doesn't quite work as intended (flags the sender as
'unknown' for sent messages, for example), but it's taking them a surprisingly long time to get it right.

Ten years or so ago, we were used to seeing program settings stored in .ini files along with the program executable. Then, I think
with the advent of XP (or possibly NT), it became all the rage to store settings in the registry. Now the trend seems to be to put
stuff like this in XML files dotted around the place, where they can be easily updated. Account settings, for example, are now
stored in OEACCOUNT files in the store folder, not in the registry as OE did. Some program parameters are distributed using OECONFIG
files, updated with every sign-in. And now Spam and Safety rules are also distributed in this manner. They'll get it right some day.
--
Noel

"Ildhund" <> wrote in message
news:iia2r4$oa$...
This is certainly part of it. If you have a programmer's bent, have a look
at the SAS.Rule file in the store folder (SAS = 'Spam and Safety'). It's an
XML file that dictates how to deal with the various flags that mail servers
attach, including those indicating failure to pass authentication tests.
This is, I think, new to WLMail 2011 and doesn't quite work as intended
(flags the sender as 'unknown' for sent messages, for example), but it's
taking them a surprisingly long time to get it right.

Ten years or so ago, we were used to seeing program settings stored in .ini
files along with the program executable. Then, I think with the advent of XP
(or possibly NT), it became all the rage to store settings in the registry.
Now the trend seems to be to put stuff like this in XML files dotted around
the place, where they can be easily updated. Account settings, for example,
are now stored in OEACCOUNT files in the store folder, not in the registry
as OE did. Some program parameters are distributed using OECONFIG files,
updated with every sign-in. And now Spam and Safety rules are also
distributed in this manner. They'll get it right some day.
--
Noel
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++

Thanks for the replies. I suppose it’s wait and see then.

Regards
p.mc

It's not any consolation..but checking mail messages(for a Live ID account
@live.com) received in the past and current I also notice the 'yellow'
header(Delete/Block, Allow Sender) for a few senders that **are** present
in my contact list or safe sender list. Those messages have one common type
of source/content...business(e.g. major Hotel) with graphics and html
links.
- I.e. content may have a bearing on the how a message is treated
regardless of contact or safe list configuration...though the same messages
when received in Outlook 2007/2010(with sender safe listed) do not throw up
the same flags.

--
....winston
msft mvp mail

"p.mc" wrote in message news:iid26a$4nj$...

"Ildhund" <> wrote in message
news:iia2r4$oa$...
This is certainly part of it. If you have a programmer's bent, have a look
at the SAS.Rule file in the store folder (SAS = 'Spam and Safety'). It's an
XML file that dictates how to deal with the various flags that mail servers
attach, including those indicating failure to pass authentication tests.
This is, I think, new to WLMail 2011 and doesn't quite work as intended
(flags the sender as 'unknown' for sent messages, for example), but it's
taking them a surprisingly long time to get it right.

Ten years or so ago, we were used to seeing program settings stored in .ini
files along with the program executable. Then, I think with the advent of
XP
(or possibly NT), it became all the rage to store settings in the registry.
Now the trend seems to be to put stuff like this in XML files dotted around
the place, where they can be easily updated. Account settings, for example,
are now stored in OEACCOUNT files in the store folder, not in the registry
as OE did. Some program parameters are distributed using OECONFIG files,
updated with every sign-in. And now Spam and Safety rules are also
distributed in this manner. They'll get it right some day.
--
Noel
++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++

Thanks for the replies. I suppose it’s wait and see then.

Regards
p.mc