> Thats absoluteley one of the killing situations. My favourised Test > was sending a 150 MB mail in 2 threads over my google-account, so that > the delivery reaches bandwith limits. Under windows PERL died almost, > checking the taskmanager shows that per.exe and "system" have 50% load > each. And it eats the whole memory. The delivery-time was above 30 minutes. > Now, on the same hardware with a higher softwarestack is goes faster, > needs less memory and amost NO CPU.
Now... I'd like to know how's your config; mine is more or less like this one http://www.iworld.de/homes/fb/ASSP/056449D7-000F4555.2/22102007_122151_0.png that is, there's a box (dual Xeon, 8Gb RAM, Win2K3) running ASSP and the IIS SMTP, the box receives all the incoming and the outgoing emails and when I send an email outside, the mailserver gets it, then it forwards it to ASSP which in turn passes it over to the IIS SMTP which queues it and then sends the mail to its final destination; I have no problems with such a setup, sure, you'll have to fine tune the "message sizes" for ASSP (e.g. the clamav maxbytes has to be set to a "tuned" value) but in general I see no problems; YMMV btw :) ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
