public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] tracking the life of an email.
@ 2006-02-24 21:03 Nick Smith
  2006-02-24 21:12 ` Dave Nebinger
  0 siblings, 1 reply; 5+ messages in thread
From: Nick Smith @ 2006-02-24 21:03 UTC (permalink / raw
  To: gentoo-user

i have setup a mailserver running qmail with clamav and spamassassin,
and it uses queue-scanner.  im still learning alot about administering
mail servers, and i was wondering, how can i track a message going
through the system? i know i can stumble through the log files, but
how do i know the exact route a message takes through my mailserver?
like from coming into the machine, being scanned by spamassassin,
being scanned by clamav, then passed to qmail to be delivered. where
can i see proof that it is actually doing all those steps?

TIA

nick

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] tracking the life of an email.
  2006-02-24 21:03 [gentoo-user] tracking the life of an email Nick Smith
@ 2006-02-24 21:12 ` Dave Nebinger
  2006-02-24 22:03   ` Nick Smith
  0 siblings, 1 reply; 5+ messages in thread
From: Dave Nebinger @ 2006-02-24 21:12 UTC (permalink / raw
  To: gentoo-user

Nick Smith wrote:
> i have setup a mailserver running qmail with clamav and spamassassin,
> and it uses queue-scanner.  im still learning alot about administering
> mail servers, and i was wondering, how can i track a message going
> through the system? i know i can stumble through the log files, but
> how do i know the exact route a message takes through my mailserver?
> like from coming into the machine, being scanned by spamassassin,
> being scanned by clamav, then passed to qmail to be delivered. where
> can i see proof that it is actually doing all those steps?

Most of these components will issue messages to syslog using the 'mail' 
facility.  If you configure your syslog daemon to route messages from 
this facility to, say, /var/log/mail.log, you'll have all of the info 
you need.

If you're using syslog-ng, the following addition will do this for you:

destination mail { file("/var/log/mail.log" perm(0644) ); };
filter f_mail { facility(mail); };
log { source(src); filter(f_mail); destination(mail); };

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] tracking the life of an email.
  2006-02-24 21:12 ` Dave Nebinger
@ 2006-02-24 22:03   ` Nick Smith
  2006-02-24 22:14     ` kashani
  2006-02-25 23:57     ` Mariusz Pękala
  0 siblings, 2 replies; 5+ messages in thread
From: Nick Smith @ 2006-02-24 22:03 UTC (permalink / raw
  To: gentoo-user

>
> Most of these components will issue messages to syslog using the 'mail'
> facility.  If you configure your syslog daemon to route messages from
> this facility to, say, /var/log/mail.log, you'll have all of the info
> you need.
>
> If you're using syslog-ng, the following addition will do this for you:
>
> destination mail { file("/var/log/mail.log" perm(0644) ); };
> filter f_mail { facility(mail); };
> log { source(src); filter(f_mail); destination(mail); };
>
> --
> gentoo-user@gentoo.org mailing list
>
>

for some reason qmail spreads things out into 3 or 4 or 5 different
log files, one for sent, smtp, pop, imap etc, its a real pain to go
through those files, i dont know if its qmail or syslog-ng thats doing
it, but ive been wanting to find a way to combine all those logs into
one mail.log file for easy grepping.....
thanks for the input.

-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] tracking the life of an email.
  2006-02-24 22:03   ` Nick Smith
@ 2006-02-24 22:14     ` kashani
  2006-02-25 23:57     ` Mariusz Pękala
  1 sibling, 0 replies; 5+ messages in thread
From: kashani @ 2006-02-24 22:14 UTC (permalink / raw
  To: gentoo-user

Nick Smith wrote:
  > for some reason qmail spreads things out into 3 or 4 or 5 different
> log files, one for sent, smtp, pop, imap etc, its a real pain to go
> through those files, i dont know if its qmail or syslog-ng thats doing
> it, but ive been wanting to find a way to combine all those logs into
> one mail.log file for easy grepping.....
> thanks for the input.
> 

It's qmail that does that. Unless you mess with it, it does it's own 
logging in binary no less. Look for the qmail-analog package which makes 
parsing it easier.

kashani
-- 
gentoo-user@gentoo.org mailing list



^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [gentoo-user] tracking the life of an email.
  2006-02-24 22:03   ` Nick Smith
  2006-02-24 22:14     ` kashani
@ 2006-02-25 23:57     ` Mariusz Pękala
  1 sibling, 0 replies; 5+ messages in thread
From: Mariusz Pękala @ 2006-02-25 23:57 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

On 2006-02-24 17:03:24 -0500 (Fri, Feb), Nick Smith wrote:
> for some reason qmail spreads things out into 3 or 4 or 5 different
> log files, one for sent, smtp, pop, imap etc, its a real pain to go
> through those files, i dont know if its qmail or syslog-ng thats doing
> it, but ive been wanting to find a way to combine all those logs into
> one mail.log file for easy grepping.....

Something like: 

  tail -F /var/log/qmail/qmail-*/current >> /var/log/qmail-all

would be Okay?

-- 
No virus found in this outgoing message.
Checked by "grep -i virus $MESSAGE"
Trust me.

[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-02-26  0:13 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-02-24 21:03 [gentoo-user] tracking the life of an email Nick Smith
2006-02-24 21:12 ` Dave Nebinger
2006-02-24 22:03   ` Nick Smith
2006-02-24 22:14     ` kashani
2006-02-25 23:57     ` Mariusz Pękala

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox