RE: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Well I'm glad you asked that question, after rebuilding maildrop, I noticed it *overwrote* my /etc/maildroprc file. Normally, it is a symlink to /etc/mailfilter. So when it overwrote the maildroprc symlink I had created, it brought with it the .maildir reference. Thank you for asking the question :) It spurred some more investigation to get the problem fixed. So far in the time it took to write this, over 500 messages were cleared from the queue :) Looks like it may be finally good to go. Matt -Original Message- From: Tom Collins [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 02, 2008 2:40 PM To: vchkpw@inter7.com Subject: Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues On Jan 2, 2008, at 3:05 PM, Matthew Goodman wrote: > @4000477c1866206baccc delivery 30202: deferral: > /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/ > vpopmail/./.maildir/25184.0.ark.// > > I see a few of these... aside from the usual "Unable to create log > file" > error that maildrop kicks out for aliases or emails that don't > belong to > actual accounts. > > Any ideas? Why does maildrop want to use .maildir instead of Maildir? Odd that it wants to use the vpopmail directory instead of a user's directory as well... -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477c78e9310545571378502!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
On Jan 2, 2008, at 3:05 PM, Matthew Goodman wrote: @4000477c1866206baccc delivery 30202: deferral: /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/ vpopmail/./.maildir/25184.0.ark.// I see a few of these... aside from the usual "Unable to create log file" error that maildrop kicks out for aliases or emails that don't belong to actual accounts. Any ideas? Why does maildrop want to use .maildir instead of Maildir? Odd that it wants to use the vpopmail directory instead of a user's directory as well... -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477c2eeb310543570762282!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Here's an odd one: @4000477c1866206baccc delivery 30202: deferral: /usr/bin/maildrop:_Unable_to_create_a_dot-lock_at_/var/vpopmail/./.maildir/25184.0.ark.// I see a few of these... aside from the usual "Unable to create log file" error that maildrop kicks out for aliases or emails that don't belong to actual accounts. Any ideas? > On Jan 2, 2008, at 11:13 AM, Matthew Goodman wrote: >> My customers use Qmailadmin to administer their email boxes. For some >> reason, when they create an account using Qmailadmin, unless they >> "Enable >> Spam Detection" a .qmail file is NOT created. Is this normal >> behavior from >> what you know of it? I suppose this might be the wrong list, but >> again, >> Qmailadmin's behavior does not explain why after the upgrade >> Vpopmail has >> a problem delivering mail. > > > This is normal behavior -- if email should just be placed in the > user's Maildir, no .qmail file is necessary. > > It sounds like your vdelivermail is having problems. Have you > checked the qmail-send logs? It should be showing you why there's a > temp failure. > > I am personally using 5.4.20 on my system, and according to the CVS > logs, vdelivermail in 5.4.26 is the same as in 5.4.20. > > -- > Tom Collins - [EMAIL PROTECTED] > Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ > QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ > > > > > > !DSPAM:477c18c2310546724113822!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
On Jan 2, 2008, at 11:13 AM, Matthew Goodman wrote: My customers use Qmailadmin to administer their email boxes. For some reason, when they create an account using Qmailadmin, unless they "Enable Spam Detection" a .qmail file is NOT created. Is this normal behavior from what you know of it? I suppose this might be the wrong list, but again, Qmailadmin's behavior does not explain why after the upgrade Vpopmail has a problem delivering mail. This is normal behavior -- if email should just be placed in the user's Maildir, no .qmail file is necessary. It sounds like your vdelivermail is having problems. Have you checked the qmail-send logs? It should be showing you why there's a temp failure. I am personally using 5.4.20 on my system, and according to the CVS logs, vdelivermail in 5.4.26 is the same as in 5.4.20. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477c0bcc310541768617602!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
On Jan 2, 2008, at 2:08 PM, Tom Collins wrote: Correct. --enable-valias means that instead of using .qmail-alias files in the domain directory, aliases are stored in the database. Isn't it "in addition to using .qmail-alias files" not "instead of"? !DSPAM:477be750310541330512215!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
Ok, I took your advice and instead switched each users .qmail file (that did not have one setup) to utilize the maildrop command that Qmailadmin enables once "Spam Detection" is checked. This seems to work. It's |/var/qmail/bin/preline /usr/bin/maildrop /etc/mailfilter My customers use Qmailadmin to administer their email boxes. For some reason, when they create an account using Qmailadmin, unless they "Enable Spam Detection" a .qmail file is NOT created. Is this normal behavior from what you know of it? I suppose this might be the wrong list, but again, Qmailadmin's behavior does not explain why after the upgrade Vpopmail has a problem delivering mail. I see about 11,000 messages in the qmail queue at the moment. None of them are being delivered. Users have messages backed up in their /Maildir/tmp folder from several days ago. qmailctl flush does not force the delivery of all these items. The actual setup looks like this: netqmail-1.05, qmail-scanner-2.01-st, vpopmail 5.4.26 - all compiled from Gentoo ebuilds. The vpopmail ebuild I sort of made by hand, so as much as possible I investigate the ebuilds carefully for strange/rogue settings and such. As I stated before, things were working fine with vpopmail 5.4.17 since July without a hitch. I just have to confess that my guru-ness with vpopmail is limited, so this problem is a bit more elusive than my own abilities can track. At any rate, any thoughts would be helpful. > On Jan 2, 2008, at 1:29 AM, Matthew Goodman wrote: >> ---.qmail file for users without any maildrop rules to run--- >> >> |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir > > > No! You don't want to do this. > > Reminder to everyone in the world -- vdelivermail should only be in > your .qmail-default file. Never anywhere else. > > I'm not sure I understand why your installation of 5.4.26 isn't > working -- if there isn't a .qmail file, the message should just go > into the user's maildir. > > If you absolutely MUST have a .qmail file, it will just contain a > single line -- the path to that user's Maildir. > > Keep in mind that with directory hashing, their maildir might not be > in domains/%d/%u/Maildir. > > You could try using just ./Maildir and see if that works -- I think > vdelivermail is already in the user's directory when it's parsing > the .qmail file. > > -- > Tom Collins - [EMAIL PROTECTED] > Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ > QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ > > > > > > !DSPAM:477be26d310542003195226!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
On Jan 2, 2008, at 10:59 AM, Matthew Goodman wrote: 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? Correct. --enable-valias means that instead of using .qmail-alias files in the domain directory, aliases are stored in the database. It does not affect individual user .qmail files. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477be152310542880817634!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
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: vchkpw@inter7.com > 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: vchkpw@inter7.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: vchkpw@inter7.com > 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: 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 f
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues [ATTN maintainers]
On 1/2/2008 11:18 AM, Tom Collins wrote: >On Jan 2, 2008, at 1:29 AM, Matthew Goodman wrote: |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir No! You don't want to do this. Reminder to everyone in the world -- vdelivermail should only be in your .qmail-default file. Never anywhere else. When you think you want to use vdelivermail somewhere besides .qmail-default, you actually probably want to use maildirdeliver: http://www.din.or.jp/~ushijima/maildirdeliver.html . I've been using the code for years - it's quite stable. It does not support maildir++. Tom/Rick/Mike/Ken: Since Tetsu asserts copyright, I think we/you should ask him if we can include maildirdeliver in the vpopmail distribution, and install it just as any other program in ~vpopmail/bin/. If he declines, we could always rip out the relevant parts of the qmail code ourselves and include it as our own version of maildirdeliver. -- Jeremy Kister http://jeremy.kister.net./ !DSPAM:477bbe7e310546079645503!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
On Jan 2, 2008, at 1:29 AM, Matthew Goodman wrote: ---.qmail file for users without any maildrop rules to run--- |/var/vpopmail/bin/vdelivermail /var/vpopmail/domains/%d/%u/Maildir No! You don't want to do this. Reminder to everyone in the world -- vdelivermail should only be in your .qmail-default file. Never anywhere else. I'm not sure I understand why your installation of 5.4.26 isn't working -- if there isn't a .qmail file, the message should just go into the user's maildir. If you absolutely MUST have a .qmail file, it will just contain a single line -- the path to that user's Maildir. Keep in mind that with directory hashing, their maildir might not be in domains/%d/%u/Maildir. You could try using just ./Maildir and see if that works -- I think vdelivermail is already in the user's directory when it's parsing the .qmail file. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ !DSPAM:477bb968310541098019786!
Re: [vchkpw] Upgrade to Vpopmail 5.4.26 and .qmail-default issues
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: vchkpw@inter7.com 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: vchkpw@inter7.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: vchkpw@inter7.com 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: 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 o
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: vchkpw@inter7.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: vchkpw@inter7.com 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: 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:477b598f310548813521591!
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: vchkpw@inter7.com 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: 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:477a9144310547769512702!
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: 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!
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:477a4aba310546407617175!
