Let me try and summarize what I have recieved from all these e-mails as well as put together myself. Then you guys could give me some feedback if I'm on the right trail. What I need to do is install SpamAssassin w/pop3proxy on a linux box. Then setup the pop3proxy to point to my external pop3 server. On the client side I will need to setup each client's login to include their login name and the SpamAssassin/pop3proxy server (I'm not sure if I can only do this if I use the SAproxy utility for windows). Thats how I understand this should work. Now configuring this is another situation. How does it look to you guys? I have just noticed that there are a lot of utilities and stuff to use and am trying to piece it all together.

thanks

On 7/6/05, Jesse Shumaker <[EMAIL PROTECTED]> wrote:
So you must have SAproxy on each client to do this? I know that is another product that I have heard of. If so do you have a download link where I can get SAproxy? If that is just the name you are calling the SpamAssassin proxy it looks like all I would need to do is specify the destination server in the login box and I'm set. All I have to do on the server end is setup the POP3proxy. Is this correct?


On 7/6/05, Paolo Cravero as2594 < [EMAIL PROTECTED] > wrote:
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                 /


Reply via email to