Hallo Randy, On Mon, 1 Dec 2003 04:47:10 +0100 (MET)GMT (1-12-03, 4:47 +0100, where I live), you wrote:
RB> I tried to send a specific RAR file, attached to an email using MIME, and RB> got this error message every time I tried to send. I tried to send it about The error message that you had in your log wasn't a real error from your server. When TB sends a mail to your smtp server the actual message is transmitted someway like this: MAIL FROM: your-address --> 250 Will receive from your-address RCPT TO: destination-address --> 250 Will send to destination-address DATA --> 354 Enter message, ending with "." on a line by itself Here follows the message, last thing sent is a dot on a line by itself. The responses behind the arrow are the server responses, the numbers are what matters, the texts vary per server and are only important to explain to those of us who study the logs what went wrong (or didn't) As your error was a proper smtp-response, the server and TB might have gotten out of sync. Your decision to zip your attachment gave your server the time to get itself straightened up, so the zip got transmitted, waiting five minutes before sending iy again would've helped too (I think). RB> !11/29/2003, 15:14:46: SEND - Server reports error. The response is: Enter RB> message, ending with "." on a line by itself RB> !11/29/2003, 15:14:46: SEND - Server reports error. The response is: Enter RB> message, ending with "." on a line by itself These two have the same time stamp. RB> 11/29/2003, 15:22:30: SEND - sending mail messages - 2 messages in queue That's no server-message, that's TB's summary what happened. -- Groetjes, Roelof ________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
