1)

The latter one. With iRedAdmin-Pro, you can set a quota for domain, and domain admin is free to balance the mailbox quota for different users, but not exceed the domain quota.

Curious why you want to prevent quota change by domain admin for one account? if you don't mind sharing.

2)

Sure. Login to iRedAdmin-Pro as global admin, go to domain profile page.

3)

It's easy, create a new config file under /etc/nginx/sites-available/ for your web domain "example.com" like this:

server {
    listen 80;
    server_name example.com;
    return 301 https://$host$request_uri;
}

server {
    listen 443;
    server_name example.com;

    root /var/www/html;
    index index.php index.html;

    include /etc/nginx/templates/misc.tmpl;
    include /etc/nginx/templates/ssl.tmpl;
    include /etc/nginx/templates/roundcube-subdomain.tmpl;
    include /etc/nginx/templates/iredadmin-subdomain.tmpl;
}

Don't forget to link this file to /etc/nginx/sites-enabled/, otherwise it's not loaded by Nginx.

4)

Depends on how you upgrade Roundcube. If you follow section "On the command line", and upgrade with command "bin/installto.sh", it will upgrade the SQL database. Note: this requires you have old Roundcube directory and database on new server.

Another way is, import the SQL files under "SQL/mysql/<xxx>.sql" manually. You can query SQL table "roundcubemail.system" on OLD server to know the version (of SQL structure) it runs, then find newer SQL files under "SQL/mysql/" and import them manually (the sql file names contains year, month, day, you won't miss it).

Can I assume that I do not need to import the old "amavisd" database to the new server? It just looks like stuff that is related to the processing and tracking of mail on the old server, and on the new server it will be repopulated automatically with data related to the new server.

OK, so I imported the various databases from my old server to the new server, but the initial domain set up during the installation of iRedMail (and iRedAdmin-Pro) on the new server is, of course, missing, because it did not exist on the old server. The mail spool for the domain exists in the file system, of course.

I presume this can be fixed by simply importing certain records from the original databases. I have a back-up copy of the "vmail" database, which seems to be the only database with relevant data; should I just import the records in that?

Thanks.

Craig

An unfortunate side effect of this is that I cannot view the email with all of the information about the new iRedMail installation. I was looking all over for it (as I hadn't saved it somewhere else separately yet) then realised where it is. It's still on the server, just inaccessible in the normal way until I figure out how to put the domain back into or reattach it to the iRedAdmin system.

While you reduce the "max quota of mail user", it's too risky to reduce quota of existing mail user, if someone's mailbox is larger than 2GB, further inbound mails will be rejected by Dovecot due to quota exceeded.

In early iRedAdmin-Pro release, it's a global setting, but that is not good for a hosting service, different domain may need different default quota, so we made it a per-domain setting.

Yes if you want to change it, just update vmail.domain.settings column.

Yes. Another ways:

- Update quota through iRedAdmin-Pro RESTful API: https://docs.iredmail.org/iredadmin-pro … l.api.html
- Run script shipped in iRedAdmin-Pro: tools/update_mailbox_quota.py.

It's sorted by domain name, alphabetized.

Could you help capture some screenshots (with comment text in picture) to help me understand this issue?

OK, thanks. I will experiment.

Makes sense, but I want to set a baseline default quota (which is more than it was on the old server), and then possibly change it on individual domains later.

Perfect, thanks.

I have attached screenshots of both the old and new servers, with the same list of domains. As you can see, on the old server the list starts at A and only reaches C on the first page. On the new server there is one domain starting with a J at the top of the list, then the list goes to a domain starting with "ac" (when you can see on the list on the old server that there are domains starting with "ab") and it goes to Z on the first page. Many domains have been skipped. On the second page the list again goes from A all the way to Z; different domains, but again many skipped.

If you want I will give you access to the development server so you can see for yourself.

Yes, that makes sense, except the SQL dumped from the old server included "DROP TABLE IF EXISTS" SQL instructions, so the original domain was lost when the "vmail" database was imported. But it's just a development server so on the production server I will make sure it is not lost when I import the SQL.

Thanks for your help. Hopefully that is all I need to move forward, but I hope the sorting issue can be fixed, or the cause of the problem found.

Thanks Zhang. That works with the default sort order (loading the page when I click "Domains and Accounts" or when I click a letter), but there are still some domains listed out of order if I then click on the "Domain" heading. The domains listed out of order seem to be domains with aliases, and a domain with one alias is sorted before a domain with two aliases before a domain with three aliases before domains with no aliases, etc. If you look at my screenshot of the new server you'll see that the first domain has a black smudge to the right of the domain name. It's in the blurred out area, but that black smudge is a big "A1", indicating that the first domain ("je*****") has one alias. That is still happening when I manually sort on the domain column.

Otherwise it's working well enough for me at the moment.

You can remove this "settings.pyc" file, it will be re-generated automatically.
But the point is, does the changed parameter work now?

You can see the webmaster address if you login to iRedAdmin-Pro as a normal domain admin instead of global admin, at the footer of page.

Odd question: For various reasons I have gone against the advice in iRedAdmin-Pro and created domain admins on the default domain of my mail server rather than marking existing users under individual domains as admins. (One reason is that if I set up a domain and the domain owner wants to set up email addresses himself, there is no user on the domain for me to make the domain admin.) However, those admins can still mark themselves as domain admins once they have logged in as the admin user I create, and log into iRedAdmin-Pro using their own email address from that point on.

For example, my domain admins all look like name@mail43.example.com, mail43.example.com being the primary domain on my *old* server.

If I want to make all of those existing users look like name@mail.example.com (without the number 43 in the sub-domain), is it just a matter of just changing all of those user names somewhere in the vmail database?

Thanks.