Outlook 2003 sending msgs that aren't there

[hmc]

Hi, I just installed Outlook 2003. So far it's been fine, but this
morning,
it's been trying to send 6 msgs from my Yahoo acct--and not succeeding.
Funny thing is that there are no msgs in the outbox. And I didn't even
create any msgs to send.

I did do that "test account settings" a few times, but those went out just
fine. Anyone have any ideas what's going on? I can't send anything out
from
my Yahoo b/c these 6 invisible, non-existent "msgs" are in the way.

 

[Brian Tillman]

Hi, I just installed Outlook 2003. So far it's been fine, but this
morning,
it's been trying to send 6 msgs from my Yahoo acct--and not
succeeding. Funny thing is that there are no msgs in the outbox. And
I didn't even create any msgs to send.

Possible read receipts. See http://www.outlook-tips.net/howto/delete_rr.htm

 

[hmc]

THANK YOU, Brian. I don't know what read receipts are (I'm assuming they are
emails that I received which demand a receipt indicating they've been read),
but the suggestion on this page fixed it. So thank you. It was driving me
crazy. Not a nice way to christen Outlook 2003 on this machine.

 

[Guest]

THANK YOU, Brian. I don't know what read receipts are (I'm assuming
they are
emails that I received which demand a receipt indicating they've been
read),
but the suggestion on this page fixed it. So thank you. It was driving
me
crazy. Not a nice way to christen Outlook 2003 on this machine.

No, they are read receipts that YOU sent. You either optioned to ask
for a read receipt when you composed an e-mail or you have your e-mail
client configured to always ask for a read receipt when you send
e-mails. You should turn that option off if it is on.

 

[Brian Tillman]

No, they are read receipts that YOU sent.

I agree with this

You either optioned to ask
for a read receipt when you composed an e-mail or you have your e-mail
client configured to always ask for a read receipt when you send
e-mails. You should turn that option off if it is on.

I disagree with this. Receipts are the response to receipt requests, the
sending of which is controlled on the sender (remote) side. The OP's
Outlook received a receipt request and queued a receipt for delivery based
on the setting in the bottom part of the tracking options dialogue box
(i.e., the "Use this option to decide how to respond to requests..." part).

 

[Guest]

No one has asked if he is using Yahoo paid POP mail. Outlook can't be used
with Yahoo free web mail. Test Settings button actually sends an email. If
you don't actually receive the test email, it's not working.

 

[Guest]

No one has asked if he is using Yahoo paid POP mail. Outlook can't be
used
with Yahoo free web mail. Test Settings button actually sends an
email. If
you don't actually receive the test email, it's not working.

For normal messages in the Outbox attempting to go to a non-existent
server, those messages would still be visible in the Outbox even when
the e-mail client errors if it cannot connect to a mail server. The OP
may be using a paid Yahoo Mail account and have POP3 access. The OP may
be using YahooPOPs with a freebie Yahoo Mail account to give POP3-like
access to the e-mail client. In either case, if the e-mail client
cannot connect to a mail server, the e-mail stays in the Outbox and it
is not hidden.

When sending an e-mail with a read receipt request, the
Disposition-Notification-To header gets added to that outbound e-mail.
This alerts the recipient's e-mail client that a read receipt was
requested (which can then decide on what to do about it: ignore, prompt,
reply).

The e-mail which had the read receipt option enabled (to add the
Disposition-Notification-To header) goes out through the Outbox. The
recipient gets the e-mail with its header noting a read receipt is
requested. In this case, say the recipient's e-mail client sends back
an acknowledgement. The sender now gets an inbound e-mail which is the
acknowledgement. Wouldn't the inbound acknowledgement e-mail get stuck
in the Inbox (instead of the Outbox)? And why would the sender's e-mail
client get stuck trying to send a message that it must have already
successfully sent if the acknowledgement is now coming back? If
anything, it would get "stuck" on trying to PULL the acknowledgement
e-mail from the POP3 (inbound) mail server, not when trying to PUSH new
e-mails out.

I would think that if the problem is with the e-mail client continually
retrying to *send* a message that is hidden in the *Outbox* then it is
the original outbound e-mail with the Disposition-Notification-To header
(i.e., the outbound e-mail that wants to issue the request to the
recipient ) that is causing the sticking. The help article to which
Brian linked says, "If you have read receipts that won't send, ...". So
the sticking is caused by:

- An outbound e-mail.
- That has the Disposition-Notification-To header added (to alert the
recipient of the request).
- And which is supposed to pass through the Outbox folder.

So what is getting stuck in the Outbox is the outbound e-mail with read
receipt *request*. It isn't for the acknowledgement being returned, if
ever. You may never get the acknowledgement but that doesn't fix the
prior problem of Outlook getting stuck trying to send the request. The
options on how to handle acknowledgements (ignore, prompt, reply) do not
apply because this is an outbound e-mail with the request, not an
inbound e-mail with the acknowledgement. Getting Outlook unstuck means
losing the e-mail message that you intended to send in the first place.

 

[Brian Tillman]

I would think that if the problem is with the e-mail client
continually retrying to *send* a message that is hidden in the
*Outbox* then it is the original outbound e-mail with the
Disposition-Notification-To header (i.e., the outbound e-mail that
wants to issue the request to the recipient ) that is causing the
sticking. The help article to which Brian linked says, "If you have
read receipts that won't send, ...". So the sticking is caused by:

- An outbound e-mail.
- That has the Disposition-Notification-To header added (to alert the
recipient of the request).
- And which is supposed to pass through the Outbox folder.

So what is getting stuck in the Outbox is the outbound e-mail with
read receipt *request*.

And, again, I disagree. The read receipt request was part of some inbound
message. The OP's Outlook created a read receipt to send in response,
placed it in the Outbox (hidden), and there it got stuck. Now, I may not
have a complete understanding of how recipt requests and receipts work, but
this is my impression of what is happening.

 

[Guest]

And, again, I disagree. The read receipt request was part of some
inbound message. The OP's Outlook created a read receipt to send in
response, placed it in the Outbox (hidden), and there it got stuck.
Now, I may not have a complete understanding of how recipt requests
and receipts work, but this is my impression of what is happening.

So you're thinking the OP got an inbound e-mail that had the
Disposition-Notification-To header in it (i.e., the OP got an e-mail
with a read receipt request), Outlook saw that header, the Tracking
settings in Outlook were configured to automatically reply to the
request, and it is the outbound acknowledgement that gets Outlook stuck.
That would only occur if the OP had Outlook configured to automatically
reply to inbound read receipt requests. If Outlook were configured to
Prompt then the OP should have mentioned the prompt appearing before
Outlook got stuck (if he remembered that there was a prompt). If
Outlook is configured to ignore the request then no acknowledgement
would get constructed for an outbound e-mail. It also means that the OP
received an inbound e-mail (the one with the Disposition-Notification-To
header) in his Inbox. We don't know if the OP got a new message in
their Inbox just before Outlook got hung up.

Knowing how Outlook is configured regarding its action regarding read
receipts would help. I don't remember what is the default setup for
read receipt handling; I always have my Outlook configured to ignore
them. Knowing if one of the messages that showed up in the Inbox (or
wherever it got moved) had the Disposition-Notification-To header would
help. Unfortunately, Outlook's "advanced find" isn't that advanced so
you cannot scan e-mails for a particular header that Outlook hasn't been
preprogrammed to recognize. In the advanced tab of Advanced Find, under
the All Mail fields selection for which field to search within, there is
a Receipt Requested selection (geez, you'd think they would actually use
the REAL header names). Maybe that one will match on
Disposition-Notification-To, so you could define an advanced search to
look for "Receipt Requested equals Yes" or just on "Receipt Requested
exists" (if the header was No then there would be no point in including
it, so it is almost always set to Yes).

 

[The Dowd's]

I am curious, I have a Yahoo free account, when I try to email from my yahoo
account to my email account I use outlook for I never get the yahoo mail,
(from myself or anyone with yahoo account. Is this an outlook problem then
? I 've been trying to figure this out.

 

[Guest]

Hi, I just installed Outlook 2003 this week and have been having problems
with accepting senders requests for a "read receipt". I have the setting in
OL 2004 to "allow me to choose" when to send a receipt and everytime I accept
to send a receipt, it hangs in limbo waiting to send. It tries all my
accounts, until it finally sends using one of my accts. Microsoft phone tech
supp was totally useless about this topic. But, after getting totally
frustrated today, I did some more digging on the error I received today and
found the following MS article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;836491#toc

Apparently, this may be what is happening to me. Can anyone offer any help
about MS Exchange 2000? If I'm correct, this is a program that I have on my
pc that works with OL 2003? (mpc67 - at - yahoo dot com)

 

[Brian Tillman]

I am curious, I have a Yahoo free account, when I try to email from
my yahoo account to my email account I use outlook for I never get
the yahoo mail, (from myself or anyone with yahoo account. Is this
an outlook problem then ?

Probably not. Outlook isn't actually receiving the mail for your non-Yahoo!
account, the mailbox hosted by the ISP for that account is. What Outlook is
doing is downloading the mail from that mailbox to your local machine.

One thing you can try is to see if your mailbox receives the Yahoo! messages
by using a web interface to examine the mailbox. If the messages aren't
there, then it's obviously not an Outlook problem. If they are there and
Outlook doesn't download them during a send/receive, then it would, at first
glance, seem to be an Outlook problem. If this latter happens and you have
an anti-virus or -spam scanner integrated with Outlook, then I'd disable
that and check again.

 

[Brian Tillman]

Hi, I just installed Outlook 2003 this week and have been having
problems with accepting senders requests for a "read receipt". I have
the setting in OL 2004 to "allow me to choose" when to send a receipt
and everytime I accept to send a receipt, it hangs in limbo waiting
to send. It tries all my accounts, until it finally sends using one
of my accts. Microsoft phone tech supp was totally useless about this
topic. But, after getting totally frustrated today, I did some more
digging on the error I received today and found the following MS
article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;836491#toc

Apparently, this may be what is happening to me. Can anyone offer any
help about MS Exchange 2000? If I'm correct, this is a program that
I have on my pc that works with OL 2003? (mpc67 - at - yahoo dot com)

Exchange won't reside on your PC. Exchange is a server program that would
host your mailbox to which Outlook would connect to view the mail. You
would know if your account is an Exchange account, at the very least by
examining Tools>E-mail Account>Next.

I think it's a better chance that the account Outlook is trying to use to
send the receipts is either not authenticating or fails authentication to
its SMTP server, causing Outlook to attempt the send via another account
instead of giving a failure error.