RE: [vchkpw] Per user .qmail patch
Bash scripts are fun! :)
Definitely make it work both ways for a while. Maybe print some
messages to logs or something to alert people they're doing it the wrong
way. I'm sure there are plenty who don't read ChageLog files but do
check logs. Another thing would be to print a big warning message at
the end of a compile. Or maybe force the user to acknowledge the change
by passing a configuration directive to configure. No directive would
yield a message to the user.
Charlie
> -Original Message-
> From: Matt Brookings [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 16, 2005 10:46 PM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] Per user .qmail patch
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Charles J. Boening wrote:
> > cat /var/qmail/users/assign | gawk -F ':' '{ print $5}' | xargs -i
> > find '{}' -mindepth 2 -name .qmail* | xargs -i rename qmail
> vpopmail '{}'
>
> Debate your bash scripts all day ;) The project should still
> allow for both methods for a time to give people who don't
> read the list, or the README, or the ChangeLog, a chance to
> catch up with the change.
>
> - --
> /*
> Matt Brookings <[EMAIL PROTECTED]> GnuPG Key B7B54216
> Software developer Systems technician
> Inter7 Internet Technologies, Inc. (815)776-9465
> */
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.6 (GNU/Linux)
>
> iD8DBQFDo7Q+hzYRRre1QhYRAjGOAJwMkmzMpvPFeh2wgvMHJIrZXq4m9wCfcjtV
> oXCg4mxbTPHbmbYHiyNnjos=
> =32qh
> -END PGP SIGNATURE-
>
Re: [vchkpw] Per user .qmail patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles J. Boening wrote:
> cat /var/qmail/users/assign | gawk -F ':' '{ print $5}' | xargs -i find
> '{}' -mindepth 2 -name .qmail* | xargs -i rename qmail vpopmail '{}'
Debate your bash scripts all day ;) The project should still allow for
both methods for a time to give people who don't read the list, or the
README, or the ChangeLog, a chance to catch up with the change.
- --
/*
Matt Brookings <[EMAIL PROTECTED]> GnuPG Key B7B54216
Software developer Systems technician
Inter7 Internet Technologies, Inc. (815)776-9465
*/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDo7Q+hzYRRre1QhYRAjGOAJwMkmzMpvPFeh2wgvMHJIrZXq4m9wCfcjtV
oXCg4mxbTPHbmbYHiyNnjos=
=32qh
-END PGP SIGNATURE-
RE: [vchkpw] Per user .qmail patch
Ahhh ... Got it. I only have a couple domains so I don't do domain
hashing. :)
Sorry ... I can't resist. Friday and all. Here's another stab.
cat /var/qmail/users/assign | gawk -F ':' '{ print $5}' | xargs -i find
'{}' -mindepth 2 -name .qmail* | xargs -i rename qmail vpopmail '{}'
Starting to look a little convoluted. :)
Charlie
> -Original Message-
> From: Jeremy Kister [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 16, 2005 2:46 PM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] Per user .qmail patch
>
> On 12/16/2005 4:41 PM, Charles J. Boening wrote:
> > Details, details :)
> >
> > I'm sure you could filter those out.
> >
> > find /home/vpopmail/domains -mindepth 3 -name .qmail* | xargs -i
> > rename qmail vpopmail '{}'
>
> now you've broken those with large numbers of domains and
> domain hashing..
>
> # grep example.com /var/qmail/users/assign
> +example.com-:example.com:1010:1010:/home/vpopmail/domains/1/a
> /example.com:-::
>
> or, perl... ;p
>
> http://jeremy.kister.net/code/perl/change-vpopmail-files.pl
>
> --
>
> Jeremy Kister
> http://jeremy.kister.net./
>
>
>
>
>
Re: [vchkpw] Per user .qmail patch
Drew Wells wrote: Yep, it is exactly that. At the moment I have all the files in ~vpopmail/domains// called '.qmail'. I have attached the patch 'as is' that I have been using for a while now, and have also quickly modded the patch in include .vpopmail files (as a secondary to .qmail, please note this is untested) in the users directory. I have also attached a patch which sort of takes care of the Delivered-To: line using either of the 2 above patches. Silly question. What's the advantage of this over .qmail-user-list in the main domain directory ? Rick
RE: [vchkpw] Per user .qmail patch
Yep, it is exactly that. At the moment I have all the files in
~vpopmail/domains// called '.qmail'.
I have attached the patch 'as is' that I have been using for a while now,
and have also quickly modded the patch in include .vpopmail files (as a
secondary to .qmail, please note this is untested) in the users directory.
I have also attached a patch which sort of takes care of the Delivered-To:
line using either of the 2 above patches.
(just deals with .qmail's for now) and will modify it next
week if needed.
On Fri, 16 Dec 2005, Charles J. Boening wrote:
> I thought that was the proposal. To call the files .vpopamil files
> since vdelivermail was actually doing the delivery. You'd still have
> .qmail files in the ~vpopmail/domains/ directory but the
> ~vpopmail/domains// directory would have
> .vpopamail files.
>
> Guess I'll have to go back and read again.
>
>
> Charlie
>
>
>
> > -Original Message-
> > From: Jeremy Kister [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 16, 2005 2:21 PM
> > To: vchkpw@inter7.com
> > Subject: Re: [vchkpw] Per user .qmail patch
> >
> > On 12/16/2005 3:00 PM, Charles J. Boening wrote:
> > > Don't really need a perl script. This should work.
> > >
> > > find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
> > > vpopmail '{}'
> >
> > from your suggestion, I think you're one of the people who
> > are confused. :)
> >
> > renaming all .qmail* files in ~vpopmail/domains will break
> > your installation horribly.
> >
> > --
> >
> > Jeremy Kister
> > http://jeremy.kister.net./
> >
> >
>
diff -uPr vpopmail-5.4.13.orig/vdelivermail.c vpopmail-5.4.13/vdelivermail.c
--- vpopmail-5.4.13.orig/vdelivermail.c 2005-09-02 19:47:29.0 +0100
+++ vpopmail-5.4.13/vdelivermail.c 2005-12-16 15:53:29.0 +
@@ -62,6 +62,7 @@
#ifdef QMAIL_EXT
/* the User with '-' and following chars out if any */
char TheUserExt[AUTH_SIZE];
+char TheExt[AUTH_SIZE];
#endif
#define FILE_SIZE 156
@@ -217,6 +218,11 @@
vexit(EXIT_BOUNCE);
}
+strncpy(TheExt, &TheUser[i+1], AUTH_SIZE);
+for (i = 0; (TheExt[i] != 0); i++) {
+ if (TheExt[i] == '.') TheExt[i] = ':';
+}
+
#endif
vget_assign(TheDomain, TheDomainDir, sizeof(TheDomainDir), &TheDomainUid,
&TheDomainGid);
@@ -697,16 +703,36 @@
chdir(dir);
+#ifdef QMAIL_EXT
/* format the file name */
-if ( (fs = fopen(".qmail","r")) == NULL ) {
+if (strlen(TheExt)) {
+strcpy(tmpbuf,".qmail-");
+strcat(tmpbuf,TheExt);
+if ( (fs = fopen(tmpbuf,"r")) == NULL ) {
+for (i=strlen(TheExt);i>=0;--i) {
+if (!i || TheExt[i-1]=='-') {
+strcpy(tmpbuf,".qmail-");
+strncat(tmpbuf,TheExt,i);
+strcat(tmpbuf,"default");
+if ( (fs = fopen(tmpbuf,"r")) != NULL) {
+break;
+}
+}
+}
+}
+} else {
+fs = fopen(".qmail","r");
+}
+#else
+fs = fopen(".qmail","r");
+#endif
+/* no .qmail file at all */
+if (fs == NULL ) {
/* no file, so just return */
return(-1);
}
-/* format a simple loop checker name */
-snprintf(tmpbuf, sizeof(tmpbuf), "[EMAIL PROTECTED]", TheUser, TheDomain);
-
/* read the file, line by line */
while ( fgets(qmail_line, sizeof(qmail_line), fs ) != NULL ) {
if (*qmail_line == '#') continue;
@@ -716,14 +742,6 @@
if (qmail_line[i] == '\n') qmail_line[i] = 0;
}
-/* simple loop check, if they are sending it to themselves
- * then skip this line
- */
-if ( strcmp( qmail_line, tmpbuf) == 0 ) continue;
-/* check for &[EMAIL PROTECTED] as well */
-if ((*qmail_line == '&') && (strcmp (qmail_line + 1, tmpbuf) == 0))
-continue;
-
deliver_mail(qmail_line, "");
return_value = 1;
diff -uPr vpopmail-5.4.13.orig/vdelivermail.c vpopmail-5.4.13/vdelivermail.c
--- vpopmail-5.4.13.orig/vdelivermail.c 2005-09-02 19:47:29.0 +0100
+++ vpopmail-5.4.13/vdelivermail.c 2005-12-16 21:39:15.0 +
@@ -62,6 +62,7 @@
#ifdef QMAIL_EXT
/* the User with '-' and following chars out if any */
char TheUserExt[AUTH_SIZE];
+char TheExt[AUTH_SIZE];
#endif
#define FILE_SIZE 156
@@ -217,6 +218,11 @@
vexit(EXIT_BOUNCE);
}
+strncpy(TheExt, &TheUser[i+1], AU
Re: [vchkpw] Per user .qmail patch
On 12/16/2005 5:21 PM, Charles J. Boening wrote: > I thought that was the proposal. To call the files .vpopamil files > since vdelivermail was actually doing the delivery. You'd still have > .qmail files in the ~vpopmail/domains/ directory but the > ~vpopmail/domains// directory would have > .vpopamail files. > Guess I'll have to go back and read again. no, that's entirely correct. just that the original posted code didnt leave qmail-local's .qmail-user files inside // alone. -- Jeremy Kister http://jeremy.kister.net./
Re: [vchkpw] Per user .qmail patch
On 12/16/2005 4:41 PM, Charles J. Boening wrote:
> Details, details :)
>
> I'm sure you could filter those out.
>
> find /home/vpopmail/domains -mindepth 3 -name .qmail* | xargs -i rename
> qmail vpopmail '{}'
now you've broken those with large numbers of domains and domain hashing..
# grep example.com /var/qmail/users/assign
+example.com-:example.com:1010:1010:/home/vpopmail/domains/1/a/example.com:-::
or, perl... ;p
http://jeremy.kister.net/code/perl/change-vpopmail-files.pl
--
Jeremy Kister
http://jeremy.kister.net./
RE: [vchkpw] Per user .qmail patch
I thought that was the proposal. To call the files .vpopamil files
since vdelivermail was actually doing the delivery. You'd still have
.qmail files in the ~vpopmail/domains/ directory but the
~vpopmail/domains// directory would have
.vpopamail files.
Guess I'll have to go back and read again.
Charlie
> -Original Message-
> From: Jeremy Kister [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 16, 2005 2:21 PM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] Per user .qmail patch
>
> On 12/16/2005 3:00 PM, Charles J. Boening wrote:
> > Don't really need a perl script. This should work.
> >
> > find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
> > vpopmail '{}'
>
> from your suggestion, I think you're one of the people who
> are confused. :)
>
> renaming all .qmail* files in ~vpopmail/domains will break
> your installation horribly.
>
> --
>
> Jeremy Kister
> http://jeremy.kister.net./
>
>
Re: [vchkpw] Per user .qmail patch
On 12/16/2005 3:00 PM, Charles J. Boening wrote:
> Don't really need a perl script. This should work.
>
> find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
> vpopmail '{}'
from your suggestion, I think you're one of the people who are confused. :)
renaming all .qmail* files in ~vpopmail/domains will break your
installation horribly.
--
Jeremy Kister
http://jeremy.kister.net./
RE: [vchkpw] Per user .qmail patch
Details, details :)
I'm sure you could filter those out.
find /home/vpopmail/domains -mindepth 3 -name .qmail* | xargs -i rename
qmail vpopmail '{}'
:)
Charlie
> -Original Message-
> From: Rick Macdougall [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 16, 2005 12:22 PM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] Per user .qmail patch
>
> Charles J. Boening wrote:
> > Don't really need a perl script. This should work.
> >
> > find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
> > vpopmail '{}'
> >
> >
>
> Except for the small problem of replacing the .qmail files
> for qmail-local in the domain directories :)
>
>
>
Re: [vchkpw] Per user .qmail patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jeremy Kister wrote: > It's hard for some people to understand what qmail-local does and what > vdelivermail does; calling files ".qmail" which are actually handled by > vdelivermail is misleading. If this is a concern, it would make more sense to allow both naming schemes, at least for a few stable versions instead of requiring people to change the naming convention they've become accustomed to immediately. Just my two cents ;) - -- /* Matt Brookings <[EMAIL PROTECTED]> GnuPG Key B7B54216 Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDozMxhzYRRre1QhYRAsYWAJ9eH2GBHykGzSMZavkT1IkTGLE+aACfS1ir c1cstL9Jj0hQBXXHOVmfv70= =UmSx -END PGP SIGNATURE-
Re: [vchkpw] Per user .qmail patch
Charles J. Boening wrote:
Don't really need a perl script. This should work.
find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
vpopmail '{}'
Except for the small problem of replacing the .qmail files for
qmail-local in the domain directories :)
RE: [vchkpw] Per user .qmail patch
Don't really need a perl script. This should work.
find /home/vpopmail/domains -name .qmail* | xargs -i rename qmail
vpopmail '{}'
Charlie
> -Original Message-
> From: Jeremy Kister [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 16, 2005 11:47 AM
> To: vchkpw@inter7.com
> Subject: Re: [vchkpw] Per user .qmail patch
>
> On Fri, 16 Dec 2005 16:03:07 + (GMT), Drew Wells wrote:
> > I have patched VpopMail 5.4.13 so that each user in a
> domain can have > there E-Mail handled by there own set of
> .qmail files (in > /var/vpopmail/domains/{domain}/{user}),
> this is a patch to > 'int check_forward_deliver(char *dir)'
> in vdelivermail.c.
>
> good idea
>
> > Is this patch of any interest to anyone or is this meant
> to be done > another way ?
>
> since we're talking about revamping code, we should change
> the name of the files.
>
> It's hard for some people to understand what qmail-local does
> and what vdelivermail does; calling files ".qmail" which are
> actually handled by vdelivermail is misleading.
>
> As suggested by Charles Cazabon (archived at
> http://msgs.securepoint.com/cgi-bin/get/qmail0510/86/1/1/1/1/1
> .html), we should call these files .vpopmail and/or .vpopmail-user
>
> this will clearly differentiate qmail-local and
> vdelivermail's responsibilities and will natively point
> newbies in the right direction.
>
> both vpopmail and qmailadmin could be updated trivially, and
> a couple of lines of perl could upgrade everyone's
> vpopmail/domains directory tree.
> I'd be happy to write the upgrade script.
>
>
> whether or not we decide to change the name of the files,
> we'll have to
> ask Antonio to update chkusr and checkuser before the release, or at
> least note the possible incompatibility with existing installations.
>
>
> --
>
> Jeremy Kister
> http://jeremy.kister.net./
>
>
Re: [vchkpw] Per user .qmail patch
On Fri, 16 Dec 2005 16:03:07 + (GMT), Drew Wells wrote:
> I have patched VpopMail 5.4.13 so that each user in a domain can have
> there E-Mail handled by there own set of .qmail files (in
> /var/vpopmail/domains/{domain}/{user}), this is a patch to
> 'int check_forward_deliver(char *dir)' in vdelivermail.c.
good idea
> Is this patch of any interest to anyone or is this meant to be done
> another way ?
since we're talking about revamping code, we should change the name of
the files.
It's hard for some people to understand what qmail-local does and what
vdelivermail does; calling files ".qmail" which are actually handled by
vdelivermail is misleading.
As suggested by Charles Cazabon (archived at
http://msgs.securepoint.com/cgi-bin/get/qmail0510/86/1/1/1/1/1.html), we
should call these files .vpopmail and/or .vpopmail-user
this will clearly differentiate qmail-local and vdelivermail's
responsibilities and will natively point newbies in the right direction.
both vpopmail and qmailadmin could be updated trivially, and a couple of
lines of perl could upgrade everyone's vpopmail/domains directory tree.
I'd be happy to write the upgrade script.
whether or not we decide to change the name of the files, we'll have to
ask Antonio to update chkusr and checkuser before the release, or at
least note the possible incompatibility with existing installations.
--
Jeremy Kister
http://jeremy.kister.net./
Re: [vchkpw] Per user .qmail patch
Drew Wells wrote:
Yep, exactly that. I am using '[EMAIL PROTECTED]' and it is
handled by /var/vpopmain/domains/elysium.ltd.uk/drew/.qmail-vpopmail.
I like it, good idea.
DAve
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail source code.
I may be slow, it's been a very long month already and I am taking a
beating this morning. You are saying that if I have an address of
[EMAIL PROTECTED] I may create
/home/vpopmail/pixelhammer.com/dave/.qmail-list
and it will be handled correctly?
DAve
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
I have patched VpopMail 5.4.13 so that each user in a domain can have
there E-Mail handled by there own set of .qmail files (in
/var/vpopmail/domains/{domain}/{user}), this is a patch to
'int check_forward_deliver(char *dir)' in vdelivermail.c.
This means for us when we delete an E-Mail address all the special
delivery rules are also deleted (for that user).
Is this patch of any interest to anyone or is this meant to be done
another way ?
Regards
Call me crazy but I have used .qmail files in the users directory for
two years with vpopmail, up to 5.4.10.
How does your patch differ from vpopmails normal behavior?
DAve
Re: [vchkpw] Per user .qmail patch
Yep, exactly that. I am using '[EMAIL PROTECTED]' and it is
handled by /var/vpopmain/domains/elysium.ltd.uk/drew/.qmail-vpopmail.
On Fri, 16 Dec 2005, DAve wrote:
> Drew Wells wrote:
> > It extends the normal use of .qmail file to .qmail, .qmail-default,
> > .qmail-extension and .qmail-extension-default based on the remaining
> > extension on the incoming E-Mail address in the order as specified in the
> > qmail source code.
>
> I may be slow, it's been a very long month already and I am taking a
> beating this morning. You are saying that if I have an address of
> [EMAIL PROTECTED] I may create
>
> /home/vpopmail/pixelhammer.com/dave/.qmail-list
>
> and it will be handled correctly?
>
> DAve
>
> >
> > On Fri, 16 Dec 2005, DAve wrote:
> >
> >
> >>Drew Wells wrote:
> >>
> >>>I have patched VpopMail 5.4.13 so that each user in a domain can have
> >>>there E-Mail handled by there own set of .qmail files (in
> >>>/var/vpopmail/domains/{domain}/{user}), this is a patch to
> >>>'int check_forward_deliver(char *dir)' in vdelivermail.c.
> >>>This means for us when we delete an E-Mail address all the special
> >>>delivery rules are also deleted (for that user).
> >>>Is this patch of any interest to anyone or is this meant to be done
> >>>another way ?
> >>>
> >>>Regards
> >>
> >>Call me crazy but I have used .qmail files in the users directory for
> >>two years with vpopmail, up to 5.4.10.
> >>
> >>How does your patch differ from vpopmails normal behavior?
> >>
> >>DAve
> >>
> >
> >
> >
> >
>
>
Re: [vchkpw] Per user .qmail patch
Drew Wells wrote:
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail source code.
I may be slow, it's been a very long month already and I am taking a
beating this morning. You are saying that if I have an address of
[EMAIL PROTECTED] I may create
/home/vpopmail/pixelhammer.com/dave/.qmail-list
and it will be handled correctly?
DAve
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
I have patched VpopMail 5.4.13 so that each user in a domain can have
there E-Mail handled by there own set of .qmail files (in
/var/vpopmail/domains/{domain}/{user}), this is a patch to
'int check_forward_deliver(char *dir)' in vdelivermail.c.
This means for us when we delete an E-Mail address all the special
delivery rules are also deleted (for that user).
Is this patch of any interest to anyone or is this meant to be done
another way ?
Regards
Call me crazy but I have used .qmail files in the users directory for
two years with vpopmail, up to 5.4.10.
How does your patch differ from vpopmails normal behavior?
DAve
Re: [vchkpw] Per user .qmail patch
Yes, it does - I think there may be a slight issue with 'Delivered-To:',
but not sure what to do about it.
On Fri, 16 Dec 2005, Ken Jones wrote:
> That sounds like a pretty good patch to me.
>
> So it completes the vpopmail .qmail file processing
> functionality to match what qmail-local supports
> including . to : character handling?
>
> Ken Jones
>
> Drew Wells wrote:
> > It extends the normal use of .qmail file to .qmail, .qmail-default,
> > .qmail-extension and .qmail-extension-default based on the remaining
> > extension on the incoming E-Mail address in the order as specified in the
> > qmail source code.
> >
> > On Fri, 16 Dec 2005, DAve wrote:
> >
> >
> >>Drew Wells wrote:
> >>
> >>>I have patched VpopMail 5.4.13 so that each user in a domain can have
> >>>there E-Mail handled by there own set of .qmail files (in
> >>>/var/vpopmail/domains/{domain}/{user}), this is a patch to
> >>>'int check_forward_deliver(char *dir)' in vdelivermail.c.
> >>>This means for us when we delete an E-Mail address all the special
> >>>delivery rules are also deleted (for that user).
> >>>Is this patch of any interest to anyone or is this meant to be done
> >>>another way ?
> >>>
> >>>Regards
> >>
> >>Call me crazy but I have used .qmail files in the users directory for
> >>two years with vpopmail, up to 5.4.10.
> >>
> >>How does your patch differ from vpopmails normal behavior?
> >>
> >>DAve
> >>
> >
> >
>
>
Re: [vchkpw] Per user .qmail patch
That sounds like a pretty good patch to me.
So it completes the vpopmail .qmail file processing
functionality to match what qmail-local supports
including . to : character handling?
Ken Jones
Drew Wells wrote:
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail source code.
On Fri, 16 Dec 2005, DAve wrote:
Drew Wells wrote:
I have patched VpopMail 5.4.13 so that each user in a domain can have
there E-Mail handled by there own set of .qmail files (in
/var/vpopmail/domains/{domain}/{user}), this is a patch to
'int check_forward_deliver(char *dir)' in vdelivermail.c.
This means for us when we delete an E-Mail address all the special
delivery rules are also deleted (for that user).
Is this patch of any interest to anyone or is this meant to be done
another way ?
Regards
Call me crazy but I have used .qmail files in the users directory for
two years with vpopmail, up to 5.4.10.
How does your patch differ from vpopmails normal behavior?
DAve
Re: [vchkpw] Per user .qmail patch
It extends the normal use of .qmail file to .qmail, .qmail-default,
.qmail-extension and .qmail-extension-default based on the remaining
extension on the incoming E-Mail address in the order as specified in the
qmail source code.
On Fri, 16 Dec 2005, DAve wrote:
> Drew Wells wrote:
> > I have patched VpopMail 5.4.13 so that each user in a domain can have
> > there E-Mail handled by there own set of .qmail files (in
> > /var/vpopmail/domains/{domain}/{user}), this is a patch to
> > 'int check_forward_deliver(char *dir)' in vdelivermail.c.
> > This means for us when we delete an E-Mail address all the special
> > delivery rules are also deleted (for that user).
> > Is this patch of any interest to anyone or is this meant to be done
> > another way ?
> >
> > Regards
>
> Call me crazy but I have used .qmail files in the users directory for
> two years with vpopmail, up to 5.4.10.
>
> How does your patch differ from vpopmails normal behavior?
>
> DAve
>
Re: [vchkpw] Per user .qmail patch
Drew Wells wrote:
I have patched VpopMail 5.4.13 so that each user in a domain can have
there E-Mail handled by there own set of .qmail files (in
/var/vpopmail/domains/{domain}/{user}), this is a patch to
'int check_forward_deliver(char *dir)' in vdelivermail.c.
This means for us when we delete an E-Mail address all the special
delivery rules are also deleted (for that user).
Is this patch of any interest to anyone or is this meant to be done
another way ?
Regards
Call me crazy but I have used .qmail files in the users directory for
two years with vpopmail, up to 5.4.10.
How does your patch differ from vpopmails normal behavior?
DAve
