Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi,
I'm not that hero in C. But let's try. So, if we want to log all
addresses using the qmail-ext feature, it is done in (vpopmail 5.2.1)
the main function, line 137 (if ((vpw=vauth_getpw(TheUserExt,
TheDomain)) != NULL ) {), right?
The VALIAS is not used (it is not defined in config.h), so that should
be the only place where the address is checked, is that also right?
Kind regards,
Harm van Tilborg
Tom Collins wrote:
On Jul 27, 2006, at 10:51 AM, Harm van Tilborg wrote:
If users have only access to qmailadmin (maybe not really vpopmail
related, but ok), are they able to use qmail-ext addresses? Or do they
really have to know how qmail deals with the 'ext' addresses?
With qmail-ext enabled, users can put -anything after their email
address and still get the message. They'd have to know about that
feature, and chances are they aren't making use of it.
If you're unsure, you could modify vdelivermail to log any qmail-ext
addresses that it matches. If nothing comes through in a few weeks, you
can probably safely disable that feature.
--
Tom Collins - [EMAIL PROTECTED]
Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/
QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
On Jul 27, 2006, at 10:51 AM, Harm van Tilborg wrote: If users have only access to qmailadmin (maybe not really vpopmail related, but ok), are they able to use qmail-ext addresses? Or do they really have to know how qmail deals with the 'ext' addresses? With qmail-ext enabled, users can put -anything after their email address and still get the message. They'd have to know about that feature, and chances are they aren't making use of it. If you're unsure, you could modify vdelivermail to log any qmail-ext addresses that it matches. If nothing comes through in a few weeks, you can probably safely disable that feature. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi, Thanks for the quick response. If users have only access to qmailadmin (maybe not really vpopmail related, but ok), are they able to use qmail-ext addresses? Or do they really have to know how qmail deals with the 'ext' addresses? Kind regards, Harm van Tilborg Tom Collins wrote: On Jul 27, 2006, at 8:12 AM, Harm van Tilborg wrote: 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? I think so, but I haven't done an upgrade from 5.2.1 in a long time. 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? If you have users relying on it to get their email, then it will be a problem. Some of my users make use of it to generate unique email addresses (like tom-amazon for all email from amazon.com) that they can later turn into blackhole or bounce addresses. 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? Domain quotas are definitely broken, and have been disabled in the current release. 4) Will this upgrade change anything to the already set (but not working) quotas? I don't know -- I don't personally use quotas. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
On Jul 27, 2006, at 8:12 AM, Harm van Tilborg wrote: 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? I think so, but I haven't done an upgrade from 5.2.1 in a long time. 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? If you have users relying on it to get their email, then it will be a problem. Some of my users make use of it to generate unique email addresses (like tom-amazon for all email from amazon.com) that they can later turn into blackhole or bounce addresses. 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? Domain quotas are definitely broken, and have been disabled in the current release. 4) Will this upgrade change anything to the already set (but not working) quotas? I don't know -- I don't personally use quotas. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
[vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi all, I'm dubbing with four questions. 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? 4) Will this upgrade change anything to the already set (but not working) quotas? Kind regards, Harm van Tilborg PS: keep up the great work!
