as i read in serverl discussions POP3 should not be affected from spin-locks/event-handkler problems this sounds for me like dbmail-pop3d is still single threaded?
does this finally mean that only one connection is served with data while the others practically wait? if yes - should we not start more than one process and what happens if the current served client is terrible slow while receive a 15 MB message? will all others have to wait for him?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
