[Devil-linux-develop] DL mail gateway notes

[Kari M. <ka...@tr...>]

Few notes from my mailgw.....com project:

- the following services are required:
   postfix, spamd, freshclam, sagator, syslog[-ng]
- postfix requires quite a bit hacking for a safe setup, which is=20
accidentally NOT an open relay, but still is an backup MX for many=20
domains, and optionally an gateway for some LAN-side mail servers
- it is a good idea to limit the relay_recipients in postfix so that you=20
don't get overloaded with spam sent to non-existing addresses
- integrating sagator+clamav+spamassassin to postfix is rather=20
straightforward
- it would be a great addition, if i could integrate postfix to=20
saslauthd on this same setup, but it is not possible at this time due to=20
a missing saslauth conf file -- this seems to be a known issue
- last but not least: getting a (graphical) report a something of a key=20
requirement on production systems; currently this seems next to=20
impossible with a stock DL

    - sagator has a /etc/mrtg/sagator.cfg file for rudimentary mrtg=20
graphing -- DL does not have mrtg, only rrdtool.
    - i tried to find a way to convert that sagtor.cfg to something=20
rrdtool would understand, but my knowledge falls short at this time.
    - mailgraph is an excellent (best?) graphing tool on=20
postfix+spamassassin+clamav log files, it uses rrdtool. well, mailgraph=20
only works with metalog ja syslog log files, not with syslog-ng. i'm=20
told changing from syslog-ng to syslog might break things. mailgraph=20
also requires few more perl modules than we currently have.


Any suggestions on how I could get graphs on mail traffic?

I'm willing to send key parts of my main.cf and some other key files, if=20
there is interest. Either to this list, or to requester(s) directly.


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.