smtproute logging
I am about to use smtproute to route some email to another email server. Does using smtproute log any messages when used? Steve Woolley [EMAIL PROTECTED]
qmailanalog
I am using qmail with the svscan method of supervising the processes. I would also like to use qmailanalog to do some stats/analysis. Under the old "inetd" method of process management. The qmail logs were under /var/log/qmail, now they are stored under /var/service/qmail/log/main. This is not a problem per se, but The timestamps under the old method were in the following form: 901967408.116537 now they are in the form: @40003a76ca281592e16c Is there some preprocessor that I am should run this through? or maybe some type of awk statement? Or should I be looking in a totally different place for my logs? Steve Woolley [EMAIL PROTECTED]
Re: qmailanalog
I apologize but I am unfamiliar with what you mean by Tai64nlocal Is this a command line option for multilog or something else? - Original Message - From: "Mike Jackson" [EMAIL PROTECTED] To: "Steve Woolley" [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 02, 2001 11:53 AM Subject: Re: qmailanalog Steve Woolley wrote: I am using qmail with the svscan method of supervising the processes. I would also like to use qmailanalog to do some stats/analysis. Under the old "inetd" method of process management. The qmail logs were under /var/log/qmail, now they are stored under /var/service/qmail/log/main. This is not a problem per se, but The timestamps under the old method were in the following form: 901967408.116537 now they are in the form: @40003a76ca281592e16c This is tai64 international format. Is there some preprocessor that I am should run this through? or maybe some type of awk statement? Or should I be looking in a totally different place for my logs? Tai64nlocal works for me. Mike
Moving qmail servers
I recently tried (unsuccessfully) to replace one of my qmail servers (Red Hat Linux 6.2) by: 1) creating new qmail server (lets call it mail2) 2) tar'ing up the following dirs: /var/qmail/control /var/qmail/queue /var/qmail/users /home/vpopmail/domains (cause I use vpopmail) /home/vpopmail/users (cause I use vpopmail) 3) stopping the qmail processes on mail1 (the qmail server to be replaced) and mail2 4) un-tar'ing the files on the mail2 5) shutdown server mail1 6) rename and re-IP mail2 to mail1 by editting the following: /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/hosts /etc/sysconfig/network /etc/HOSTNAME 7) bring up new qmail server (now known as mail1) The hopes were by following this pattern I would: * experience very little down time * if a problem occured, all I had to do was simply shutdown new qmail server and bring up old one * no DNS changes to make The only problem was it didn't work. Everything seemed to come up OK. Email could be queued up but would not get delivered UNTIL I bounced the box. In this case all the mail that was queued up got sent but any new mail still experienced the problem (it would queue up but would not be delivered until I rebooted the box). After a few frustrating attempts at fixing, I simply shut the new box down and brought up the old one. The only thing I could guess was the when qmail is compiled, I remember the instructions were specific about making sure (hostname -f) responded with the FQDN. Since at the time the box was compiled, the FQDN of the new qmail server was mail2.domainname.com, this caused some problem when I shifted the FQDN to mail1.domainname.com. Questions: Is their a better way to perform this task? Did I miss some key task when I renamed and re-IP'd the new qmail server? Steve Woolley [EMAIL PROTECTED]
Re: Moving qmail servers
The problem is probably with you moving the queue directory (which is a definite no-no, because the filenames in there must So would the proper order have been to: first: halt qmail processes on original qmail server then: copy /var/qmail/control and /var/qmail/users to new qmail server This would have halt qmail from accepting new emails. The transmitting email servers would have attempted a resend preiodically and once the new email server was up, everyone would be happy. Steve
smtproutes
I am planning to use smtproutes to route email from a qmail server to an internal Microsoft Exchange 5.5 server. If the Exchange server goes down for a period of time, will the qmail server cache (for lack of a better word) the routed emails locally until the Exchange server comes back up? or will the qmail server bounce the email back (after a given amount of time)? Steve Woolley [EMAIL PROTECTED]
Re: slow connection init
I added both the -R and -H options and the initial connection lag does not seem to have reoccurred. I will be trying the -R and the -H individually to isolate the problem. However, later in your note, you mentioned identd. I have removed this service from my exposed email and web servers because I heard they were security holes. I also thought identd was only for other hosts trying to id processes on my box and thus figured it was not needed. Could this be the problem? Steve - Original Message - From: "Andrew Richards" [EMAIL PROTECTED] To: [EMAIL PROTECTED]; "'Steve Woolley'" [EMAIL PROTECTED] Sent: Monday, January 22, 2001 2:35 PM Subject: RE: slow connection init flys (very fast). After aprox one day, any connection into this server (sshd, telnet , pop, smtp, etc) takes a while to initiate. Sometimes more than 60 seconds -- which of course times out most POP connections. Once connected, everything seems to act normal (connections initiated quickly). Steve, Also take a look at the -R, -H and -l options to tcpserver - these relate to DNS and identd lookups - try using all three (see the man page) and see if the behaviour of the box changes. If so, investigate why - then either leave these options in, or address the issues these options work around. cheers, Andrew.
slow connection init
I am running a Red Hat v6.2 (w/ patches) server on a AMD Athlon 800MHz with 256M RAM -- and have been fairly pleased with its performance. The problem is I want to migrate my existing RH 6.2 qmail mail server (a slower Pentium II). The problem is, when first started the server flys (very fast). After aprox one day, any connection into this server (sshd, telnet , pop, smtp, etc) takes a while to initiate. Sometimes more than 60 seconds -- which of course times out most POP connections. Once connected, everything seems to act normal (connections initiated quickly). I have looked into the logs and looked at netsat -pa to get some insight into this slowdown, but have not had very good luck. I know this is probably not directly related to qmail, but I am a little woried about the svscan process and how quickly it can wake up a process. P.S I can see the correct processes running when I get in this process initiation hang so I don't think they've died. Could it be some reverse name resolution problem? HELP!?!?!?! -- Steve Woolley [EMAIL PROTECTED]
Re: slow connection init
I had this problem with my mail server as well... qmail logs extensively, and if you have it using the generic logging stuffs, the files get HUGE and the entire system drags like a dog. Thanks for the input Teep. Since this is a new box (and I also verified) the size of the log files are (so far) very small. Thx
Re: Trouble compiling qmail under RedHat v6.2 Intel
Peter Green wrote: Either re-install (with --force) kernel-headers to get all of the proper symlinks back, or check the following: After doing this I got ALOT further, unfortunately it crapped out on: ... ... rm -f tryshsgr.o tryshsgr ./compile prot.c ./compile coe.c ./compile cdb_hash.c ./compile cdb_unpack.c ./compile cdb_seek.c cdb_seek.c: In function `cdb_bread': cdb_seek.c:19: `EINTR' undeclared (first use in this function) cdb_seek.c:19: (Each undeclared identifier is reported only once cdb_seek.c:19: for each function it appears in.) cdb_seek.c:21: `EIO' undeclared (first use in this function) make: *** [cdb_seek.o] Error 1 Sorry if it seems I am a neophyte at this. It is only becuase I am. Thanks for your help. Steve
Re: Trouble compiling qmail under RedHat v6.2 Intel
Petr Novotny wrote: ./compile sig_alarm.c In file included from /usr/include/signal.h:300, from sig_alarm.c:1: /usr/include/bits/sigcontext.h:28: asm/sigcontext.h: No such file or You need glibc-devel and kernel-headers packages. I checked and I believe I have these: [root@myhost /root]# rpm -q kernel-headers kernel-headers-2.2.16-3 [root@myhost /root]# rpm -q glibc glibc-2.1.3-15 [root@myhost /root]# rpm -q glibc-devel glibc-devel-2.1.3-15 Any other thoughts? Thanks for your response. Steve
Trouble compiling qmail under RedHat v6.2 Intel
I am having trouble compiling qmail from the source distribution unde RedHat 6.2 Intel. According to the README's I should not have to anything special to compile but I seem to be blowing up because of a simple standard header file not being found. I know I could probably go back and locate each one of these files but I normally do not have this kind of problem when compiling source. Am I missing some key PATH setting or key piece of info to compiling this properly? Steve Woolley Compilation output: [swoolley@myhost qmail-1.03]$ make ( cat warn-auto.sh; \ echo CC=\'`head -1 conf-cc`\'; \ echo LD=\'`head -1 conf-ld`\' \ ) auto-ccld.sh cat auto-ccld.sh make-load.sh make-load chmod 755 make-load cat auto-ccld.sh find-systype.sh find-systype chmod 755 find-systype ./find-systype systype ( cat warn-auto.sh; ./make-load "`cat systype`" ) load chmod 755 load cat auto-ccld.sh make-compile.sh make-compile chmod 755 make-compile ( cat warn-auto.sh; ./make-compile "`cat systype`" ) \ compile chmod 755 compile ( ( ./compile tryvfork.c ./load tryvfork ) /dev/null \ 21 \ cat fork.h2 || cat fork.h1 ) fork.h rm -f tryvfork.o tryvfork ./compile qmail-local.c qmail-local.c: In function `main': qmail-local.c:448: warning: return type of `main' is not `int' ./compile qmail.c ./compile quote.c ./compile now.c ./compile gfrom.c ./compile myctime.c ./compile slurpclose.c cat auto-ccld.sh make-makelib.sh make-makelib chmod 755 make-makelib ( cat warn-auto.sh; ./make-makelib "`cat systype`" ) \ makelib chmod 755 makelib ./compile case_diffb.c ./compile case_diffs.c ./compile case_lowerb.c ./compile case_lowers.c ./compile case_starts.c ./makelib case.a case_diffb.o case_diffs.o case_lowerb.o \ case_lowers.o case_starts.o ./compile getln.c ./compile getln2.c ./makelib getln.a getln.o getln2.o ./compile subgetopt.c ./compile sgetopt.c ./makelib getopt.a subgetopt.o sgetopt.o ./compile sig_alarm.c In file included from /usr/include/signal.h:300, from sig_alarm.c:1: /usr/include/bits/sigcontext.h:28: asm/sigcontext.h: No such file or directory make: *** [sig_alarm.o] Error 1
