Outlook's bad design

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

Outlook is sending email messages that never
reach the recipient and no error message ever
comes back to outlook.

This is horrible design. Why does anyone use
this Microsoft crap?

Unfortunately, we have someone that insists on
using it which is a headache.
 
Hi Tom,

Did the recipient check his or her spam folder or is there any chance
the recipient might have spam automatically deleted? Generally when
Outlook sends an email and you don't get an error message, the problem
is not with the sending Outlook.
Can you give us details about your configuration (which Outlook version,
email acct type, etc) as well as details on what you do when you
encounter the issue?

Patrick Schmid
 
What kind of server are you using? This would be an issue with the SMTP
server, not Outlook. Using Exchange, I get either non-delivery reports or
delayed delivery reports, depending on the recipient's server status.
 
As others have stated, this has nothing to do with Outlook. This is just how
email works. You only get a NDR if 1) the remote system confirms delivery
failures and 2) the email actually didn't reach the destination. Lots of
mail servers these days are saying to hell with RFC compliance and just
ignoring NDR's because spam is out of control.

You really shouldn't come to a Microsoft-provided support group slamming
Microsoft without any basis or any idea of what's going on.
 
Tom said:
Outlook is sending email messages that never
reach the recipient and no error message ever
comes back to outlook.

This is horrible design. Why does anyone use
this Microsoft crap?

Unfortunately, we have someone that insists on
using it which is a headache.
Click to expand...


It is not Microsoft's responsibility for problems with YOUR e-mail
provider. No e-mail client can control what happens after it passes off
the e-mail to the mail server. It is not Microsoft's responsibility
that the recipients have chosen to use anti-spam filters or rules to
eliminate getting YOUR crap. It is not Microsoft's responsibility to
control the receiving mail server to enforce any error notices to be
returned. You have clearly exposed your ignorance as to how e-mail
works. So how does someone else wanting to use Outlook then force YOU
to use Outlook?
 
Tom said:
Outlook is sending email messages that never
reach the recipient and no error message ever
comes back to outlook.

This is horrible design. Why does anyone use
this Microsoft crap?
Click to expand...

It's not Microsoft's design that's causing the problem. It's the poor
design of one of the servers sitting between you and your client.
 
Brian said:
It's not Microsoft's design that's causing the problem. It's the poor
design of one of the servers sitting between you and your client.
Click to expand...

I think the problem is that no message pops up of SMTP server can not be reached
or mail can not be delivered for some other reasons by the SMTP server you
connect to. The Error icon on the bottom (statusbar?) is really not noticeable.
I was really surprised to see a message I thought I had sent a few days ago
still in my outbox just because SMTP server was unavailable (and I had to use
second one).

Siim Karus
 
The configuration that did not return error messages
was as follows:

Outlook 2002

2 Profiles

One of the profiles was set up previously to use
MS exchange server. A second profile was
added using SMTP and pop3. Under the mail
icon, MS exchange was set up as the default mail
service.

Mail leaving the second profile using smtp and pop3
would not be delivered and no error messages ever
were received. It was particularly difficult to
troubleshoot this problem because it would only
not be delivered sporadically.

Sometimes Outlook would deliver mail, but usually it
wouldn't.
 
Did you try troubleshooting with a different email client and the same
SMTP/POP configuration? If yes, what was the result?

Patrick Schmid
 
All different email clients work perfectly.
Making the smtp/pop configuration the default
under the mail icon in Windows XP
apparently solved the problem. Although
there are still doubts, will advise.

Outlook was sporadically sending mail to its
own/senders address.
 
If other email clients with the same configuration work fine from the
same computer, then Outlook shouldn't have any problems either.
The messages were always explicitly sent with the SMPT acct and couldn't
have accidentally ended up with the Exchange acct?

Patrick Schmid
 
Are you using an outgoing email scan from an anti-virus program? Sending to
a black hole is a known bug that can happen if that's the case. The A-V
software replaces the server IP's with it's own, usually a LocalHost
setting. Outlook delivers the email there, the A-V server accepts it and
while it's scanning the email the server connection times out. The A-V
software doesn't check this, it just sends out to nothing and Outlook
doesn't know that. If that's the case disable outgoing email scanning, it's
useless anyway.
 
Back
Top