Greetings all,

I’ve got an issue with R:Mail 2.6   (actually, I think it’s an Exchange server 
issue).   I’m running Turbo V-8, build 8.0.19.31229.

My schools recently updated our domain name and switched from Lotus Notes to 
Exchange

I’m using R:Mail 2.6, simple loop, to send 795 (or whatever) emails.   
Connecting to a SMTP MS Exchange Server.

Everything perks along nicely until I’ve sent 188-190 emails, then the emails 
start taking 10, then 20, then 40 seconds each, up to 50 seconds each.   I’ve 
run this multiple times, always slows down at the 188-190 email limit, even 
when I put a 1 second pause in the program loop or when I changed the length of 
the email message.   Seems like this makes a cache or disk storage size limit 
unlikely.   I’ve used different sets of data, so it’s not a problem with the 
email address being used or a data corruption problem.  The program doesn’t 
quit, just slows down by a factor of 25.  Yikes.

From the log file, it looks like the SMTP connection is not saying it’s ready 
for an extended period of time.

Am I reading this correctly?   I think R:Mail is connecting, but not receiving 
a response back from the server for 50 seconds.   Is that correct?

Sent 1/22/2009 4:57:58 PM: QUIT<EOL>
Stat Disconnected.
Stat Connected.
Recv 1/22/2009 4:58:48 PM: 220 “server name changed to protect the 
innocent.edu” Microsoft ESMTP MAIL Service ready at Thu, 22 Jan 2009 16:58:50 
-0600<EOL>

I don’t think this is an R:Mail or Turbo V-8 issue, since it worked just dandy 
before MS Exchange, but I’m unsure what to tell the IT folks to change to make 
it work.

Any help would be appreciated.

Paul

Paul Patrick, Associate Registrar
University of Central Oklahoma
[email protected]
(405) 974-2336



**ADDRESS CHANGE NOTICE**-The University of Central Oklahoma is
moving to a new Internet address.  All e-mail addresses and Web
sites are now available at uco.edu.  All e-mail addresses and Web
sites will use uco.edu effective January 2, 2009.

**CONFIDENTIALITY** -This e-mail (including any attachments) may
contain confidential, proprietary and privileged information.  Any
unauthorized disclosure or use of this information is prohibited.

Reply via email to