Ahh, that explains alot then. I've definitely had the occasional complaint from a user about being over quota, only to find that they were far from it.

I'll shell out the cash and take a look at QControl. Can only make things better, especially considering that the current web-based alternative is broken ;-)

I suppose for the large customer I could do something like that, but that just one more server to maintain and worry about fixing when something goes wrong. I'll do some research and see if there is something out there I'm missing that could accomplish what it is that I'm hoping to accomplish.

What is the quickest/easiest/most efficient way of "freezing" account activity? By this I'm assuming you mean, creating new accounts, changing passwords, etc?

Casey

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>

On 10/6/11 6:03 PM, Eric Shubert wrote:
On 10/06/2011 05:32 PM, Casey wrote:
Where exactly are quotas broken?

If I knew, I might fix it. ;)
I don't know, but sometimes it reports people as being over quota when they're not.

Vqadmin has been handy on the old
server when I'm in a pinch and need to make a quick chance but don't
necessarily have access via SSH. QControl seems like it provides all the
same features plus the stats, which could be somewhat nice.

QControl *is* nice.

Another thing I'm curious about, is how to give some of our customers
access to some of the stats that are displayed through isoqlog. One of
our biggest clients has over 600 accounts and their IT department is
interested in seeing some statistics for their domain. Boy it sure would
be nice if there was some kind of open source piece of software that
combined isoqlog as well as the output from qmailmrtg, so the customers
could get a breakdown of mail usage per domain.

Yes, it would. Or, you could give them their own QMT host (virtual machine). ;)

Also, going back a couple of emails, I'm still a bit confused about the
"--enable-mysql-replication" flag available when recompiling vpopmail.
Can anyone provide a bit more of an explanation of what that does, and
what kind of a situation in which you would want to enable it?

I don't know about that off hand. Should be documented in vpopmail somewhere. Anyone else?

Oh and I changed my workflow a bit on the migration...I was using the
migrate-domains script pretty much as is to backup each mailbox,
aliases, mailing list, etc and finally generate an "import" script. That
method was definitely working, but then I thought to myself - you know
what, this is going to end up causing alot more work for me, because it
just contributes to the problem of having to keep all of the maildirs in
sync. So what I did was modify the script, and commented out the lines
that created the tarballs of each mailbox, as well as the line that
added the extraction portion to the "import" script. So what ends up
happening is that the mailboxes don't get backed up with the version of
the script, but the full import script is still created, and each line
that would extract the individual mailbox archive is commented out, so
the script simply creates the domain & postmaster account, as well as
each individual account, alias, and mailing list, in addition to setting
the parameters such as password, quota, comment, etc. So at least this
will speed up the process of getting everyone added into the system.

That part I follow. Get the accounts migrated at first, and forget the emails for the time being. Keep in mind, you'll want to freeze any account activity from that point on, 'til you're operational on the new host.

Then i can run the original script on the old server to backup the
mailboxes, rsync them over, and use sed to modify each domain's import
script -- uncomment the mailbox extraction line, and batta bing batta
boom...that should do the trick (this all sounded great in my head and
in an email seems alright, so I'm sure in the field there will be some
form of minor hiccup or two)

I'm not sure I follow here, but ok. I don't think you want to process anything account-wise at this stage (counting on a re-add not to mess anything up). Plus, I don't see how rsync is buying you anything at this stage. I think I'd just ssh the tarball(s) over to the new host.

Splitting up the process like this makes sense to me though. Do accounts once, then maildirs as many times as you need to.

Thanks!

Casey

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com <http://www.smileglobal.com>

On 10/6/11 4:49 PM, Eric Shubert wrote:
If you need what vqadmin provides in a gui and you need it to work
right away, I'd go ahead and get QControl. Personally, I don't use
vqadmin at all, because it's broken. I can get by with the CLI for
maintaining domains, and qmailadmin works fine for maintaining users.
(Of course, quotas are still broken, so I just use NOQUOTA for all
accounts). Keep in mind though, I'm not an ISP. I help people host
their own.


Reply via email to