9.1 Using Pop3proxy

‚  < ‚  Day Day Up ‚  > ‚  

Pop3proxy, by Dan McDonald, is one of the oldest SpamAssassin POP proxies and, to its credit, still functions well with SpamAssassin 2.63. It's a no-fills proxy written in Perl and requires manual installation and configuration. It does not perform network-based SpamAssassin tests. Download Pop3proxy (and read the manual) at http://mcd.perlmonk.org.

9.1.1 Installing Pop3proxy

Follow these steps to install Pop3proxy:

  1. Download pop3proxy.zip and unpack it into a directory of your choice. For this example, I assume you've unpacked it in C:\pop3proxy so a directory listing of that directory would look like this:

     C:\pop3proxy>  dir /s  Directory of C:\pop3proxy 03/26/2004  09:56p      <DIR>          . 03/26/2004  09:56p      <DIR>          .. 03/26/2004  09:56p      <DIR>          pop3proxy 08/18/2002  05:40p              60,781 pop3proxy.pl 08/18/2002  05:40p              28,798 pop3proxy.html                2 File(s)         89,579 bytes  Directory of C:\pop3proxy\pop3proxy 03/26/2004  09:56p      <DIR>          . 03/26/2004  09:56p      <DIR>          .. 08/12/2002  08:19a               6,240 Artistic 08/11/2002  08:45p                 567 kill_proxy.pl 08/12/2002  08:30a                 536 hostmap.sam                3 File(s)          7,343 bytes 

  2. Install a version of Perl for Windows that includes the Time::HiRes module. Several Perl distributions for Windows are available, but one that is known to work (and provides a precompiled version of the module) is ActivePerl, available at http://www. activestate .com/Products/ActivePerl. Either ActivePerl 5.6.1 or 5.8.3 works well with Pop3proxy. ActivePerl 5.8.3 supports Unicode. ActivePerl 5.6.1 does not support Unicode but has been extensively tested with SpamAssassin. In this example, I assume you've installed ActivePerl in C:\perl .

    Time::Hires can be installed through ActivePerl's Perl Package Manager. After installing ActivePerl, run the Perl Package Manager, and type install Time::HiRes at the ppm> prompt. Type quit to exit the Package Manager.

  3. Download and unpack SpamAssassin. Copy all of the files and directories in SpamAssassin's lib directory to ActivePerl's C:\perl\site\lib directory. Copy SpamAssassin's rules directory and all its contents to C:\pop3proxy\rules . Copy the user_prefs.template file from the rules directory to C:\pop3proxy and rename it user_prefs. The C:\pop3proxy directory should now look like this:

     C:\pop3proxy>  dir /w /s  Directory of C:\pop3proxy [.]              [..]             [pop3proxy]      pop3proxy.html pop3proxy.log    pop3proxy.pl     [rules]          user_prefs                4 File(s)        110,825 bytes  Directory of c:\pop3proxy\pop3proxy [.]             [..]            Artistic        hostmap.sam     kill_proxy.pl                3 File(s)          7,343 bytes  Directory of C:\pop3proxy\rules [.]                     [..]                    10_misc.cf 20_anti_ratware.cf      20_body_tests.cf        20_compensate.cf 20_dnsbl_tests.cf       20_fake_helo_tests.cf   20_head_tests.cf 20_html_tests.cf        20_meta_tests.cf        20_phrases.cf 20_porn.cf              20_ratware.cf           20_uri_tests.cf 23_bayes.cf             25_body_tests_es.cf     25_body_tests_pl.cf 25_head_tests_es.cf     25_head_tests_pl.cf     30_text_de.cf 30_text_es.cf           30_text_fr.cf           30_text_it.cf 30_text_pl.cf           30_text_sk.cf           50_scores.cf 60_whitelist.cf         languages               local.cf regression_tests.cf     STATISTICS-set1.txt     STATISTICS-set2.txt STATISTICS-set3.txt     STATISTICS.txt          triplets.txt user_prefs.template 

  4. Edit C:\pop3proxy\user_prefs and set up SpamAssassin preferences. See Chapter 2 and Chapter 3 for configuration details.

9.1.2 Starting Pop3proxy

To start Pop3proxy, you must invoke Perl on the pop3proxy.pl script and provide command-line arguments to identify the POP server. If you allowed ActivePerl to associate its perl.exe program with .pl file extensions, you should be able to execute pop3proxy.pl directly. Otherwise, set up a shortcut or batch file containing:

 c:\perl\bin\perl c:\pop3proxy\pop3proxy.pl --host   pop.example.com   

When invoked, the shortcut will open a DOS window and execute the proxy script. You can stop the proxy by typing CTRL-C in the DOS window. When you've confirmed that it's working as you like, you can replace \perl\bin\perl with \perl\bin\wperl in the shortcut. wperl runs the script in the background (without opening a DOS window); use it when you plan to keep Pop3proxy running all the time. You can stop the proxy by invoking the kill_proxy.pl script included with Pop3proxy, or by using the Windows Task Manager to kill the wperl process.

Here is a complete list of Pop3proxy's command-line arguments:


--host hostname[:port]

Provide the hostname (and optionally , the port number) of the remote POP server to proxy.


--logfile filename

Provide the name of a file to log connection and status information to. This defaults to pop3proxy.log . The log file can be useful in debugging problems with Pop3proxy. Example 9-1 shows a Pop3proxy log of a successful connection in which Pop3proxy downloaded two messages and classified one as spam.


--maxscan bytes

Specify the largest message, in bytes, that Pop3proxy will invoke SpamAssassin on. The default is 250,000, which is reasonable. Larger sizes cause more messages to be scanned, but larger messages scan more slowly.


--nopad

POP servers sometimes provide POP clients with message- and mailbox-size information. Running SpamAssassin on a message when it's between server and client can change (typically, enlarge) the message size . Most modern clients handle this situation with no problems, but if yours does not, the --nopad option causes Pop3proxy to overwrite text in existing headers rather than adding new ones, maintaining a constant size at the cost of obfuscating the message headers to a small degree.


--allowtop

The POP protocol provides a TOP command that the client uses to request only a limited amount of a message from the server (deferring the retrieval of the rest of the message until it's explicitly asked for). TOP doesn't interact well with spam-checking proxies, and Pop3proxy normally prevents the client from using it. If you want to try it out anyway, use the --allowtop argument.


--exitport portnumber

The kill_proxy.pl script works by connecting to a second port that pop3proxy.pl listens on. Any connections on this port cause pop3proxy.pl to exit. By default, the port number is 9625, but you can use the --exitport option to change it if you use that port number for something else. If you change the port number, you must edit the kill_proxy.pl script and change the value of $exitport near the beginning of the file.

Example 9-1. A log from Pop3proxy
 New connection: From: 127.0.0.1:2094 To:   192.168.0.4:110 192.168.0.4:110 (Server) said +OK to none +OK POP3 Ready pop.example.com 127.0.0.1:2094 (Client) said CAPA 192.168.0.4:110 (Server) said -ERR to CAPA 127.0.0.1:2094 (Client) said USER 192.168.0.4:110 (Server) said +OK to USER 127.0.0.1:2094 (Client) said PASS 192.168.0.4:110 (Server) said +OK to PASS 127.0.0.1:2094 (Client) said STAT 192.168.0.4:110 (Server) said +OK to STAT 127.0.0.1:2094 (Client) said UIDL 192.168.0.4:110 (Server) said +OK to UIDL 127.0.0.1:2094 (Client) said LIST 192.168.0.4:110 (Server) said +OK to LIST 127.0.0.1:2094 (Client) said RETR 192.168.0.4:110 (Server) said +OK to RETR Snarfing RETR response Detected end of snarfed multiline 35510 bytes, SPAM, Message-id: <200402062012.i16KCGBb015885@example.com> 127.0.0.1:2094 (Client) said LIST 192.168.0.4:110 (Server) said +OK to LIST 127.0.0.1:2094 (Client) said RETR 192.168.0.4:110 (Server) said +OK to RETR Snarfing RETR response Detected end of snarfed multiline 2096 bytes, NOT spam, Message-id: <1063926361.20040206152006@oreilly.com> 127.0.0.1:2094 (Client) said QUIT 192.168.0.4:110 (Server) said +OK to QUIT 192.168.0.4:110 - socket close on read Flushing peer on close 127.0.0.1:2094 - peer gone after write, closing 

Pop3proxy can proxy multiple POP servers through the use of a hostmap file. See the Pop3proxy manual for more information about setting up such a file.

9.1.3 Configuring the POP Client

Finally, you must reconfigure a mail client to connect to localhost (or 127.0.0.1) instead of the usual POP server. Connections to localhost will be received by Pop3proxy and proxied to the POP server. Figure 9-2 shows the Eudora 5.1 dialog box for configuring the incoming POP server for an account.

Figure 9-2. Configuring Eudora to use Pop3proxy

‚  < ‚  Day Day Up ‚  > ‚  


SpamAssassin
SpamAssassin
ISBN: 0596007078
EAN: 2147483647
Year: 2004
Pages: 88

Similar book on Amazon

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net