qmail Digest 18 Oct 1999 10:00:01 -0000 Issue 793
Topics (messages 31775 through 31799):
Re: SMTP Help.
31775 by: Sam
Re: Wrong date when qmail is called from /bin/mail
31776 by: Todd A. Jacobs
31778 by: farber.admin.f-tech.net
31780 by: David Dyer-Bennet
31788 by: Todd A. Jacobs
31790 by: Todd A. Jacobs
Re: qmail dies 2 times a day, at least
31777 by: Vince Vielhaber
Re: Messages in queue, not preprocessed, why?
31779 by: Chris Green
Re: qmail only delivers when restarted
31781 by: David Dyer-Bennet
31789 by: Todd A. Jacobs
31791 by: David Dyer-Bennet
Re: Frequency of queue processing
31782 by: Rogerio Brito
Problems with trigger? (was: Re: qmail only delivers when restarted)
31783 by: Rogerio Brito
31784 by: David Villeger
31785 by: David Villeger
31799 by: Chris Green
mail appliance
31786 by: Jon Rust
adding Mailbox contents to a Maildir
31787 by: Cris Daniluk
31793 by: Mikko Hänninen
Re: memphis rpm
31792 by: Peter Samuel
Disk Space
31794 by: Matt Mouser
31795 by: Adam D . McKenna
Re: target dependent smart host?
31796 by: Anand Buddhdev
Relaying.
31797 by: Tony Wade
31798 by: Anand Buddhdev
Administrivia:
To subscribe to the digest, e-mail:
[EMAIL PROTECTED]
To unsubscribe from the digest, e-mail:
[EMAIL PROTECTED]
To bug my human owner, e-mail:
[EMAIL PROTECTED]
To post to the list, e-mail:
[EMAIL PROTECTED]
----------------------------------------------------------------------
On Sat, 16 Oct 1999, Larry H. Raab wrote:
> Well...the question I asked is if it was an OK place to put it.
> If INETD.CONF isn't a boot script could you tell me a better place to put it
> that might be a boot script?
You will find that in the documentation for your specific operating
system. Different systems use different boot scripts.
On Sat, 16 Oct 1999 [EMAIL PROTECTED] wrote:
> Look at the end of the timestamps.... one is ZULU or GMT.. the other is
> your "local" time PDT (Pacific Daylight Time).
So /bin/mail doesn't recognize the local time format?
--
Todd A. Jacobs
Network Systems Engineer
/bin/mail is not putting the headers on your mail.. the MTA/MUA is (ie
sendmail/qmail and pine).
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On Sat, 16 Oct 1999, Todd A. Jacobs wrote:
> On Sat, 16 Oct 1999 [EMAIL PROTECTED] wrote:
>
> > Look at the end of the timestamps.... one is ZULU or GMT.. the other is
> > your "local" time PDT (Pacific Daylight Time).
>
> So /bin/mail doesn't recognize the local time format?
>
> --
> Todd A. Jacobs
> Network Systems Engineer
>
>
>
Todd A. Jacobs <[EMAIL PROTECTED]> writes on 16 October 1999 at 17:06:47 -0700
> My date offset seems to have aquired a problem since I moved from sendmail
> to qmail when mailing from the command-line using /bin/mail under Red Hat
> 6.0. I get the following date:
>
> Date: 16 Oct 1999 23:55:55 -0000
>
> while sending from pine returns:
>
> Date: Sat, 16 Oct 1999 16:57:35 -0700 (PDT)
>
> Any ideas as to what's wrong, and how I can fix it?
Nothing is wrong; the first date says just before midnight GMT (that's
what the "-0000" means. The second date shows just before 5pm Pacific
Daylight Time (that's what the "-0700" means). Assuming you performed
those two tests one minute and 40 seconds apart, everything is working
perfectly.
qmail uses GMT for any header timestamps it adds because: When
tracing mail across timezones, it's easier if they're all displayed in
the same timezone, and because if you want them displayed any
particular way that's a good task to assign to the displaying program,
*and* because by not trying to find the local timezone, Dan avoids
having to reimplement that part of the standard C library (he avoids
using the standard C library because it's insecure and buggy on too
many systems).
--
David Dyer-Bennet **Update your records, forwarding expires soon** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
On Sun, 17 Oct 1999 [EMAIL PROTECTED] wrote:
> /bin/mail is not putting the headers on your mail.. the MTA/MUA is (ie
> sendmail/qmail and pine).
But it used to when running under sendmail. Someone else told me that
qmail defaults to using zulu. Is there a way to force it to use local
time, instead of GMT?
--
Todd A. Jacobs
Network Systems Engineer
On Sun, 17 Oct 1999, David Dyer-Bennet wrote:
> qmail uses GMT for any header timestamps it adds because: When
> tracing mail across timezones, it's easier if they're all displayed in
> the same timezone, and because if you want them displayed any
> particular way that's a good task to assign to the displaying program,
> *and* because by not trying to find the local timezone, Dan avoids
> having to reimplement that part of the standard C library (he avoids
> using the standard C library because it's insecure and buggy on too
> many systems).
Ah! That's a reason I can understand, and can live with. :) Security is a
big issue at my site, so anything that enhances security is okay by me. I
just like having a reason. Thanks for the info.
--
Todd A. Jacobs
Network Systems Engineer
On 17-Oct-99 Gustavo V G C Rios wrote:
> Dear gentleman,
>
> I am running qmail, and it's dying at least 2 times a single day.
> I decided to run ktrace for it, here is what i got:
What do the logs say? Are there any entries about it?
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
# include <std/disclaimers.h> Have you seen http://www.pop4.net?
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
On Sat, Oct 16, 1999 at 05:49:07PM -0400, Chris Johnson wrote:
> On Sat, Oct 16, 1999 at 10:40:11PM +0100, Chris Green wrote:
> > I have just moved my qmail installation from RedHat 5.2 Linux to
> > Mandrake 6.1 Linux (RedHat 6.1 based).
> >
> > I have got just about everything working, the local tests seem to work
> > but when I do qmail-qstat I get:-
> >
> > messages in queue: 16
> > messages in queue but not yet preprocessed: 16
> >
> > It stays like this for a long time (15 minutes or so) and then
> > suddenly delivers everything, does anyone have any idea what the
> > problem might be?
>
> All together now...
>
> Check the permissions on /var/qmail/queue/lock/trigger. They should look like
> this:
>
> prw--w--w- 1 qmails qmail 0 Oct 16 17:39 trigger
>
Ah, OK, thanks! :-)
Of course being a named pipe my copy messed up the permissions.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
Chris Johnson <[EMAIL PROTECTED]> writes on 16 October 1999 at 21:24:31 -0400
> On Sat, Oct 16, 1999 at 05:33:00PM -0700, Todd A. Jacobs wrote:
> > For some reason, qmail has gotten into a state where it will only deliver
> > mail when killed and then restarted. After a restart, it refuses to
> > deliver local mail after the first batch has been processed.
>
> This is the third time this has come up in the past day and a half.
>
> Check the permissions on /var/qmail/queue/lock/trigger. They should look like
> this:
>
> prw--w--w- 1 qmails qmail 0 Oct 16 17:39 trigger
And I asked after the first time if anybody had any idea what caused
this to happen; I haven't seen any responses / suggestions yet. I'm
not particularly suspicious that qmail somehow does it to itself,
mind. But it comes up *so often* that I'd really like to know how it
happens. I haven't done it yet, and I'd like to keep it that way :-)
.
--
David Dyer-Bennet **Update your records, forwarding expires soon** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
On Sun, 17 Oct 1999, David Dyer-Bennet wrote:
> > Check the permissions on /var/qmail/queue/lock/trigger. They should look like
> > this:
> >
> > prw--w--w- 1 qmails qmail 0 Oct 16 17:39 trigger
That was definitely the problem in my case. I'm not sure how it changed,
though. If I find out, I promise you'll be the second one to know. :)
I couldn't find any info on the trigger file. Can you explain how qmail is
using this named pipe, and why it has to be world-writable?
--
Todd A. Jacobs
Network Systems Engineer
Todd A. Jacobs <[EMAIL PROTECTED]> writes on 17 October 1999 at 15:43:35 -0700
> On Sun, 17 Oct 1999, David Dyer-Bennet wrote:
>
> > > Check the permissions on /var/qmail/queue/lock/trigger. They should look like
> > > this:
> > >
> > > prw--w--w- 1 qmails qmail 0 Oct 16 17:39 trigger
>
> That was definitely the problem in my case. I'm not sure how it changed,
> though. If I find out, I promise you'll be the second one to know. :)
>
> I couldn't find any info on the trigger file. Can you explain how qmail is
> using this named pipe, and why it has to be world-writable?
I haven't examined this bit of source just recently, but very roughly,
qmail-inject uses this to alert the central q-management process that
there's new business waiting. Since qmail-inject runs as any user
sending mail, the trigger needs to be world-writable. I'm sure the
process on the other end of that pipe is *very* careful what it does
with whatever comes through it!
--
David Dyer-Bennet **Update your records, forwarding expires soon** [EMAIL PROTECTED]
http://dd-b.lighthunters.net/ (photos) Minicon: http://www.mnstf.org/minicon
http://www.dd-b.net/dd-b (sf) http://ouroboros.demesne.com/ Ouroboros Bookworms
Join the 20th century before it's too late!
On Oct 16 1999, Russell Nelson wrote:
> Todd A. Jacobs writes:
> > How can I modify the frequency at which qmail processes the queue?
>
> You can't, because qmail doesn't "process the queue". Each message
> has its own retry schedule, and qmail-send sleeps until the next
> message needs to be retried. Somebody figured it out -- I think it's
> in Dave Sill's LWQ document.
This is something I had the pleasure of discussing with Dave
Sill some time ago:
As far as I know, qmail has 2 channels (as DJB seems to call
them) of messages: the local and the remote channels.
The formula for the time of a "next delivery" of a message
that has not yet been successfully delivered *after* the i-th
time it was tried is:
next_retry = birth + (i*c)^2,
where birth is the time when the message has first entered the
queue, c = 10 for local messages and c = 20 for remote
messages.
So, if you make a table of those values for c = 20 (that is
remote deliveries) and i = 0, ..., 39, you should get the
table Dave Sill has put on his site.
The relevant code is in qmail-send.c, function nextretry().
> What problem are you trying to solve?
He is problem is probably related to trigger not being group
and world writable, me thinks...
[]s, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
On Oct 17 1999, David Dyer-Bennet wrote:
> And I asked after the first time if anybody had any idea what caused
> this to happen; I haven't seen any responses / suggestions yet. I'm
> not particularly suspicious that qmail somehow does it to itself,
> mind. But it comes up *so often* that I'd really like to know how it
> happens. I haven't done it yet, and I'd like to keep it that way :-)
> .
To this day, I still don't know. Some people suspect there is
some tarball phase involved, but we can never be sure (newbies
won't know nor they will admit doing something wrong). :-)
Anyway, mine has always worked fine, even after I make a
backup of my queue. Who knows? :-)
[]s, Roger...
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Rogerio Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito/
Nectar homepage: http://www.linux.ime.usp.br/~rbrito/opeth/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>On Oct 17 1999, David Dyer-Bennet wrote:
>> And I asked after the first time if anybody had any idea what caused
>> this to happen; I haven't seen any responses / suggestions yet. I'm
>> not particularly suspicious that qmail somehow does it to itself,
>> mind. But it comes up *so often* that I'd really like to know how it
>> happens. I haven't done it yet, and I'd like to keep it that way :-)
This is most likely caused by people trying to copy /var/qmail using "cp -r".
It could also be that they copy /var/qmail using tar but not as root and
not using the -p option (if the user is not root tar will use the current
umask with the -x option).
Maybe (needs to be checked) installing qmail as a user different from root
has the same impact.
David.
______________________________________
David Villeger
(212) 673 6100 ext 264
http://www.CheetahMail.com
The Internet Email Publishing Solution
>Maybe (needs to be checked) installing qmail as a user different from root
>has the same impact.
>
>David.
No... that's ridiculous. Qmail doesn't untar the named pipe, it creates it.
I am convinced this problem is caused by people who try to copy /var/qmail
and don't do it right.
David.
______________________________________
David Villeger
(212) 673 6100 ext 264
http://www.CheetahMail.com
The Internet Email Publishing Solution
On Sun, Oct 17, 1999 at 05:10:38PM -0400, David Villeger wrote:
> >Maybe (needs to be checked) installing qmail as a user different from root
> >has the same impact.
> >
> >David.
>
> No... that's ridiculous. Qmail doesn't untar the named pipe, it creates it.
>
> I am convinced this problem is caused by people who try to copy /var/qmail
> and don't do it right.
>
That was certainly how I managed to screw it up. I upgraded from
Linux RedHat 5.2 to Mandrake 6.1, I had a new drive to install on so
just mounted the old RedHat drive on the new system so I could copy
files across and so on.
I copied the qmail installation basically by doing:-
cp -R /oldvar/qmail/* /var/qmail
The things I forgot were:-
1 - The tcpserver executables etc. in /usr/local/bin, this was easy to
find as I got an error in the logs about them being missing. I also
forgot the checkpassword binary in /bin.
2 - I forgot to add all the qmail users and groups! Hmmmm!!! This
screwed things up thoroughly until I realised what I had done.
3 - Sundry permission and ownership problems but these were fairly
easy to fix by looking at the error logs (things such as writable home
directories) and by comparing with the old installation (ownership
etc. in the /var/qmail area). The final thing was the permissions on
the trigger file, which I asked about here.
I have to say it wasn't too painful and I didn't lose *any* mail in
the process which was quite pleasing. I did bounce a few messages
initially before I managed to get rid of sendmail and postfix both of
which are installed in the default Mandrake 6.1 setup.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
I'm trying to build a mail "appliance" that I can install for
customers who know nothing about UNIX and/or qmail. I suppose webmin
will do for adding users, though a bit clumsy. Even so, that still
leaves forwarding and vacation messages out. I'll try to write some
scripts of my own for this purpose, but if someone wants to share,
that would be great. Just looking for some no-frills, perl/shell CGI.
thanks,
jon
Is there an existing script that will merge a Mailbox into an existing
Maildir? We're trying to combine two existing servers into one, but one uses
Maildir and the other uses Mailbox. I'd write my own, but just as soon use
an existing one if available
Thanks
Cris Daniluk - [EMAIL PROTECTED]
Digital Services Network, Inc - http://www.dsnet.net/
(330)609-8624 ext 20 - Fax (330)609-9990
Cris Daniluk <[EMAIL PROTECTED]> wrote on Sun, 17 Oct 1999:
> Is there an existing script that will merge a Mailbox into an existing
> Maildir? We're trying to combine two existing servers into one, but one uses
> Maildir and the other uses Mailbox. I'd write my own, but just as soon use
> an existing one if available
If you have mutt installed, it's fairly easy to create a mutt
commandline that does this, something like:
mutt -f =mboxfolder -e 'push "T~A\n\;s=maildirfolder\nq"'
(just off the top of my head, so you'd need to check and possibly
further develop that, also note if you don't have $folder set
appropriately for Mutt, then you need to use full paths instead of
the = shortcut)
Apparently I also have a mbox2maildir perl script, the credits of which
say:
# put into the public domain by Bruce Guenter <[EMAIL PROTECTED]>
# based heavily on code by Russell Nelson <[EMAIL PROTECTED]>
I imagine I got this from the qmail page, but I'd be happy to mail it
to you if you can't find it there or elsewhere.
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list maintainer // net.freak // DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
"OK, who stopped the payment on my reality check?"
On Fri, 15 Oct 1999, Mate Wierdl wrote:
> On Fri, Oct 15, 1999 at 10:13:16AM +1000, Peter Samuel wrote:
> > On Thu, 14 Oct 1999, Mate Wierdl wrote:
> >
> > > I have no idea how the vacation package work.
> > >
> > > But: the installation of the memphis rpm has changed. In
> > > particular, you also need qmail-run. Is qmail working properly,
> > > otherwise?
> >
> > The problem isn't vacation per se (Jon and I have already debugged
> > thru that poart). The problem is that if you have a .qmail file of the
> > form
> >
> > | some_program
> >
> > and "some_program" calls qmail-inject (or one of its cousins such as
> > datemail etc), qmail-inject dies.
> >
> > I've asked Jon to triple check permissions of files in
> > /var/qmail/control to ensure they are readable by all.
> >
>
> And this is only with the memphis rpm? Do you also have the problem?
> I just did:
> [wierdlm@moni wierdlm]$ echo '|./hello.sh' > .qmail
> [wierdlm@moni wierdlm]$ echo '#!/bin/sh
> > echo hello | qmail-inject mw
> > ' > hello.sh
> [wierdlm@moni wierdlm]$ chmod +x hello.sh
> [wierdlm@moni wierdlm]$ echo |qmail-inject wierdlm
>
> and mw received:
I don't have the problem. But I don't use the RPMS - I build from the
source distro.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
Hi,
I was wondering how small could I get Qmail down in file size? I am only
talking about the binaries and config files. All the user mail boxes and
stuff won't be a problem. The reason I ask is because I run a different
linux distro that stores all my os and daemons in a ramdisk. This is great.
Right now everything boots off a floppy (exim and qpopper) and then loads in
ram, and I have all my user files stored on hard drives. I wish to do the
same thing with qmail. All the current packages I use are just tarred
gzipped files. How small can I get qmail's binaries and config files down
to? I would love to use Qmail as it has tons more vhosting features than
other mailservers and is way more scaleable. Thanks for your help.
Matt
You could try stripping the binaries. I think they're already stripped
though.
man strip
besides that, I hope you are putting your queue on a real disk, because if
you're not, it'll be lost every time you reboot.
--Adam
On Sun, Oct 17, 1999 at 09:26:01PM -0700, Matt Mouser wrote:
> Hi,
>
> I was wondering how small could I get Qmail down in file size? I am only
> talking about the binaries and config files. All the user mail boxes and
> stuff won't be a problem. The reason I ask is because I run a different
> linux distro that stores all my os and daemons in a ramdisk. This is great.
> Right now everything boots off a floppy (exim and qpopper) and then loads in
> ram, and I have all my user files stored on hard drives. I wish to do the
> same thing with qmail. All the current packages I use are just tarred
> gzipped files. How small can I get qmail's binaries and config files down
> to? I would love to use Qmail as it has tons more vhosting features than
> other mailservers and is way more scaleable. Thanks for your help.
>
> Matt
>
On Sat, Oct 16, 1999 at 12:28:38PM +0200, [EMAIL PROTECTED] wrote:
> Hi,
> my linux box is using a dial up line to connect
> to the internet.
> The system is configured to store outgoing mail
> in /var/qmail/alias/pppdir.
> These mails are send automatically, after a connect
> to the ISP. Local mail is delivered immediately.
> So far, so good.
>
> Now I set up an wireless data connection to a
> friend, he's staying not far form me.
> All mails to his host (or to his LAN) should be
> deliverd immediately through this wireless link.
>
> How can I tell my system ....
>
> 1.) Mail to cassiopeia.qad.org is local, deliver now,
> because it is my local linux box
> 2.) Mail to every host in the domain deepthinker.de
> should be deliverd to the smart host dick.deepthinker.de
> immediately (the IP-Route is set in proper style).
>
> 3.) All other Mail should be colleted in /var/qmail/alias/pppdir
> and send out by starting 'maildirsmtp'.
You probably have an entry in your control/virtualdomains file like
this:
:alias-ppp
which traps _all_ non-local mail and puts it into pppdir. You need to
make an exception to this entry, to tell qmail that "deepthinker.de" is
really remote. Add the following line to control/virtualdomains
deepthinker.de:
and HUP qmail-send. Mails for your friend will go over your wireless
link.
See "man qmail-send" for details of this "exception" feature.
--
See complete headers for more info
Hi all,
I seem to have a relaying problem with 2 servers that i have worked on.
I installed Qmail-1.03
ucspi-tcp-0.84
checkpassword-0.81
I put all the relevant domain details in /var/qmail/control/rcpthosts
what happens is in both instances a Exchange server forwards the mail to the
Qmail server.
The Qmail server then rejects the mail saying, "Domain not in rcpthosts"
tcpserver runs with the following command ( not sure if this is actually
what controls the Relaying)
tcpserver -c 1000 -u 71 -g 80 0 smtp /var/qmail/bin/qmail-smtpd x
/etc/tcp.smtp.cdb &
in the file /etc/tcp.smtp
123.123.123.:allow,RELAYCLIENT=""
If i remove the rcpthosts file. Do i not make the server an Open Relay
server again ?
How do i set the relaying correctly ?
Tony Wade
On Mon, Oct 18, 1999 at 09:34:01AM +0200, Tony Wade wrote:
> I put all the relevant domain details in /var/qmail/control/rcpthosts
>
> what happens is in both instances a Exchange server forwards the mail to the
> Qmail server.
>
> The Qmail server then rejects the mail saying, "Domain not in rcpthosts"
>
> tcpserver runs with the following command ( not sure if this is actually
> what controls the Relaying)
>
> tcpserver -c 1000 -u 71 -g 80 0 smtp /var/qmail/bin/qmail-smtpd x
> /etc/tcp.smtp.cdb &
>
> in the file /etc/tcp.smtp
That line is wrong. All the tcpserver options must come first, before
the qmail-smtpd invocation. Try instead:
tcpserver -c1000 -u71 -g80 -x/etc/tcp.smtp.cdb 0 smtp /var/qmail/bin/qmail-smtpd &
> 123.123.123.:allow,RELAYCLIENT=""
>
> If i remove the rcpthosts file. Do i not make the server an Open Relay
> server again ?
_Don't_ do that. A server with no rcpthosts file is an open relay!!
--
See complete headers for more info
