AW: log files
hi the qmail-send/run only executes the /var/qmail/rc script (so its nearly the same). And at the first time I havn't had the multilog command in /var/qmail/run, i've then added it because the log doesn't worked for me. And it still doesn't work. -Ursprüngliche Nachricht- Von: Charles Cazabon [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 9. August 2001 16:40 An: QMail Mailling List Betreff: Re: log files Wolfgang Pichler [EMAIL PROTECTED] wrote: I have a running qmail box, with (at this time) only 1 problem: The qmail-send program write its logs to tty1 and not in the log files. [...] my qmail-send rc looks like: ---cut--- #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH qmail-start Maildir /usr/local/bin/multilog /var/log/qmail/qmail-send ---cut--- my qmail-send/log/run file: ---cut--- #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/qmail-send Your qmail-send rc? Do you mean /service/qmail-send/run or /var/qmail/rc? In any case, you can't have multilog in that script plus a log/run script and still make sense. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: log files
Wolfgang Pichler ([EMAIL PROTECTED]) wrote: hi the qmail-send/run only executes the /var/qmail/rc script (so its nearly the same). And at the first time I havn't had the multilog command in /var/qmail/run, i've then added it because the log doesn't worked for me. And it still doesn't work. Hi Wolfgang, try this: #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH \ qmail-start ./Maildir/ multilog t s100 n100 /usr/local/server/qmail/main Put this in yout /var/qmail/rc s defines how big the logfile can get n defines how many logfiles aregenerated The rest is the path where your logfiles are stored. /martin
log files
hi I have a running qmail box, with (at this time) only 1 problem: The qmail-send program write its logs to tty1 and not in the log files. I've setted qmail up with the use of supervise und multilog (tcpserver). All the other processes (qmail-pop3d/qmail-smtpd) are putting there logs in the right files. so can anyone help me for solving this problem ? Here are my running processes and the start scripts: my running processes ---cut--- 99 ?S 0:09 svscan /service 114 ?S 0:00 supervise vmailmgrd 115 ?S 0:00 supervise log 116 ?S 0:00 supervise qmail-pop3d 117 ?S 0:00 supervise log 118 ?S 0:00 supervise qmail-smtpd 119 ?S 0:00 supervise log 120 ?S 0:00 supervise qmail-send 121 ?S 0:03 supervise log ---cut--- my qmail-send rc looks like: ---cut--- #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH qmail-start Maildir /usr/local/bin/multilog /var/log/qmail/qmail-send ---cut--- my qmail-send/log/run file: ---cut--- #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/qmail-send ---cut--- Pichler Wolfgang Dialog Austria Software Telekommunikation Ges.m.b.H. Goethestrasse 93 A-4020 Linz Tel +43 (0) 70 662774 37 Fax +43 (0) 70 662774 22 Mailmailto:[EMAIL PROTECTED] Web www.dialog-gruppe.at +++
Re: log files
Wolfgang Pichler [EMAIL PROTECTED] wrote: I have a running qmail box, with (at this time) only 1 problem: The qmail-send program write its logs to tty1 and not in the log files. [...] my qmail-send rc looks like: ---cut--- #!/bin/sh exec env - PATH=/var/qmail/bin:$PATH qmail-start Maildir /usr/local/bin/multilog /var/log/qmail/qmail-send ---cut--- my qmail-send/log/run file: ---cut--- #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/qmail/qmail-send Your qmail-send rc? Do you mean /service/qmail-send/run or /var/qmail/rc? In any case, you can't have multilog in that script plus a log/run script and still make sense. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Bounce-backs with attachments, log files. . .
It seems when a user sends mail with an attachment and it bounces back, the bounce-back has the attachment in-line with the mail text (as opposed to something you can click on then save or open). This isn't a major problem (my users aren't getting bounce-backs with 20MB attachments every five minutes) but when it does occur users complain about their mail reading program taking much longer to open---or even locking up---because of the in-line attachment. Is there any way to change this behavior or is this how all e-mail servers are supposed to work (this is the first full-blown mail server I've set up)? All apologies if the answer to this next question is blatantly obvious; I thought I looked everywhere I was supposed to. I'm assuming the long number at the beginning of each line in /var/log/qmail/current (I'm using multilog instead of splogger) is some form of timestamp. How do you convert that to an easily-recognizable format? Thanks much for any help with this. ---Norvell Spearman --- ``Trouble is my business.'' ---Philip Marlowe
Re: Bounce-backs with attachments, log files. . .
Norvell Spearman [EMAIL PROTECTED] wrote: It seems when a user sends mail with an attachment and it bounces back, the bounce-back has the attachment in-line with the mail text (as opposed to something you can click on then save or open). This isn't a major problem (my users aren't getting bounce-backs with 20MB attachments every five minutes) but when it does occur users complain about their mail reading program taking much longer to open---or even locking up---because of the in-line attachment. Is there any way to change this behavior or is this how all e-mail servers are supposed to work (this is the first full-blown mail server I've set up)? There's no right or wrong way for an MTA to do this -- provided the MTA returns full headers with the bounce, it's done it's job. It doesn't even have to return the body of the message at all. Also, if MUAs are crashing when they receive these messages, they should be upgraded/fixed or discarded. However, returning attachments as attachments would be very problematic -- qmail would then have to parse the original message, determine if it was a MIME-encoded message, what type (multipart, etc.), decode each of the parts, and then generate a multipart bounce message, re-attaching and re-encoding the attachments from the first message. With that much parsing and text manipulation going on, qmail would have been _much_ more difficult to get BugFree (tm). Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ ---
Re: Bounce-backs with attachments, log files. . .
On Tue, Jun 26, 2001 at 05:01:36PM +0200, Peter van Dijk wrote: I think there is a patch. Yup. Fred Lindberg did it and it can be found on http://www.ezmlm.org/pub/patches/qmail-mime.tgz (also listed on http://www.qmail.org/ Yet More Qmail Addons) \Maex -- SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research Development | D-80807 Muenchen| Fax: +49 (89) 32356-299 Stress is when you wake up screaming and you realize you haven't fallen asleep yet.
Re: Qmail Errors in Log Files
Don't forget to check your /etc/inetd.conf. I've seen a few installs recently that were calling qmail from inetd. -sc On Wed, Mar 14, 2001 at 10:56:04PM -0800, Randy Jordan wrote: Delivered-To: [EMAIL PROTECTED] Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm Precedence: bulk Delivered-To: mailing list [EMAIL PROTECTED] From: "Randy Jordan" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Qmail Errors in Log Files Date: Wed, 14 Mar 2001 22:56:04 -0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 my qmail logs have thousands of these errors "40003ab04bb822ed854c tcpserver: fatal: unable to bind: address already used" I see hundreds of people with this same error and the same answers seem to always pop up"make sure something else is not using the port, or make sure sendmail is not running" i do not have sendmail running, when i telnet to localhost 25 i see this "Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 mail.mydomain.com ESMTP" There has got to be a way to fix this there is just to many people with the same problem. Thanks Randy Jordan -- Sean Chittenden[EMAIL PROTECTED] PGP signature
Qmail Errors in Log Files
my qmail logs have thousands of these errors "40003ab04bb822ed854c tcpserver: fatal: unable to bind: address already used" I see hundreds of people with this same error and the same answers seem to always pop up"make sure something else is not using the port, or make sure sendmail is not running"i do not have sendmail running, when i telnet to localhost 25 i see this "Trying 127.0.0.1...Connected to localhost.localdomain.Escape character is '^]'.220 mail.mydomain.com ESMTP" There has got to be a way to fix this there is just to many people with the same problem. Thanks Randy Jordan
Re: Qmail Errors in Log Files
On Wed, Mar 14, 2001 at 10:56:04PM -0800, Randy Jordan wrote: my qmail logs have thousands of these errors "40003ab04bb822ed854c tcpserver: fatal: unable to bind: address already used" You shouldn't run more than one MTA on one IP address (assuming this log is from qmail-smtpd). Make sure you haven't started qmail twice and you have stopped sendmail or any other mta. I see hundreds of people with this same error and the same answers seem to always pop up"make sure something else is not using the port, or make sure sendmail is not running" i do not have sendmail running, when i telnet to localhost 25 i see this "Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 mail.mydomain.com ESMTP" There has got to be a way to fix this there is just to many people with the same problem. Thanks Randy Jordan -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: Qmail Errors in Log Files
On Wed, Mar 14, 2001 at 10:56:04PM -0800, Randy Jordan wrote: my qmail logs have thousands of these errors "40003ab04bb822ed854c tcpserver: fatal: unable to bind: address already used" I see hundreds of people with this same error and the same answers seem to always pop up"make sure something else is not using the port, or make sure sendmail is not running" i do not have sendmail running, when i telnet to localhost 25 i see this "Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 mail.mydomain.com ESMTP" There has got to be a way to fix this there is just to many people with the same problem. Thanks Randy Jordan How do you start tcpserver?? There are most probably several tcpservers trying to run on port 25. Jörgen
Dailly log files
Hi, I'm using multilog and tcpserver, like lwq. Is there a way to patch multilog to create dailly log files. I mean in /var/qmail/log/send/ should be: 20010201.log 20010202.log ... Thanks, Ari
Re: logging to console and log files
On Wed, Feb 07, 2001 at 07:16:59AM +, Tim Hassan wrote: I actually liked that very much (if server is physically restricted) but there is one draw back; nothing will be logged to log/current. Therefore, I wandered if there is a way to have supervise log to both console and to qmail-send/log and/or qmail-smtpd/log. change /var/qmail/supervise/qmail-send/log/run to include exit 2/dev/console and change to multilog invocation in the same script from multilog \ options \ /whereever/qmail-send/log to multilog \ options \ /whereever/qmail-send/log \ +* \ e in other work: make use of the "e" option of the multilog process. See http://cr.yp.to/daemontools/multilog.html for more information. I'd actually hate that. Regards, Uwe
logging to console and log files
Hi, I setup once a qmail box and forgot to set the sticky bit (chmod +t) on the qmail-send and qmail-smtpd directories (in /var/qmail/supervise) so supervise was outputing everything to console. I actually liked that very much (if server is physically restricted) but there is one draw back; nothing will be logged to log/current. Therefore, I wandered if there is a way to have supervise log to both console and to qmail-send/log and/or qmail-smtpd/log. Any ideas? Tim Hassan
Relationship between the both qmail log files
-Original Message- From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] Sent: Friday, December 01, 2000 9:51 AM To: Wong, Wing-Kin Subject: ezmlm response Hi! This is the ezmlm program. I'm managing the [EMAIL PROTECTED] mailing list. Acknowledgment: I have added the address [EMAIL PROTECTED] to this mailing list. See http://pobox.com/~djb/qmail.html for more information about qmail. Please read http://pobox.com/~djb/qmail/faq.html before sending your question to the qmail mailing list. --- Here are the ezmlm command addresses. I can handle administrative requests automatically. Just send an empty note to any of these addresses: [EMAIL PROTECTED]: Receive future messages sent to the mailing list. Dear all, Are there any relationship between the both qmail log files of qmail-smtpd and qmail-send? If yes, how can i log the TCPREMOTEIP in the qmail-send log files? Thanks a lot! Best regards, Kent Wong Platform developer PCCW-HKT [EMAIL PROTECTED]
Re: Relationship between the both qmail log files
On Fri, Dec 01, 2000 at 11:07:51AM +0800, Wong, Wing-Kin wrote:
Are there any relationship between the both qmail log files of qmail-smtpd
and qmail-send?
No, there is no direct relationsship.
If yes, how can i log the TCPREMOTEIP in the qmail-send log files?
There is no support for this.
What we do (for accounting) is compile qmail with an extra delivery.
From FAQ
8.2. How do I keep a copy of all incoming and outgoing mail messages?
Answer: Set QUEUE_EXTRA to "Tlog\0" and QUEUE_EXTRALEN to 5 in extra.h.
Recompile qmail.
We have a ~alias/.qmail-log that contains the line
| awk '/^$/ { exit } /^[mM][eE][sS][sS][aA][gG][eE]-/ { print }
|/^[rR][eE][cC][eE][iI][vV][eE][dD]:/ { r=r+1; if (r==2) print; }'
Now the logfile shows lines like that
new msg 376799
info msg 376799: bytes 765 from [EMAIL PROTECTED] qp 20509 uid 101
starting delivery 570966: msg 376799 to local [EMAIL PROTECTED]
starting delivery 570975: msg 376799 to remote [EMAIL PROTECTED]
delivery 570966: success:
Received:_from_ns.space.net_(HELO_kronecker.space.net)_(195.30.0.1)/Message-ID:_[EMAIL PROTECTED]/did_0+0+1/
delivery 570975: success:
195.30.1.25_accepted_message./Remote_host_said:_250_ok_975625194_qp_27212/
end msg 376799
you can read that like that
msg 376799 - delivery 570966 this is the extra
- delivery 570975 this is the "normal"
The extra goes to the script and outputs
Received:_from_ns.space.net_..._(195.30.0.1)
and the Message-Id. You can now parse this line and extract the IP
address. This IP address belongs to the host that injected msg 376799
delivery 570966 - msg 376799
and now you know a lot about the message 376799
size 765 bytes
from [EMAIL PROTECTED]
to [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
From-IP: 195.30.0.1
You didn't write what you need the information for. Probably this can
be easier accomplished by patching qmail-smtpd.c
We've modified ours to output lines like
spamcheck: pid 24861: addrallowed: ns.space.net:195.30.0.1
1:[EMAIL PROTECTED] to [EMAIL PROTECTED]
Sorry, I can't provide a patch, as the modification is part of a heavily
hacked qmail-1.01 smtp server.
\Maex
--
SpaceNet AG | http://www.Space.Net/ | Stress is when you wake
Research Development| mailto:[EMAIL PROTECTED] | up screaming and you
Joseph-Dollinger-Bogen 14 | Tel: +49 (89) 32356-0| realize you haven't
D-80807 Muenchen | Fax: +49 (89) 32356-299 | fallen asleep yet.
meaning of the log files
Hi, In my /var/log/qmail/current file, I got some error messages that i would like to know what is the meaning. That is, "warning: trouble opening local/8/16131; will try again lager." Thank you so much for your help. Mark Lo
Re: meaning of the log files
On Tue, Nov 14, 2000 at 02:19:29AM +0800, Mark Lo wrote: In my /var/log/qmail/current file, I got some error messages that i would like to know what is the meaning. That is, "warning: trouble opening local/8/16131; will try again lager." qmail-send either failed to open the file /var/qmail/queue/local/8/16131 or to open, read or understand /var/qmail/queue/info/8/16131. Check especially the second one: for existance, readability and content (Fsender@domain\0 - the last character being an ASCII 0) Regards, Uwe
Re: meaning of the log files
On Tue, 14 Nov 2000 02:19:29 +0800, Mark Lo wrote: trouble opening local/8/16131; will try again lager." ^ ^^ Were you in the pub directory? I'll slip down to my local and have a beer! My many typos don't usually have a smile as a result. Thank your fingers for this one! In the beginning was The Word and The Word was Content-type: text/plain The Word of Rod.
Whrere are my log files?
Hello, I have configured qmail-send qmail-smtp to run under the daemon tools, according to qmail howto. For example I use the two following run script under /service/qmail-send/log/ #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s250 /var/log/qmail/qmail-send /var/log/qmail /var/log/qmail/qmail-send are owned by qmaill My problem is that ther is nothing inside the log directories
Re: Whrere are my log files?
"John Chronakis" [EMAIL PROTECTED] wrote: For example I use the two following run script under /service/qmail-send/log/ #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t s250 /var/log/qmail/qmail-send /var/log/qmail /var/log/qmail/qmail-send are owned by qmaill My problem is that ther is nothing inside the log directories Is multilog running? Is the sticky bit set on /service/qmail-send? -Dave
Re: Whrere are my log files?
Hello again, Is multilog running? Is the sticky bit set on /service/qmail-send? There are two instances of multilog running, one for qmai-send and one for qmail-smtpd. The sticky bit is set for /var/qmail/supervice/qmail-send (/service/qmail-send is a sim link to the former). I just worry if the /var/qmail/rc file is correct, because man qmail-start sais that default logger is splogger. Here it is. #!/bin/sh exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start './Maildir/' John
Re: Whrere are my log files? The blind man said.
I was blind !!! The cause off all these was a missing backslash in the /service/qmail-send/log/run file. Thanks for your help. John
How I deal with qmail log files
This little perl script is what I use to transform qmail log files into
something I can understand easily. Face it, the format of the log files is
hard to track with your eyes, to tell when a message actually worked, with
its repeating message numbers and delivery numbers...
I run it under a 'watch -n 1 mailwatch' in the background to keep an eye on
things, but also put in options for retrieving from other files, and
retrieving an arbitrary number of deliveries (mailwatch /var/log/maillog.2
125) and all the entries (mailwatch /var/log/maillog.1 -) (default is
mailwatch /var/log/maillog 18)
I didn't bother transforming the tai times with the localtime function, just
clipping out the times in the log file already myself. It would be trivial
to make the change though.
In its current incarnation, it prints out the messages that are recieved but
not delivered, and then prints out the specified number of entries (minus
the number of messages-in-delivery lines)
(it ignores everything with 'emon' in it, my little monitoring script, to
keep it from spamming my screen)
Its probably not complete, and not particularly efficient, but it sure
relaxes my mind when scanning current status.
David
--BEGIN PERL SCRIPT--
#!/usr/bin/perl
$| = 1;
my $logfile = $ARGV[0] ? $ARGV[0] : "/var/log/maillog";
if ($ARGV[1] eq "-") {
$length = 0;
@loglist = `cat $logfile`;
} elsif ($ARGV[1]) {
$length = $ARGV[1];
my $tail = $length * 50;
@loglist = `/usr/bin/tail --lines $tail $logfile`;
} else {
$length = "18";
@loglist = `/usr/bin/tail --lines 1000 $logfile`;
}
foreach (@loglist) {
if (/info msg (\d+): bytes (\d+) from \(.*?)\/) {
$from{$1} = $3;
$size{$1} = $2;
unless ($from{$1} =~ /\@/) {
$from{$1} = "BLANK-ADDRESS($from{$1})";
}
} elsif (/starting delivery (\d+): msg (\d+) to remote (.*?)$/) {
$msg2del{$2} = $1;
$del2msg{$1} = $2;
$addressee{$2} = $3
} elsif (/starting delivery (\d+): msg (\d+) to local (.*?)$/) {
$msg2del{$2} = $1;
$del2msg{$1} = $2;
$addressee{$2} = $3
} elsif (/(...).+delivery (\d+): success: /) {
if (exists $del2msg{$2}) {
# printf "%s SUCCESS: %8.8s From %30.30s to %30.30s\n", $1, $2,
$from{$del2msg{$2}}, $addressee{$del2msg{$2}};
$string = "$1 SUCCESS: From $from{$del2msg{$2}} delivered to
$addressee{$del2msg{$2}}";
unless ($string =~ /emon/) {
push @through, $string;
}
} else {
push @through, "orphan: no message info for delivery $2 ";
}
} elsif (/(...).+delivery (\d+): failure: (.*)$/) {
if (exists $del2msg{$2}) {
push @through, "$1 FAILED: From $from{$del2msg{$2}} to
$addressee{$del2msg{$2}}";
push @through, "$1 REASON: $3";
}
} elsif (/(...).+delivery (\d+): deferral: /) {
if (exists $del2msg{$2}) {
push @through, "$1 DEFERRED: From $from{$del2msg{$2}} to
$addressee{$del2msg{$2}}";
}
} elsif (/status: /) {
} elsif (/end msg (\d+)/) {
delete $from{$1};
delete $size{$1};
delete $msg2del{$del2msg{$1}};
delete $addressee{$del2msg{$1}};
delete $del2msg{$1};
} elsif (/new msg/) {
} elsif (/(...).*bounce msg (\d+)/) {
push @through, "$1 BOUNCE: from $from{$2} to $addressee{$2}";
} else {
print "error: no match $_";
}
}
open PIPE, "| cut -b -130";
$count = 0;
foreach (keys %from) {
$count ++;
unless (exists $msg2del{$_}) {
print PIPE "message from $from{$_} recieved and waiting for delivery\n";
} else {
print PIPE "message from $from{$_} to $addressee{$_} delivery in
process\n"
}
}
print PIPE "---OLDER---\n";
if ($length) {
$lines = $length - $count ;
$offset = $#through - ($lines);
} else {
$lines = $#through;
$offset = 0;
}
foreach (0..$lines) {
print PIPE "$through[$offset + $_]\n";
}
print PIPE "---NEWER---\n";
---END PERL SCRIPT-
-Original Message-
From: David Dyer-Bennet [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 31, 2000 10:54 AM
To: qmail list
Subject: Re: tai64n -- why?
[EMAIL PROTECTED] [EMAIL PROTECTED] writes on 31 July 2000 at 10:50:23
-0700
On Mon, Jul 31, 2000 at 12:23:38PM -0500, David Dyer-Bennet wrote:
Charles Cazabon [EMAIL PROTECTED] writes on 31 July 2000 at
11:20:48 -0600
David Dyer-Bennet [EMAIL PROTECTED] wrote:
Really? If I want to tail a log file, eg, I go like this:
tail ../someservice/current | tai64nlocal
and it all looks fine for humans.
Yeah, it works fine for people who check log files by tailing
them. I
check them by bringing them into an emacs buffer, so the funny
timestamps make them darned near useless.
So why not tail
