To my understanding, --enable-valias just stores alias info into the mysql database. This should not be affecting the delivery of email to non-aliased email, should it?
Matt > You compiled vpopmail to store its .qmail files in mysql by selecting > --enable-valias. Run ./configuration --help to get a summary of the > options and what they do. How did you decide which options to use? > > Regards, > > Tren > > ----- Original Message ----- > From: Matthew Goodman <[EMAIL PROTECTED]> > To: email@example.com <firstname.lastname@example.org> > Sent: Wed Jan 02 01:29:36 2008 > Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues > > I have created a script for now that will go through and create any users > that do not currently have a .qmail file and manually set one up. > > > > What would be a suitable .qmail file? Something like this? > > > > ---.qmail file for users without any maildrop rules to run--- > > > > |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir > > > > Iâm still not sure why this would break just because of an upgrade. Has > to be a vpopmail thing. Compile options are: > > > > ./configure \ > > --sysconfdir=/var/vpopmail/etc \ > > --enable-non-root-build \ > > --enable-qmaildir=/var/qmail \ > > --enable-qmail-newu=/var/qmail/bin/qmail-newu \ > > --enable-qmail-inject=/var/qmail/bin/qmail-inject \ > > --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh \ > > --enable-vpopuser=vpopmail \ > > --enable-vpopgroup=vpopmail \ > > --disable-many-domains \ > > --enable-file-locking \ > > --enable-file-sync \ > > --enable-md5-passwords \ > > --enable-logging=y \ > > --enable-auth-logging \ > > --enable-log-name=vpopmail \ > > --enable-qmail-ext \ > > --disable-tcp-rules-prog \ > > --disable-tcpserver-file \ > > --disable-roaming-users \ > > --enable-maildrop \ > > --enable-auth-module=mysql \ > > --enable-libs=/usr/include/mysql \ > > --enable-libdir=/usr/lib/mysql \ > > --enable-valias \ > > --disable-mysql-replication \ > > --enable-mysql-limits" > > > > > > From: Matthew Goodman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 01, 2008 9:15 AM > To: email@example.com > Subject: RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues > > > > As a workaround, Iâve added: > > > > |/var/qmail/bin/preline /usr/bin/maildrop /etc/mailfilter > > > > Into everyoneâs .qmail-default > > > > This delivers mail as if they checked the back âSpam Detectionâ. > > > > From: Tren Blackburn [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 01, 2008 4:25 AM > To: firstname.lastname@example.org > Subject: Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues > > > > 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: email@example.com <firstname.lastname@example.org> > 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: email@example.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:477bdf40310541600311831!