Re: [qmailadmin] Aliases/Forwards
- Original Message - From: Jeff Hedlund [EMAIL PROTECTED] New code is going to write to the .qmail- file with the email address either way so that it's more consistent (this does not change behavior in any way-- except that with the current vpopmail code, it will process the 'aliased' users .qmail file properly). This will fix the first major problem as listed in: http://marc.theaimsgroup.com/?l=qmailadminm=105361966010705w=2 I my view creating an alias that by-basses the maildrop's .qmail file has ALWAYS been a bad idea. It only confuses the end user. If you can, it would be nice to include the fallback address in your fix. Many thanks, Gérald PS. This will be the 3rd time someone creates a patch to fix this problem. I hope this time it gets adopted.
Re: [qmailadmin] Aliases/Forwards
Gerald Villemure wrote: This will fix the first major problem as listed in: http://marc.theaimsgroup.com/?l=qmailadminm=105361966010705w=2 I my view creating an alias that by-basses the maildrop's .qmail file has ALWAYS been a bad idea. It only confuses the end user. I agree. In fact, there should be a patch going into vpopmail soon that will cause the users .qmail file to be processed even if a /Maildir/ is specified in an alias file. (but my patch to qmailadmin will start writing it as an e-mail address anyway). If you can, it would be nice to include the fallback address in your fix. My previously mentioned vpopmail patch should also fix this problem, the part of the vpopmail patch that will fix it is here: http://marc.theaimsgroup.com/?l=vchkpwm=105301620128601w=2 (that does not include the part to fix the parsing of .qmail files with a Maildir/, but that will be part of the final patch that will hopefully be admitted into the next release of vpopmail) PS. This will be the 3rd time someone creates a patch to fix this problem. I hope this time it gets adopted. I'm optimistic! :) Jeff
Re: [qmailadmin] Aliases/Forwards
On Saturday, May 31, 2003, at 06:10 AM, Gerald Villemure wrote: PS. This will be the 3rd time someone creates a patch to fix this problem. I hope this time it gets adopted. I've been talking to Jeff directly, and this will be adopted in my next release of qmailadmin. It's been on my to do list, and I have copies of the last two patches that I was going to review/apply to the source when I had time. Updating the UI at the same time is a great idea. -- Tom Collins [EMAIL PROTECTED]
[qmailadmin] interface change?
I just installed 1.0.20 with the help menu's turned on and when I ran it there was no links for the help menus, nor were there the version numbers for qmailadmin and vpopmail. did something change in the install process? I have all my ./configure stuff done in a script for each program and didn't notice any changes for qmailadmin to implement these things. Insight? Thanks; Michael R. Bagnall Powertools Productions, LLC PO Box 325, Lebanon, TN 37088 (615) 453-1141 / (800) 444-1563 [EMAIL PROTECTED] http://www.powertools.net
Re: [qmailadmin] Aliases/Forwards
New code is going to write to the .qmail- file with the email address either way so that it's more consistent (this does not change behavior in any way-- except that with the current vpopmail code, it will process the 'aliased' users .qmail file properly). If I understand you correctly, you are going to make it so that there is no such thing as an alias, not only in the UI, but in the code. This would be a good thing, I think. We currently use only forwards because there are some instances where alias won't work (eg. an alias points to an address that is forwarded). We have some users that get confused with this, and removing the alias would help a lot. Trey Nolen
Re: [qmailadmin] Aliases/Forwards
Trey Nolen wrote: If I understand you correctly, you are going to make it so that there is no such thing as an alias, not only in the UI, but in the code. This would be a good thing, I think. We currently use only forwards because there are some instances where alias won't work (eg. an alias points to an address that is forwarded). We have some users that get confused with this, and removing the alias would help a lot. You understand correctly :) Jeff
Re: [qmailadmin] interface change?
On Saturday, May 31, 2003, at 08:07 AM, Michael R. Bagnall wrote: I just installed 1.0.20 with the help menu's turned on and when I ran it there was no links for the help menus, nor were there the version numbers for qmailadmin and vpopmail. did something change in the install process? I have all my ./configure stuff done in a script for each program and didn't notice any changes for qmailadmin to implement these things. Insight? Did you download an install the help files? http://www.inter7.com/devel/qmailadmin-help-1.0.8.tar.gz I've been contacted by the original author of those files, and he is working on an update for the next production/stable release (hopefully coming soon!). -- Tom Collins [EMAIL PROTECTED]
[qmailadmin] Re: Postmaster catchall doesn't forward
again: that was in my patch, too i've mailed (naged) some inter7 members several times but they never did any thing to get my fixes into qmailadmin :( Tom Collins schrieb: On Saturday, May 31, 2003, at 09:30 AM, Alan Murrell wrote: When I set Postmaster as the default catchall account, and put a forwarding address in it, the mails do not forward; they just stay in the Postmaster's box. Is this a bug that has been fixed in the latest version, or is this just something that isn;t supposed to work? That is a bug that should be fixed in the next (1.0.21) release. See the Aliases/Forwards thread that just started on the mailing list. It's been a long standing problem and we're going to take care of it all around. We'll be patching qmailadmin to use email addresses for the catchall, forwards and aliases instead of using direct Maildir delivery (which bypasses any special rules set up for that address, like forwarding postmaster). The interim solution is to use a remote address catchall to bypass the postmaster mailbox. -- Tom Collins [EMAIL PROTECTED] == Powered by SQWebmail
RE: [qmailadmin] Make error while compiling qmailadmin-1.0.6
I downloaded new files ran ./configure then make. I get the following error: [EMAIL PROTECTED] qmailadmin-1.0.6]# make cd . automake --foreign Makefile configure.in:3: your implementation of AM_INIT_AUTOMAKE comes from an configure.in:3: old Automake version. You should recreate aclocal.m4 configure.in:3: with aclocal and run automake again. make: *** [Makefile.in] Error 1 I then run aclocal and automake then make. This is when I get the QA_PACKAGE error. John Morrow -Original Message- From: Jeff Hedlund [mailto:[EMAIL PROTECTED] Sent: Saturday, May 31, 2003 4:11 AM To: John Morrow Subject: Re: [qmailadmin] Make error while compiling qmailadmin-1.0.6 I haven't tried compiling 1.0.6, but QA_PACKAGE is the variable that holds 'qmailadmin' and QA_VERSION holds the version number (1.0.6 in this case) You didn't run autoconf, did you? ./configure should have taken care of the QA_PACKAGE and QA_VERSION. Jeff
Re: [qmailadmin] Re: Postmaster catchall doesn't forward
On Saturday, May 31, 2003, at 10:43 AM, Thorsten Voss wrote: again: that was in my patch, too i've mailed (naged) some inter7 members several times but they never did any thing to get my fixes into qmailadmin :( Please send a copy of the patch directly to Jeff, as he is doing work directly related to it right now. I promise that it will be in the next release. If anyone else has patches for qmailadmin, and even vpopmail, please send them to me and I'll try to add them to the official release. I am working with sourceforge on establishing projects for qmailadmin and vpopmail. I'll keep you up to date as it progresses. -- Tom Collins [EMAIL PROTECTED]
RE: [qmailadmin] Make error while compiling qmailadmin-1.0.6
That did it. Went through configure, make and make install-strip. Thanks a lot. Now could you please briefly explain to a newbie what the touch command did? John Morrow -Original Message- From: Tom Collins [mailto:[EMAIL PROTECTED] Sent: Saturday, May 31, 2003 12:23 PM To: [EMAIL PROTECTED] Subject: Re: [qmailadmin] Make error while compiling qmailadmin-1.0.6 The automake/autoconf files for qmailadmin have been messed up for some time now. Jeff Hedlund has made some progress on fixing them up, and his changes will be in the upcoming 1.0.21 release (sometime early next week). After downloading qmailadmin 1.0.6, try running `touch *` in the qmailadmin-1.0.6 directory before you do .configure. That might prevent it from running automake. -- Tom Collins [EMAIL PROTECTED]
Re: [qmailadmin] Make error while compiling qmailadmin-1.0.6
On Saturday, May 31, 2003, at 02:24 PM, John Morrow wrote: That did it. Went through configure, make and make install-strip. Thanks a lot. Now could you please briefly explain to a newbie what the touch command did? The touch command sets the modification date/time of a file (or, in this case, all files in the directory) to the current date/time. Autoconf/automake compare timestamps on the various files to determine whether any of them need to be rebuilt (if the file X is used to create file Y, and X is newer than Y, then Y should be rebuilt). I'm still getting up to speed on it myself (like which files create each other file), but have found that the touch trick works great. Fixing the autoconf/automake related files is on the fix list, and Jeff Hedlund has made good progress on it. He was able to fix a lot of the problems, and those changes will be added to the 1.0.21 release. -- Tom Collins [EMAIL PROTECTED]
RE: [qmailadmin] Make error while compiling qmailadmin-1.0.6
-Original Message- From: Tom Collins [mailto:[EMAIL PROTECTED] Sent: Saturday, May 31, 2003 10:09 PM To: [EMAIL PROTECTED] Subject: Re: [qmailadmin] Make error while compiling qmailadmin-1.0.6 The touch command sets the modification date/time of a file (or, in this case, all files in the directory) to the current date/time. Autoconf/automake compare timestamps on the various files to determine whether any of them need to be rebuilt (if the file X is used to create file Y, and X is newer than Y, then Y should be rebuilt). I'm still getting up to speed on it myself (like which files create each other file), but have found that the touch trick works great. Fixing the autoconf/automake related files is on the fix list, and Jeff Hedlund has made good progress on it. He was able to fix a lot of the problems, and those changes will be added to the 1.0.21 release. -- Tom Collins [EMAIL PROTECTED] Thanks it worked great, I was able to get it installed. John Morrow
