| | Hello | | | | I have been noticing, the following behavior on one of our mail servers | | which happens to be running spamdyke. The qmail incomingconcurrency | | setting is 500. | | | | When tls-level is set to smtp, the number of timeouts increases and | errors | | indicating unable to write to ssl/tls stream increases. the errors are | I/O | | errors mostly Broken pipe, but some are Connection reset by peer. | | | | The effect I witness is increases in the smtp concurrency usage. In | | certain busy periods, it goes to the 450+ percent area. The MRTG graph | | indicates max/smtp, I didn't write the scan criteria. | | | | Setting the tls-level to none, decreases the concurrency and the errors | | diminish as well (less errors makes sense). Concurrency usage drops to | | below the 100 percent mark | | | | I guess I don't understand the methodology of enabling tls under smtp | | since I don't have port 995 open to the mailers. | | | | Needless to say, when the server reaches the max incomingconcurrency | | setting, users get shut out (temporarily). | | | | Anyone have any ideas? | | | | Best | | Greg | | | | Correction port 995 should have read 465 |
Further investigation is indicating the smtp incomingconcurrency does not appear to be affected by the tls setting (though, the errors and broken connections do appear to go away once tls is disabled), but appears to be related to the idle-timeout-secs setting. I've reduced the idle-timeout-secs from 300 to 60 and the smtp incomingconcurrency actual usage value returns to under 100%, according to the MRTG graph. Will keep an eye on this, if I find something else I'll add it here Best g _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
