"Gordon" wrote in message news:fe0gd5$c7p$(E-Mail Removed)...
> "VanguardLH" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> "Blueprint" <(E-Mail Removed)> wrote in message
>> news:1740CB05-AB8E-4A9A-BB28-(E-Mail Removed)...
>>> Sorry not to add that all computers are using XP Home (Sp2). Only
>>> my computer
>>> has Office 2007, the others have Works and will still use Outlook
>>> Express.
>>> The Accounts are from the ISP Freeserve/Orange so basically the
>>> same Account
>>> but with a different name before the '@' symbol.
>>
>> I am not personally familiar or use Freeserve. Do they provide
>> separate e-mail accounts for each user (i.e., the name before the
>> at-symbol)? Or do they only provide one mailbox that is shared
>> amongst multiple users?
>
> All the "different" email accounts provided by Freeserve (Wanadoo
> that was and is now Orange AFAIK) are in fact just aliases of the
> one master email address. they are in the format of
> (E-Mail Removed) and there used to be a workaraound
> when it was actually Freeserve (don't know whether it will work now)
> whereby in the Username in the account setup in the email client you
> could put the following:
> "username.freeserve.co.uk + myname" (without the quotes) and that
> would ONLY download email for the "myname" alias.
>
> HTH
>
Then Blueprint has no way to separate users that are accessing the
same mailbox. They get different usernames along with a password to
validate they have rights to use the e-mail provider's service but
they are all sharing the same mailbox. They are getting just one
e-mail account (i.e., just one mailbox).
The provider might have used the "+ myname" method to differentiate
between the mailbox items but apparently that's not true anymore or
stopped working. That trick only works at the server end because the
user is adding a trigger string to the username. E-mail clients don't
care about the usernames in the e-mail addresses included in the
headers of the actual mailbox items (for one, they aren't used to
deliver the mails, and for two, they can be bogus). They issue a LIST
command to find out if there are any items in the mailbox (which you
are sharing) and a UID command to get the unique ID of each one (so
your e-mail client can tell if it downloaded that item already or if
it is new). Only after the e-mail client has issued LIST and UID to
figure what new items are in the [shared] mailbox and after all those
new items have been downloaded can an e-mail client inspect the
headers to see what username was used in the To or Cc headers (but
cannot test against the Bcc header since it isn't in the received copy
of mails). That would be too late because now all new items have been
downloaded and other sharing the same mailbox won't get their
messages.
Blueprint is screwed in using a shared mailbox. If their "trick" of
modifying the username won't cause the mail server to list and deliver
mail items only for the specified username or trigger string, the
e-mail client can't do anything to separate them up at the mail server
and all items end up getting downloaded. Blueprint will need to get
REAL e-mail accounts so each of his user's mailboxes are separate from
every other user's mailbox.
Even if the trigger string still works (i.e., Blueprint got the
username syntax correct in Outlook and Outlook Express), Outlook
functions differently than Outlook Express. Outlook first downloads
all mail items before any rules can be exercised against them.
Outlook Express can look at some info for a mail item and then decide
whether or not to download it. The trigger string mechanism used by
Freeserve probably won't work with any e-mail client that first yanks
the mail and then interrogates it.