Jesse Shumaker wrote: Hi
This looks good and I think I may try this perl module. It seems that it's geared towards a single workstation and not a network of machines. They say that you point your client to localhost, which means that each machine must have this installed. How are you guys running this so that you can have one centralized SA server? Also, how does the SA box authenticate with the ISP's POP servers for each e-mail client? In my organization each user has their own password and username for their e-mail account.
We installed it on a linux box with SA, and run it as a deamon. It supports concurrent connections, altought we haven't tested it thoroughly (hundreds of simultaneous connections...). So, rather than installing it locally on each machine, use a shared POP proxy.
The client sends SAproxy the user/password, that then SAproxy submits to the remote server. It is a proxy for POP3 protocol (no support for POP3*S*), just that before sending the message to the client it is scanned by SA.
It is also very flexible, since the destinaton server has to be specified as part of the login string ([EMAIL PROTECTED] to retrieve mail with login [EMAIL PROTECTED] from pop.domain.com server): your colleagues can use the same proxy box for retrieving mail from other POP3 accounts as well.
PC -- | QRPp-I #707 + www.paolocravero.tk + I QRP #476 | | SpamAssassin-based email antispam/antivirus solutions | \ Italian/English-to/from-Croatian translations / \ Skype: pcravero /
