G
Gerry Seymour
Folks...
I'm experiencing a problem that I think is due to read
receipts. I have an e-mail account (POP3) that is set up
twice in Outlook. The primary version is for receiving mail
from either home or my office, as well as for sending from
my office. The secondary version of this account is used
only for sending e-mail from home (uses a different
outgoing server, to accomodate my ISP's restrictions). The
problem is that when I receive my e-mail on this account at
home, Outlook attempts to send the read receipts using the
primary (office) outgoing server setting, which fails. This
essentially clogs my send/receive queue until I get back to
the office, where Outlook can connect to that outgoing
server and deliver the receipts.
Here's my question: is there a way to canncel or delete
read receipts after they've been queued by Outlook? I have
some experience with VB and VBA, so if anyone has a
programmatic solution, I'd like to hear that, as well,
though that's not something I'm likely to use in the short
term, so I'd love to hear if anyone knows how to delete
these bloodsuckers without programming.
Thanks!
Gerry Seymour
(e-mail address removed)
I'm experiencing a problem that I think is due to read
receipts. I have an e-mail account (POP3) that is set up
twice in Outlook. The primary version is for receiving mail
from either home or my office, as well as for sending from
my office. The secondary version of this account is used
only for sending e-mail from home (uses a different
outgoing server, to accomodate my ISP's restrictions). The
problem is that when I receive my e-mail on this account at
home, Outlook attempts to send the read receipts using the
primary (office) outgoing server setting, which fails. This
essentially clogs my send/receive queue until I get back to
the office, where Outlook can connect to that outgoing
server and deliver the receipts.
Here's my question: is there a way to canncel or delete
read receipts after they've been queued by Outlook? I have
some experience with VB and VBA, so if anyone has a
programmatic solution, I'd like to hear that, as well,
though that's not something I'm likely to use in the short
term, so I'd love to hear if anyone knows how to delete
these bloodsuckers without programming.
Thanks!
Gerry Seymour
(e-mail address removed)