| 1 |
Nick Smith wrote: |
| 2 |
> i have setup a mailserver running qmail with clamav and spamassassin, |
| 3 |
> and it uses queue-scanner. im still learning alot about administering |
| 4 |
> mail servers, and i was wondering, how can i track a message going |
| 5 |
> through the system? i know i can stumble through the log files, but |
| 6 |
> how do i know the exact route a message takes through my mailserver? |
| 7 |
> like from coming into the machine, being scanned by spamassassin, |
| 8 |
> being scanned by clamav, then passed to qmail to be delivered. where |
| 9 |
> can i see proof that it is actually doing all those steps? |
| 10 |
|
| 11 |
Most of these components will issue messages to syslog using the 'mail' |
| 12 |
facility. If you configure your syslog daemon to route messages from |
| 13 |
this facility to, say, /var/log/mail.log, you'll have all of the info |
| 14 |
you need. |
| 15 |
|
| 16 |
If you're using syslog-ng, the following addition will do this for you: |
| 17 |
|
| 18 |
destination mail { file("/var/log/mail.log" perm(0644) ); }; |
| 19 |
filter f_mail { facility(mail); }; |
| 20 |
log { source(src); filter(f_mail); destination(mail); }; |
| 21 |
|
| 22 |
-- |
| 23 |
gentoo-user@g.o mailing list |
Archives