I've never run into that behaviour before. A .qmail in a users directory is not
required. I would recommend reverting back to your old version and do some
testing on a development box, virtual machine, or whatever you can test this on.
Perhaps also post more details about your environment, like operating system,
qmail version, configuration options, if you're building from source or using a
binary distribution (ie. rpm).
Hope that helps :) Happy New Year
Tren
- Original Message -
From: Matthew Goodman [EMAIL PROTECTED]
To: vchkpw@inter7.com vchkpw@inter7.com
Sent: Tue Jan 01 06:14:11 2008
Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
I should also add that I’ve got about 15,000 messages backed up. Yes, I know
14,982 are SPAM, but there are probably 18 useful ones in there somewhere J
Anyways, headed to bed, I’m starting to drift. Any thoughts would be useful.
From: Matthew Goodman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 01, 2008 4:03 AM
To: vchkpw@inter7.com
Subject: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Most of my domains in /var/vpopmail/domains/ have a .qmail-default file that
looks like this:
| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox
After upgrading from vpopmail 5.4.19 to 5.4.26, any user that was created using
QmailAdmin 1.2.10 that did NOT have the Spam Detection box checked is not
receiving their mail. This is because of absence of the .qmail file for the
user’s folder. I was under the impression that each user not having a .qmail
file is not bad in itself, as long as a .qmail-default file existed in the
parent folder for that domain.
Before this upgrade, this was not a problem seeing that a .qmail-default file
was in place at the root of each domain’s directory under
/var/vpopmail/domains. However, after the upgrade, these users (that don’t have
a .qmail file) are having all their messages dropped to their Maildir/tmp
folder.
I have no idea what is causing this. Replacing the .qmail-default with
something that resembles other user’s .qmail file fixes the problem, however,
this is not the preferred approach due to some configs being set for
catchall-delete or bounce or what-have-you.
Totally stuck on New Year’s. Hope yours is better than mine… any ideas here?
Matt
!DSPAM:477a4d27310546530436463!