Il 24/02/2012 21:03, Eric Shubert ha scritto:
On 02/24/2012 12:24 PM, Joel Eddy wrote:
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.
That's a good possibility. I can't honestly say if Outlook (any
version) uses a separate session for each messages or not, but I would
guess that it likely sends them all in a single smtp session. No
reason not to that I can see. What I said earlier about this is
probably wrong.
I do know that Outlook doesn't leave an smtp session going continually
though. That would eventually time out. However, if a slew of messages
were waiting to go out, as in the case where Outlook was offline for a
period of time, they could all be sent in a single smtp session.
If/when this happens, I honestly don't know what chkuser would do. I
expect that it would apply the limits to each messages individually,
but I'm not certain of that. Tonino?
It is per TCP session. It means when several messages are sent in
different message sessions but within a unique SMTP connection, limit is
global.
I planned to make it become per message session, but honestly in years
I've received no complains, so I'm uncertain if to make it.
I suggest to keep this tarpitting action only on public MX, disabling it
on server used for authenticated relaying.
Let me repeat again: public and relay servers must be different
(different IP or different ports), mainly because many email lients do
not handle error messages, so I enable chkuser on public MX, and disable
chkuser on authenticated relay servers, where users get back messages of
not existing (local) users from qmail.
Regards,
Tonino
Generally speaking, I'm not aware of any limits that are placed on
multiple messages in a single smtp session. This doesn't mean that
there aren't any though.
Sorry for the disinformation earlier. Please keep us posted.
--
------------------------------------------------------------
Inter@zioni Interazioni di Antonio Nati
http://www.interazioni.it [email protected]
------------------------------------------------------------
---------------------------------------------------------------------------------
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]
