Re: Outlook Express Undeliverable



<parvardigar@xxxxxxxxx> wrote in message
news:1129210387.987591.291730@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Here's a small problem. I have a client (I do know this fellow is
> computer basic) who is able to send his email out to everyone but
> this writer. We're good friends, and most of the exchanges would be
> neutral. He insists that after composing he sends to me the letter
> either as original, or 'reply'. He informs that that everyone receives
> every piece of email he sends, except me. I use a few email address so
> he has several options. I don't get it. Even though he calls me to
> follow up on a crucial message it's best for my records to have a
> 'paper trail' for reference. Any thoughts on this? Thanks
>


If your client is not getting an NDR (non-delivery report) message back from
his mail server (which means his sending mail server got rejected during the
mail session with the receiving mail server, like for an invalid or max'ed
out quota account) or from your mail server (because it improperly sends out
*new* mails as NDRs but *after* the mail session is over) then it doesn't
appear to be a problem on the client's end. The sender isn't getting
anything back saying there was a delivery problem.

Have you used the webmail interface to your server-side mailbox to check its
options? Maybe you have server-side rules defined that moved or deleted his
message. Maybe you have server-side spam filtering enabled and his mails
are getting tagged as spam and either moved into a Junk/Bulk folder or
getting deleted. Maybe you have server-side virus scanning enabled and your
sender is infected so his mails could also be infected. If anything, you
could use the webmail interface to check if the sender's mail ever arrived.
If you see it there but cannot yank it using your local e-mail client then
the problem is local and not a delivery problem between accounts. Have your
client send a test mail to you but make sure your local e-mail client is NOT
running. Then check if their mail arrived by using the webmail interface.

It is possible your e-mail provider has blacklisted the sender or their
domain. Usually this means the mail would either get rejected (if the
receiving mail server was configured properly to reject such mails *during*
the mail session) and the sender gets an NDR back from their own sending
mail server, or your mail provider tags it as spam and moves it out of the
Inbox into a Junk/Bulk folder if you enabled their anti-spam feature. If
your e-mail provider blacklisted the sender, accepted their mail but trashed
it, and never let you get it then you have a very rude and irresponsible
e-mail provider. There is no guarantee that the message is spam. After
all, even if every rule, DNS blacklist, Bayesian weigthing, or other method
to detect spam says it is spam, it is NOT spam if you overtly and
deliberately subscribed to it. YOU define what is spam sent to you, and any
tools or services you employ to battle spam still must comply with YOUR
criteria as to what is and is not spam. If a tool or service tags some
mails as spam, they must not throw them away unless YOU configure or
authorize them to do so.

Any mails that are accepted must be delivered to your mailbox although they
may get moved into folders other than the Inbox. However, mails that are
rejected DURING the mail session are never delivered to you mailbox but the
sender should receive an NDR from their own sending mail server telling the
sender the reason for the in-session rejection, like destination account's
quota is full (their mailbox is full), invalid username, disabled account,
cannot find MX record for sender's mail server, sending mail server uses a
dynamic IP address instead of a static one, etc.). If you cannot find
anything in your mailbox (in any folders defined for it) and you do not have
any server-side rules or spam filtering enabled, it is very possible that
your sender is using rules or filtering to trash any NDRs that they would
have received.

--
__________________________________________________
E-mail: Remove "NIX" and add "#LAH" to Subject.
__________________________________________________


.



Relevant Pages

  • Re: content filtering
    ... opinion on experience that's limited to dealing with domestic US ... Considering that the large majority of spam originates from the US, ... Now all you need is some method of identifying the sender. ... 550 code would come to the attention of the mail server admin who could ...
    (microsoft.public.exchange.admin)
  • Re: Its finally happened...
    ... Most never get through thanks to new smtp technology, ... POP client spam filters are for those who are not mail server admins ...
    (rec.motorcycles)
  • Re: Bounce or discard?
    ... In the one case your mail server simply returns an error code telling ... the sending server that the mail was not accepted, ... in response to inform the sender of the bounce. ... One of the main differences is that in the case of spam with a forged ...
    (uk.net)
  • Re: Where do my emails go?
    ... > The sender gets an NDR. ... I did this because I wasn't 100% sure of all of the client names that I'd ... I periodically examine the mail server logs ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Returning an email to its sender. Is that possible?
    ... How do you know the sender used their own e-mail address? ... will notice the sending mail server DURING the mail session. ... Fake bounces are tantamount to vigilantism. ...
    (microsoft.public.outlook.general)