BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

TIdPop3 error

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Internet Winsock
View previous topic :: View next topic  
Author Message
Steve Wyatt
Guest





PostPosted: Tue May 22, 2007 3:16 am    Post subject: TIdPop3 error Reply with quote



I am using BDS 2006 along with the Indy 10 components.
I've written an application that uses the TIdPop3 and TIdSMTP components.
The application wakes up every couple of minutes (via a TTimer) and checks
for new emails in a specific email box. If the box contains messages, the
messages are stored to a database, forwarded to other email addresses, and
deleted from the mailbox. Finally, TIdPop3.Disconnect is called, and the
TTimer is re-enabled.
The app. will run fine for days at a time with no problems, but
occasionally, the TIdPop3.Connect method will throw an exception: "An
existing connection was forcibly closed by the remote host". There is
usually about a 10 minute lag between the time that the Connect method is
called before the exception is finally thrown.
Can someone tell me if this implies a flaw in my application? Or is this
an issue with the Indy components? (Or something else?)

Thanks,
Steve Wyatt
Back to top
Remy Lebeau (TeamB)
Guest





PostPosted: Tue May 22, 2007 6:15 am    Post subject: Re: TIdPop3 error Reply with quote



"Steve Wyatt" <steve (AT) methods (DOT) com> wrote in message
news:46521a2b$1 (AT) newsgroups (DOT) borland.com...

Quote:
The app. will run fine for days at a time with no problems, but
occasionally, the TIdPop3.Connect method will throw an exception:
"An existing connection was forcibly closed by the remote host".

The server appears to be rejecting your connections after awhile.
Since it is coming from Connect(), the underlying socket is
established ok, but the server is then likely checking your IP and/or
username, deeming you a risk (or maybe just some server-side error
occured), and ungracefully closing the socket right away. That, or a
firewall/router in between is the one closing the connection.


Gambit
Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> Delphi Internet Winsock All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.