| Next revision | Previous revision |
| howtos:saproxy [2008/02/08 18:49] – external edit 127.0.0.1 | howtos:saproxy [2012/06/28 14:16] (current) – external edit 127.0.0.1 |
|---|
| ====== Configure SAProxy for POPFile ====== | ====== Configure SAProxy for POPFile ====== |
| | |
| | ** CAUTION: ** The content of this page seems to be **outdated**. |
| |
| SAproxy is a Windows POP3 proxy implementation of Spamassassin. You can get it (free) at http://www.bloomba.com/download.html#saproxydl. | SAproxy is a Windows POP3 proxy implementation of Spamassassin. You can get it (free) at http://www.bloomba.com/download.html#saproxydl. |
| In the default configuration, SAproxy will proxy to a mailserver address and host based on the username sent to SAproxy. So in your e-mail client you would use //realusername:realPOPserver:nnn// as your POP3 account username, where "nnn" is the POP server port. If your server uses port 110 (typically) you can omit the port and just use //realusername:realPOPserver// as your username. | In the default configuration, SAproxy will proxy to a mailserver address and host based on the username sent to SAproxy. So in your e-mail client you would use //realusername:realPOPserver:nnn// as your POP3 account username, where "nnn" is the POP server port. If your server uses port 110 (typically) you can omit the port and just use //realusername:realPOPserver// as your username. |
| |
| Now POPfile proxys using the username //realPOPserver:nnn:realusername// but it will actually be told the mailserver is SAproxy, so the username you should use is //127.0.0.1:110:realusername// or just //127.0.0.1:realusername// and your client should be told the POP server is //127.0.0.1// and port 220 (this is POPfiles new listening port). | Now POPfile proxys using the username //realPOPserver:nnn:realusername// but it will actually be told the mailserver is SAproxy, so the username you should use is //127.0.0.1:110:realusername// or just //127.0.0.1:realusername// and your client should be told the POP server is //127.0.0.1// and port 220 (this is POPfile�s new listening port). |
| |
| That's all. If you've already set up your mail clients filters for POPfilter you won't have to change these as after a few corrections, it will quickly learn to recognize any mail modified by SAproxy as belonging in your spam bucket, since SAproxy will always add the same header tags and opening paragraph in the message body. If your mail client doesnt allow you to specify the server port, you can keep POPfile on 110 and use the Hosts page in the SAproxy configuration window (see below) to assign SAproxy a different port, then change your username to use that port instead of 110. | That's all. If you've already set up your mail client�s filters for POPfilter you won't have to change these as after a few corrections, it will quickly learn to recognize any mail modified by SAproxy as belonging in your spam bucket, since SAproxy will always add the same header tags and opening paragraph in the message body. If your mail client doesn�t allow you to specify the server port, you can keep POPfile on 110 and use the Hosts page in the SAproxy configuration window (see below) to assign SAproxy a different port, then change your username to use that port instead of 110. |
| |
| Now I actually use a third proxy for my hotmail account. I use hot Hotmail Popper which you can get (free) at http://www.boolean.ca. After you install it, you'll want to change its listening port to one that won't conflict with SAproxy or POPfile. Let's say 330. Now SAproxy needs to be told that the real mail server, in this case Hotmail Popper, is on port 330. This is done by adding a few lines in the hosts tab of the configuration dialogue in SAproxy. If you add any entries here, the port forwarding based on username appears to be disabled, so you will have to add explicit entries for any mail server that will be used. So in this example something like the following 2 lines would be added to the hosts page: | Now I actually use a third proxy for my hotmail account. I use hot Hotmail Popper which you can get (free) at http://www.boolean.ca. After you install it, you'll want to change its listening port to one that won't conflict with SAproxy or POPfile. Let's say 330. Now SAproxy needs to be told that the real mail server, in this case Hotmail Popper, is on port 330. This is done by adding a few lines in the hosts tab of the configuration dialogue in SAproxy. If you add any entries here, the port forwarding based on username appears to be disabled, so you will have to add explicit entries for any mail server that will be used. So in this example something like the following 2 lines would be added to the hosts page: |
| Now we'll add a 4th proxy you can obtain (for free) at ... actually I'm kidding. I'll stop here. | Now we'll add a 4th proxy you can obtain (for free) at ... actually I'm kidding. I'll stop here. |
| |
| I'd be happy to hear any comments/criticisms you might have. So far my biggest complaint is that Im getting several false positives from POPfile, but I've only been using it a couple of days so hopefully after a little more training this will improve. | I'd be happy to hear any comments/criticisms you might have. So far my biggest complaint is that I�m getting several false positives from POPfile, but I've only been using it a couple of days so hopefully after a little more training this will improve. |
| |
| This message turned out to be much longer than I intended. Thanks for reading if youve made it this far. If not, Im just typing to myself, which may be an early sign of dementia
| This message turned out to be much longer than I intended. Thanks for reading if you�ve made it this far. If not, I�m just typing to myself, which may be an early sign of dementia� |
| |
| Ric | Ric |
| |
