1a) Permanent
2) You can achieve this with a combination of rules and autoarchive. That is
of course for the mails that are actually come through the normal filtering
process first. Again; the blocked list is MANUAL filtering and unless you
have a lot of legit addresses marked as blocked it wouldn't have much use.
It would be so much more interesting to get the automatic filtering up. I've
got exactly 0 people in my blocked senders list; I only work with the filter
set to Low and some addresses in my Safe Senders and Safe Recipients list.
On my normal account I receive about 20 Junk E-mails a day and only 1 or 2
actually comes through which I couldn't have been filtered by using a
Blocked List either. On another account I only receive Junk E-mail and use
only the Low setting; it catches most of the time way over 90% of the Junk.
I know this is only a single case but I've seen tons of users (home and
corporate) with the same result. I often check their Blocked List as well
(because you are definitely not the first one who raises this discussion)
and the addresses on it don't make any sense at all and they would get the
same results with no address on that list.
3a) That would be either caused by an expanded distributionlist
(client-side; without an SMTP address of its own), an address generator or
populated by a different list. You can do the same manually. What happens?
The same as always; if the recipient of an e-mail matches with the one in
the list the e-mail will be marked as safe.
3b) Is English your native language? (no offense, it's not mine either)
Microsoft doesn't use any off terminology here. A recipient is what is being
put into the To line and the sender is what is being put in the From line.
This terminology existed already with the regular (snail) mail. There is a
big difference between Safe Sender and a Safe Recipient. Example;
You are on a discussion list called (e-mail address removed). When you send
an e-mail to this address everyone in that list receives the e-mail with you
in From and (e-mail address removed) in To. They reply to that address and
everyone will receive that message with the address who replied in the From
and (e-mail address removed) in the To. Since there are many addresses on
that list and as the list is dynamic (people subscribe and unsubscribe all
the time) keeping up with the Safe Sender list would be a daytime job. As
the To field is always the same putting (e-mail address removed) in your
Safe Recipients list makes sure you will always receive the mail in your
Inbox (as a lot of discussionlists add banners at the bottom the discussion
which could end up in the filter marking it as Junk.
--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003
-----
The Blue Max said:
1a) As mentioned in 1b you can set it to immidiately delete Junk E-mail.
You
can use rules if you want it to only occur for specific senders.
RESPONSE .......... Do you mean to say it permanently deletes the junk
e-mail or does it just place it in the deleted folder for later deletion?
1b) Well there is a lot of things you could do with your spam. Sorting by
junk-score would be fun as well. Then you could list the ones with the
highest score at the top and the lowest score at the bottom. On the other
hand it; these are Junk E-mails for a reason. I wouldn't really want to
bother about how things are sorted in the folder I would be more
interested
in reducing false-positives itself.
RESPONSE .......... I agree with you. The ultimate goal is to improve the
efficiency of the filter so it filters as expected.
2) How would you see this changed?
RESPONSE .......... Why not allow emails, blocked by the 'Blocked Sender'
list, to be sent to a folder of the users choosing? Then allow the user to
set options for that folder that would automatically delete the folder
contents either immediately or at prescribed intervals. As such, the folder
would act as a quasi-deletion box for specific blocked mail. This way both
the 'Junk Email' box and the 'Deleted E-mail' box would both be free of this
type of filtered mail which, by the way, we have confirmed we do not want by
placing it on the block sender's list.
3a) No, the (serverside) distributionlist is actually a SMTP address
itself.
The receiving client doesn't know who else is on this list. This is only
known by the mailserver hosting that SMTP address.
RESPONSE .......... This may be true in some cases, but why do we often see
long lists of recipients in the TO: field of messages sent to us? It would
seem that we are seeing their whole distribution list. What happens when
those emails are saved to the 'Safe Recipients' list?
3b) A Safe Recipient reflects what is being put in the To field by the
sender of the message. Like I said; this could be a (serverside)
distributionlist which has its on SMTP address and you are a memeber of
that
group/list.
RESPONSE .......... So basically you are saying that this is the way you
qualify a 'distribution list' (as opposed to an individual address or
domain)
as a safe sender? Why didn't they simply let you add distribution lists
(e.g. the SMTP address) to the 'Safe Sender's ' list? Why do they call it a
'Safe Recipient' list when you are using it to qualify a safe sender, just
like you are doing with the 'Safe Sender' list? I think many of us, even
many advanced users, are getting confused by the terminology Microsoft uses
here. Perhaps a little technical for most? I don't think most users are
going to grasp the distinctions, let alone the purpose, of some of these
options. Perhaps a very clear, descriptive help section would be useful
here? I'm still a little confused, even after this discussion!
Thanks again!