I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3.
I read the FAQ about upgrading and it seems pretty straightforward. I backup
up the recommended dir's, downloaded the latest stable release, compiled
with the same options I did when installing the current running version, did
make,
Christian Reeves wrote:
I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3.
I read the FAQ about upgrading and it seems pretty straightforward. I
backup up the recommended dir's, downloaded the latest stable release,
compiled with the same options I did when installing the current
Christian Reeves wrote:
I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3.
I read the FAQ about upgrading and it seems pretty straightforward. I
backup up the recommended dir's, downloaded the latest stable release,
compiled with the same options I did when installing the current
Christian Reeves wrote:
I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3.
I read the FAQ about upgrading and it seems pretty straightforward. I
backup up the recommended dir's, downloaded the latest stable release,
compiled with the same options I did when installing the current
I admin an ISP (relatively small operation but may scale exponentially in
the near future).
I recently moved to a vpop solution for our hosting customers and it's
working great. We use qmail, courier-imap, qmailadmin, and HORDE/IMP for
webmail. All existing domains were moved to the new server
After I used vdeldomain and vadddomain.
I could not login on my qmail with telnet 127.0.0.1:
421 unable to read controls (#4.3.0)
Is it a known bug in vpopmail?
I've seen the same thing happen after using vdeldomain. It changed
permisisons on /var/qmail/control/rcpthosts to 600.
I tried to send a message to a test domain before going full-on with it and
I'm not getting the results I thought I would.
Here is the command I used:
# vpopbull -f file -V blah.com
What I got was an empty e-mail that when you view the source you see the
contents of the file I specified.
So I
I recently moved from a system account based setup to vpopmail for my
primary domain. I'm in the practice of keeping system accounts limited to 8
characters.
Questions:
1 - Since I'm now using vpopmail (no system accounts), are there any
vpopmail gotchas in allowing longer usernames? Granted,
well, make sure if you have mime headers that you have boundaries and
such...
Brilliant! I didn't do it quite that way but now that I understand
what vpopbull wants, it was a complete success.
I would personally use Russell Nelson's qmail-popbull for
such a thing myself...
I'll check it
The lengths are defined in vpopmail.h
#define MAX_PW_NAME 32
#define MAX_PW_DOMAIN 64
By default the max user name is 32 chars (might be 31 with
the trailing null) and max domain name is 64. You can change
those to whatever you want before compiling.
Great, I see the other
2- Is it possible to set a max char. length limit for
vpopmail accounts?
Would this be better implemented/enforced with frontend
scripting to
check the lengh before even calling 'vadduser'?
Change vpopmail.h. The API calls and associated programs will
return an error if the lenghts
11 matches
Mail list logo