That's kinda what I figured it did. Just wasn't 100% on that decision. Thanks for the info. I think what's happening is the client uses Peachtree accounting to send invoices. And from what I remember of Peachtree is it sends the invoice to the email client of choice and sends through it. Since the client uses Outlook 2007 I'm thinking it isn't sending the message right away. Instead I think it probably Cues the message in Outlook until you hit send and receive. If that's the case, and I believe that is the default for Outlook it could very well be holding a rather large number of messages to send.
Hence, causing the per session limit pop up. I've got to go over to the clients place of business and check that to know for sure however. Joel -----Original Message----- From: Brent Gardner [mailto:[email protected]] Sent: Friday, February 24, 2012 12:07 PM To: [email protected] Subject: Re: [qmailtoaster] Re: Per Session Limit Question On 02/23/2012 11:12 AM, Eric Shubert wrote: > On 02/23/2012 09:41 AM, Joel Eddy wrote: >> >> >> I've got a situation going on that an end user hits the tcp.smtp >> limit of 50. Their Norton AV pops up with error 571 Maximum number of >> recipients for one session. So I'm assuming it's the tcp.smtp limit >> causing it. They use >> POP3 to send, receive mail. >> >> My questions are. >> Q. What is considered a session. And what limits it. Is it time in >> minutes, seconds or ? >> >> A. >> >> Q. Is it considered a session from the moment the Outlook client >> sends it's first message of the day, and does it continue the session >> if you leave Outlook open all day? >> >> A. >> >> I know I can up the CHKUSER_RCPTLIMIT="50" but if I set it to 100 and >> the end user sends 150 messages a day, does it still hit the per >> session limit? >> >> If so then the answer would be to shut down Outlook before sending >> more than >> 50 or what ever number of messages. Right? >> >> Any ideas you have are welcome. >> >> Thanks. >> >> Joel >> >> >> --------------------------------------------------------------------- >> ------------ >> > > Since it's NortonAV that's issuing the message, I expect that the > solution lies therein. > Although I can't speak to the tcp.smtp configuration, we used to run Symantec antivirus here so maybe I can clarify what's going on with that. When you have a Norton/Symantec antivirus product installed on a Windows box and configured to monitor your email, it inserts itself as a transparent proxy, watching all inbound & outbound traffic on typical email protocol ports on that machine. The Norton/Symantec product is not generating the error, it's simply reporting back to the user what it received from the outbound mail server. Brent Gardner ---------------------------------------------------------------------------- ----- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! ---------------------------------------------------------------------------- ----- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.1913 / Virus Database: 2114/4829 - Release Date: 02/24/12 --------------------------------------------------------------------------------- Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! --------------------------------------------------------------------------------- Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
