Hello MFPA, Monday, November 2, 2009, 8:44:38 AM, you wrote:
M> Hi M> On Saturday 31 October 2009 at 3:55:58 PM, in M> <mid:[email protected]>, Gene wrote: >> I am getting SPAM emails that somehow have the ability >> to set The Bat! to continue to download the message >> over and over and over. >> Account|Dispatch Mail on Server|All Messages: reveals >> that the receive box is checked for that item. I can >> remove the check mark and sometimes it will, again, >> check itself and begin downloading again..... M> The only experiences I have with messages keeping on downloading are M> when the connection to the server is lost. This has happened when M> there has been an issue with my computer, my internet connection, or M> the server. It has also happened when some "kind" soul has sent an M> email with huge attachment(s) that take so long to download that the M> server times out the connection. Both of these result in *all* M> messages being downloaded again repeatedly before any new messages M> until a server session is successfully completed. M> As far as I know, the tick in the receive box in the dispatcher window M> only applies for downloading in *that* dispatcher session. It should M> only be there by default if you have not yet downloaded that message M> (or if something has happened to whichever file TB! uses to identify M> which messages have already been downloaded, in which case it would M> probably be ticked for *all* messages) >> I had one do this for nearly a year, before I realised >> it wasn't a rogue server or intentional act. It was >> merely my own instance of The Bat! malfunctioning. >> M> Nearly a year? I must say that I admire your patience. Did this M> "rogue" message prevent newer messages from being downloaded, or do M> you always "dispatch on server?" I never "dispatch on server" unless I'm troubleshooting. >> Along those same lines, I discovered that if one sends >> a message to a group of people as BCC: and one of the >> messages comes back undeliverable, M> You mean you get a "bounce" message back later.0, or the server refuses M> to accept an addressee at the time? In this case one was undeliverable due to being and old and dead address. >> the message stays in >> the Outbox and continues to attempt delivery... thus >> sending an unending stream of duplicate messages to the >> succesfully delivered addresses..... M> That doesn't happen for me. It doen't to me, every time.... -- Best regards, Gene mailto:[email protected] --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 091102-0, 11/02/2009 Tested on: 11/2/2009 5:18:57 PM avast! - copyright (c) 1988-2009 ALWIL Software. http://www.avast.com ________________________________________________ Current version is 4.2.10.0 | 'Using TBUDL' information: http://www.silverstones.com/thebat/TBUDLInfo.html
