Very little - the proxy seems to add fractional seconds per message (see the logs while it's running) but it might "feel" slower in your mail client due to the batched-then-dumped nature of things. The proxy buffers up the whole message, then the client gets it all at once, rather than trickling in. You might see jumpy progress bars as a result sometimes.

One of the biggest lag problems with a SpamAssassin scan happens when SA spins off into the weeds on truly large messages. This may be an acceptable delay in a store-and-forward chain, but in a real time network proxy it's fatal. Pop3Proxy works around that (like many SA apps) by declining to scan messages over a certain size - 250K by default, but it's configurable.

See the discussion on the manpage for more on that.

Peace,
-McD

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.