D
David
I received a piece of spam that contains a read receipt request, and Outlook
honored that request. It shouldn't have, however, because I long ago went
to Tools/Options/Email Options/Tracking Options and UNchecked every
checkbox, plus I selected the "Never send a response" radio button.
This sure seems like a bug in Outlook to me. How can I stop it from sending
read receipts given that I've already told it not to?
The reason I know Outlook sent a read receipt is that the email address
which was supposed to receive the receipt is invalid, and my ISP's mailer
daemon sent me an email notifying me of that.
Now, I do have a couple of Rules set up to move incoming email to various
folders. I think the read receipt was generated when one of these rules
caused the incoming email to be moved. Although the rule moved it, the
email was still marked as unread.
I'm running Outlook 2002 (10.4712.4219) SP-2 on Windows XP Home. According
to Windows Update and Office Update sites all Msft software is up to date.
I'm accessing my mailbox at my ISP using IMAP.
Below is the read receipt that my ISP informed me couldn't be delivered. To
prevent spammer newsgroup crawlers from harvesting my info I've replaced
various bits with square-bracketed comments [like this].
Return-Path: [my email address appears here]
Received: (qmail 9213 invoked from network); 2 Nov 2003 20:05:57 -0000
Received: from unknown (HELO [my computer name appears here]) ([my IP
address appears here])
(envelope-sender <[my email address appears here]>)
by mail8.speakeasy.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 2 Nov 2003 20:05:57 -0000
From: "David" <[my email address appears here]>
To: "': lillian '" <[email protected]>
Subject: Read: Todays Leading Gainers, k
Date: Sun, 2 Nov 2003 12:05:48 -0800
Message-ID: <[some hex number]$[some hex number]$[some hex number]@[my
computer name]>
MIME-Version: 1.0
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="winmail.dat"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-MS-TNEF-Correlator: [a big chunk of encoded information appears here]
honored that request. It shouldn't have, however, because I long ago went
to Tools/Options/Email Options/Tracking Options and UNchecked every
checkbox, plus I selected the "Never send a response" radio button.
This sure seems like a bug in Outlook to me. How can I stop it from sending
read receipts given that I've already told it not to?
The reason I know Outlook sent a read receipt is that the email address
which was supposed to receive the receipt is invalid, and my ISP's mailer
daemon sent me an email notifying me of that.
Now, I do have a couple of Rules set up to move incoming email to various
folders. I think the read receipt was generated when one of these rules
caused the incoming email to be moved. Although the rule moved it, the
email was still marked as unread.
I'm running Outlook 2002 (10.4712.4219) SP-2 on Windows XP Home. According
to Windows Update and Office Update sites all Msft software is up to date.
I'm accessing my mailbox at my ISP using IMAP.
Below is the read receipt that my ISP informed me couldn't be delivered. To
prevent spammer newsgroup crawlers from harvesting my info I've replaced
various bits with square-bracketed comments [like this].
Return-Path: [my email address appears here]
Received: (qmail 9213 invoked from network); 2 Nov 2003 20:05:57 -0000
Received: from unknown (HELO [my computer name appears here]) ([my IP
address appears here])
(envelope-sender <[my email address appears here]>)
by mail8.speakeasy.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 2 Nov 2003 20:05:57 -0000
From: "David" <[my email address appears here]>
To: "': lillian '" <[email protected]>
Subject: Read: Todays Leading Gainers, k
Date: Sun, 2 Nov 2003 12:05:48 -0800
Message-ID: <[some hex number]$[some hex number]$[some hex number]@[my
computer name]>
MIME-Version: 1.0
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="winmail.dat"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-MS-TNEF-Correlator: [a big chunk of encoded information appears here]