Tanktalus,

This being postfix, you can set it up to authenticate against either MySQL or LDAP, and one good way to limit spam would be to authenticate the recipient address against a known database of users able to accept email.

If it doesn't exist in your authoritative database, throw it away. I'm saying this because the majority of spam I was seeing when I did email for a living (I was an email admin for a small telecom) were generated by dictionary attacks, and this is a simple, trouble free way to get rid of all that.

If this is a terminal email acceptor (as opposed to a forwarder), then you might want to grab one of the formulas for building a amavisd-spamassasin-clamav setup as well. Just be warned that this software trio is a power hungry, not suitable for old hardware if you're seeing large volumes of stuff. High volume receivers keep this trio on separate hardware from the original MX acceptor.

---

---

• 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.