https://adminsforum.com/ Thu, 15 Oct 2026 05:22:24 +0000 MyBB https://adminsforum.com/Thread-guide-back-up-aapanel-mail-server-and-verify-the-backup Mon, 12 Oct 2026 01:39:42 +0800 DEV]]> https://adminsforum.com/Thread-guide-back-up-aapanel-mail-server-and-verify-the-backup What this guide does
Create a backup plan for aaPanel Mail Server, run it immediately, and check that an archive was actually produced. This protects mailbox messages before maintenance or migration.

Tested on the AdminsForum lab
aaPanel 8.0.6 on Ubuntu, with Mail Server installed. We saved a weekly plan, ran the task once, and verified the completed archive. We did not restore over existing mailboxes. Screenshots below show the actual lab result.

Before you begin

• Sign in to aaPanel as an administrator and confirm that Mail Server is installed.
  
• Check free disk space. Allow room for the existing mail data, a temporary archive, and retained backups.
  
• Decide how much mail you can afford to lose. A weekly backup can leave up to a week of new messages unprotected; busy mailboxes usually need more frequent backups.
  
• Keep a second copy on another server or storage account. A backup on the same disk cannot protect you from losing that VPS or disk.
  

1. Open the mail backup page
Click Mail Server → Other Settings → Backup. This is the Mail Server backup page, not the website backup page. Look for Backup Plan, Open Backup, the schedule fields and Mail import.

2. Choose the schedule and retention
Turn on Open Backup. For the lab demonstration we selected:

• Period: Weekly.
  
• Day: Monday.
  
• Time: 01:30, using the server's schedule/time settings.
  
• Backup to: Disk of server.
  
• Keep last: 3 copies.
  

Click Save, wait for saving to finish, then return to the page to check the values persisted. Choose your own schedule; these demonstration values are not a recommended minimum for every mailbox.

AdminsForum lab screenshot — saved plan and the generated archive


3. Run a backup now
Open Cron from the left menu. Find [Do not delete] Mail server data backup task. Check its destination, retention and execution cycle. Click Execute in that row, then confirm. This starts a real backup immediately; you do not need to wait until the next scheduled time.

Wait for completion. The word Running in the task list indicates the task is enabled; it is not proof that a backup completed successfully.

4. Read the backup log
Open the task's Log. Look for the source directory, available disk space, compression result, destination filename, and a completion message. Our lab log reported:

Code:Copy

Backup directory: /www/vmail Directory size: 213.22 KB Compressed archive: 13.05 KB Saved under: /www/backup/path/vmail/ Backup is complete

These sizes are examples from a small lab mailbox. Your sizes will differ. A log reporting an error, an empty output file, or only a start time is not a successful backup.

AdminsForum lab screenshot — successful execution log


5. Check and keep an off-server copy
Return to Mail Server → Other Settings → Backup. In our tested version the generated archive appeared under Mail import, with Restore and Delete actions. Check its timestamp and filename against the task log.

Use aaPanel Files to open the exact directory shown in your log. Download the archive to secure storage outside the VPS. Backups contain private email, so do not put them in a public website directory or attach them to a forum post. Check that the downloaded file has a sensible size and can be opened/listed as an archive.

What is covered?
The backup task in this demonstration archived /www/vmail. This is not evidence of a full-server backup. Separately record or back up your mailbox/domain configuration, mail service settings, DNS records, certificates and other required recovery material. Do not assume a mail-data archive alone can recreate every part of a new server.

6. Understand the recovery controls
The page provides Upload from local and Select in server for importing a backup, and a Restore action for the listed archive. Before using them, keep a current backup and test on a separate disposable server. Confirm that the target has compatible Mail Server software and the correct mailbox/domain setup. Importing old mail into live accounts can affect existing data; this guide does not claim a completed restore test.

7. Stop a demonstration schedule
If you only created the schedule for practice, return to the Mail Server backup page, turn off Open Backup and save. Check the corresponding Cron task is paused. Keep the successful archive. On our lab we disabled the temporary plan after testing.

Common problems

• No archive appears: run the correct mail backup task and inspect its log; saving a plan does not immediately create a backup.
  
• Disk full or inode error: free space safely or move verified old backups off-server before trying again.
  
• Backup exists but messages are missing after recovery: check the backup date, mailbox mapping and recovery log. Do not overwrite your only copy while experimenting.
  
• Different time in the UI and log: check server and browser timezone settings; compare the actual file timestamp as well.
  

Verification checklist

• Backup settings persisted after saving.
  
• The correct task executed and its log ended successfully.
  
• A timestamped, non-empty archive exists.
  
• An off-server copy is secured.
  
• A separate recovery rehearsal is planned before relying on the backup.
  

Reference: aaPanel Mail Server documentation. Labels may differ between versions. For help, post your aaPanel version and the relevant error lines in Support & Troubleshooting; remove mailbox contents and credentials first.]]> What this guide does
Create a backup plan for aaPanel Mail Server, run it immediately, and check that an archive was actually produced. This protects mailbox messages before maintenance or migration.

Tested on the AdminsForum lab
aaPanel 8.0.6 on Ubuntu, with Mail Server installed. We saved a weekly plan, ran the task once, and verified the completed archive. We did not restore over existing mailboxes. Screenshots below show the actual lab result.

Before you begin

• Sign in to aaPanel as an administrator and confirm that Mail Server is installed.
  
• Check free disk space. Allow room for the existing mail data, a temporary archive, and retained backups.
  
• Decide how much mail you can afford to lose. A weekly backup can leave up to a week of new messages unprotected; busy mailboxes usually need more frequent backups.
  
• Keep a second copy on another server or storage account. A backup on the same disk cannot protect you from losing that VPS or disk.
  

1. Open the mail backup page
Click Mail Server → Other Settings → Backup. This is the Mail Server backup page, not the website backup page. Look for Backup Plan, Open Backup, the schedule fields and Mail import.

2. Choose the schedule and retention
Turn on Open Backup. For the lab demonstration we selected:

• Period: Weekly.
  
• Day: Monday.
  
• Time: 01:30, using the server's schedule/time settings.
  
• Backup to: Disk of server.
  
• Keep last: 3 copies.
  

Click Save, wait for saving to finish, then return to the page to check the values persisted. Choose your own schedule; these demonstration values are not a recommended minimum for every mailbox.

AdminsForum lab screenshot — saved plan and the generated archive


3. Run a backup now
Open Cron from the left menu. Find [Do not delete] Mail server data backup task. Check its destination, retention and execution cycle. Click Execute in that row, then confirm. This starts a real backup immediately; you do not need to wait until the next scheduled time.

Wait for completion. The word Running in the task list indicates the task is enabled; it is not proof that a backup completed successfully.

4. Read the backup log
Open the task's Log. Look for the source directory, available disk space, compression result, destination filename, and a completion message. Our lab log reported:

Code:Copy

Backup directory: /www/vmail Directory size: 213.22 KB Compressed archive: 13.05 KB Saved under: /www/backup/path/vmail/ Backup is complete

These sizes are examples from a small lab mailbox. Your sizes will differ. A log reporting an error, an empty output file, or only a start time is not a successful backup.

AdminsForum lab screenshot — successful execution log


5. Check and keep an off-server copy
Return to Mail Server → Other Settings → Backup. In our tested version the generated archive appeared under Mail import, with Restore and Delete actions. Check its timestamp and filename against the task log.

Use aaPanel Files to open the exact directory shown in your log. Download the archive to secure storage outside the VPS. Backups contain private email, so do not put them in a public website directory or attach them to a forum post. Check that the downloaded file has a sensible size and can be opened/listed as an archive.

What is covered?
The backup task in this demonstration archived /www/vmail. This is not evidence of a full-server backup. Separately record or back up your mailbox/domain configuration, mail service settings, DNS records, certificates and other required recovery material. Do not assume a mail-data archive alone can recreate every part of a new server.

6. Understand the recovery controls
The page provides Upload from local and Select in server for importing a backup, and a Restore action for the listed archive. Before using them, keep a current backup and test on a separate disposable server. Confirm that the target has compatible Mail Server software and the correct mailbox/domain setup. Importing old mail into live accounts can affect existing data; this guide does not claim a completed restore test.

7. Stop a demonstration schedule
If you only created the schedule for practice, return to the Mail Server backup page, turn off Open Backup and save. Check the corresponding Cron task is paused. Keep the successful archive. On our lab we disabled the temporary plan after testing.

Common problems

• No archive appears: run the correct mail backup task and inspect its log; saving a plan does not immediately create a backup.
  
• Disk full or inode error: free space safely or move verified old backups off-server before trying again.
  
• Backup exists but messages are missing after recovery: check the backup date, mailbox mapping and recovery log. Do not overwrite your only copy while experimenting.
  
• Different time in the UI and log: check server and browser timezone settings; compare the actual file timestamp as well.
  

Verification checklist

• Backup settings persisted after saving.
  
• The correct task executed and its log ended successfully.
  
• A timestamped, non-empty archive exists.
  
• An off-server copy is secured.
  
• A separate recovery rehearsal is planned before relying on the backup.
  

Reference: aaPanel Mail Server documentation. Labels may differ between versions. For help, post your aaPanel version and the relevant error lines in Support & Troubleshooting; remove mailbox contents and credentials first.]]> https://adminsforum.com/Thread-guide-check-mail-logs-and-queue-in-aapanel-free-edition Sun, 11 Oct 2026 20:27:43 +0800 DEV]]> https://adminsforum.com/Thread-guide-check-mail-logs-and-queue-in-aapanel-free-edition A message in Sent confirms client submission, not final delivery. Check the mail service, queue and recipient-specific log entry to find where delivery stopped.

Tested Ubuntu lab: aaPanel Free Edition 8.0.6, Mail Server 7.4.1. Postfix and Dovecot were active, /var/log/mail.log existed, and postqueue -p reported Mail queue is empty. Earlier forwarding tests recorded the original alias and successful local delivery. We did not create a deliberate external rejection for this guide.

1. Record the failing message
Write down the sending account, complete recipient address, send time and timezone, unique subject, and exact client error. Determine whether Send failed immediately or the message appeared in Sent. Use a single controlled test, rather than repeatedly sending the same message.

2. Check service status in aaPanel
Open Mail Server → Other Settings → Common settings and find Service Status. Our screen showed Dovecot, Rspamd and Postfix Running. Postfix handles SMTP transport; Dovecot provides mailbox access and can handle local delivery. A Running label does not establish that every message reached a remote inbox.

The same table contains Stop, Restart, Repair and Config controls. Read the error first. Repeated restarts can interrupt clients without fixing DNS, blocked outbound traffic or recipient rejection.

3. Read the queue on Ubuntu
In an authorized server terminal, run this read-only command:

Code:Copy

postqueue -p

An empty queue means no mail is currently queued in this Postfix instance. It does not prove that every earlier message was delivered: an earlier message could have bounced, been removed or already left the queue.

When entries exist, identify the queue ID, recipient and displayed delay reason. A deferred message is pending for retry. Preserve the reason before changing anything. Do not empty the entire queue to troubleshoot one message.

4. Follow the matching log entry
For our Ubuntu installation:

Code:Copy

tail -n 100 /var/log/mail.log journalctl -u postfix -u dovecot --since '30 minutes ago' --no-pager

The file path was verified in this lab. Other operating systems or logging configurations may use a different location. If a command returns no useful entries, check the logging configuration and time window; do not invent a successful result.

Search for the recipient and queue ID. One message can create several lines. Follow the same ID through submission, delivery attempt and final status. Logs may contain private addresses and message details; remove unrelated information before sharing excerpts publicly.

5. Interpret the delivery result

• status=sent: the selected destination accepted that delivery. For a remote server, read its response; acceptance does not guarantee Inbox placement.
  
• status=deferred: delivery remains pending. Read the accompanying timeout, DNS or temporary rejection reason.
  
• status=bounced: permanent failure was reported. Read the remote explanation and any returned delivery-status message.
  
• Authentication failure: inspect the client username, password and account status before diagnosing remote delivery.
  

Temporary SMTP responses generally begin with 4; permanent negative responses generally begin with 5. Diagnose the full text, not just the number.

6. Fix the cause and retest
For DNS errors, verify MX and its target. For connection timeouts, check provider port restrictions and network reachability. For authentication or reputation failures, verify SPF, DKIM, DMARC and PTR. Change one relevant setting at a time and send another unique test.


External check: our completed SEOStackTools test scored 95/100. It complements logs; it does not report the status of every message.

Continue: Reverse DNS and SEOStackTools delivery testing]]> A message in Sent confirms client submission, not final delivery. Check the mail service, queue and recipient-specific log entry to find where delivery stopped.

Tested Ubuntu lab: aaPanel Free Edition 8.0.6, Mail Server 7.4.1. Postfix and Dovecot were active, /var/log/mail.log existed, and postqueue -p reported Mail queue is empty. Earlier forwarding tests recorded the original alias and successful local delivery. We did not create a deliberate external rejection for this guide.

1. Record the failing message
Write down the sending account, complete recipient address, send time and timezone, unique subject, and exact client error. Determine whether Send failed immediately or the message appeared in Sent. Use a single controlled test, rather than repeatedly sending the same message.

2. Check service status in aaPanel
Open Mail Server → Other Settings → Common settings and find Service Status. Our screen showed Dovecot, Rspamd and Postfix Running. Postfix handles SMTP transport; Dovecot provides mailbox access and can handle local delivery. A Running label does not establish that every message reached a remote inbox.

The same table contains Stop, Restart, Repair and Config controls. Read the error first. Repeated restarts can interrupt clients without fixing DNS, blocked outbound traffic or recipient rejection.

3. Read the queue on Ubuntu
In an authorized server terminal, run this read-only command:

Code:Copy

postqueue -p

An empty queue means no mail is currently queued in this Postfix instance. It does not prove that every earlier message was delivered: an earlier message could have bounced, been removed or already left the queue.

When entries exist, identify the queue ID, recipient and displayed delay reason. A deferred message is pending for retry. Preserve the reason before changing anything. Do not empty the entire queue to troubleshoot one message.

4. Follow the matching log entry
For our Ubuntu installation:

Code:Copy

tail -n 100 /var/log/mail.log journalctl -u postfix -u dovecot --since '30 minutes ago' --no-pager

The file path was verified in this lab. Other operating systems or logging configurations may use a different location. If a command returns no useful entries, check the logging configuration and time window; do not invent a successful result.

Search for the recipient and queue ID. One message can create several lines. Follow the same ID through submission, delivery attempt and final status. Logs may contain private addresses and message details; remove unrelated information before sharing excerpts publicly.

5. Interpret the delivery result

• status=sent: the selected destination accepted that delivery. For a remote server, read its response; acceptance does not guarantee Inbox placement.
  
• status=deferred: delivery remains pending. Read the accompanying timeout, DNS or temporary rejection reason.
  
• status=bounced: permanent failure was reported. Read the remote explanation and any returned delivery-status message.
  
• Authentication failure: inspect the client username, password and account status before diagnosing remote delivery.
  

Temporary SMTP responses generally begin with 4; permanent negative responses generally begin with 5. Diagnose the full text, not just the number.

6. Fix the cause and retest
For DNS errors, verify MX and its target. For connection timeouts, check provider port restrictions and network reachability. For authentication or reputation failures, verify SPF, DKIM, DMARC and PTR. Change one relevant setting at a time and send another unique test.


External check: our completed SEOStackTools test scored 95/100. It complements logs; it does not report the status of every message.

Continue: Reverse DNS and SEOStackTools delivery testing]]> https://adminsforum.com/Thread-guide-configure-imap-and-smtp-for-aapanel-free-edition Sun, 11 Oct 2026 20:26:29 +0800 DEV]]> https://adminsforum.com/Thread-guide-configure-imap-and-smtp-for-aapanel-free-edition Use IMAP for reading email and authenticated SMTP for sending it. Both connections need the full mailbox address and a certificate matching the mail hostname.

Lab verification: mail.adminslab.com presented a trusted matching certificate on IMAP 993 and SMTP STARTTLS 587. Roundcube successfully accessed the mailbox and sent mail. This guide gives manual connection values for an email client; a specific Outlook or Thunderbird desktop installation has not been tested here.

1. Prepare the mailbox and hostname
Complete mail-domain DNS, mailbox creation and mail-service SSL first. Your mail hostname should resolve directly to the mail VPS. For Cloudflare, keep the mail A record DNS only. The webmail website address and aaPanel administration port are different services.

Open Mail Server → Mailboxes. Locate the account and confirm Status is enabled. The Login info column has a Copy link in our tested version. Treat copied login details as private: they can include the mailbox password. Do not paste them into a public support post.

2. Enter incoming IMAP settings
Choose manual configuration in your client and use:

• Protocol: IMAP
  
• Server: your certificate-covered mail hostname, for example mail.example.com
  
• Port: 993
  
• Connection security: SSL/TLS
  
• Username: full mailbox address, for example admin@example.com
  
• Password: that mailbox's password
  

Choose the client's ordinary password authentication over the encrypted connection. Do not use the VPS root password, panel credentials or aaPanel.com account.

3. Enter outgoing SMTP settings

• Server: the same verified mail hostname
  
• Port: 587
  
• Connection security: STARTTLS
  
• Authentication: required, using the mailbox username and password
  

STARTTLS upgrades this SMTP connection to encryption; it is not the same setting as implicit SSL/TLS on port 465. Use 465 only when your own configuration confirms that endpoint is enabled. Port 25 is principally used for server-to-server delivery and is not the recommended authenticated client setting here.

4. Test both directions
Finish setup, open Inbox and compare a known message with webmail. Send a unique-subject test to an address you control. Check Sent and the actual recipient's Inbox and Junk. Reply from the external recipient and verify the response arrives. This last step checks external inbound delivery; that direction still needs a separate real-provider test in our lab.


Reference: our working Roundcube mailbox. This image shows webmail, not desktop-client setup screens.

5. Troubleshoot by symptom

• Certificate mismatch: use the certificate-covered hostname and check mail-service SSL deployment. Do not accept a mismatched certificate as the normal fix.
  
• Connection timeout: verify DNS, the intended port and both VPS/provider firewall rules.
  
• Login rejected: check the full address, mailbox password and enabled Status.
  
• Can read but cannot send: check SMTP authentication and STARTTLS 587 rather than changing IMAP settings.
  
• Message appears in Sent but not at the recipient: inspect delivery logs and the queue.
  

References: aaPanel mail protocol and port documentation · Mail-service SSL guide]]> Use IMAP for reading email and authenticated SMTP for sending it. Both connections need the full mailbox address and a certificate matching the mail hostname.

Lab verification: mail.adminslab.com presented a trusted matching certificate on IMAP 993 and SMTP STARTTLS 587. Roundcube successfully accessed the mailbox and sent mail. This guide gives manual connection values for an email client; a specific Outlook or Thunderbird desktop installation has not been tested here.

1. Prepare the mailbox and hostname
Complete mail-domain DNS, mailbox creation and mail-service SSL first. Your mail hostname should resolve directly to the mail VPS. For Cloudflare, keep the mail A record DNS only. The webmail website address and aaPanel administration port are different services.

Open Mail Server → Mailboxes. Locate the account and confirm Status is enabled. The Login info column has a Copy link in our tested version. Treat copied login details as private: they can include the mailbox password. Do not paste them into a public support post.

2. Enter incoming IMAP settings
Choose manual configuration in your client and use:

• Protocol: IMAP
  
• Server: your certificate-covered mail hostname, for example mail.example.com
  
• Port: 993
  
• Connection security: SSL/TLS
  
• Username: full mailbox address, for example admin@example.com
  
• Password: that mailbox's password
  

Choose the client's ordinary password authentication over the encrypted connection. Do not use the VPS root password, panel credentials or aaPanel.com account.

3. Enter outgoing SMTP settings

• Server: the same verified mail hostname
  
• Port: 587
  
• Connection security: STARTTLS
  
• Authentication: required, using the mailbox username and password
  

STARTTLS upgrades this SMTP connection to encryption; it is not the same setting as implicit SSL/TLS on port 465. Use 465 only when your own configuration confirms that endpoint is enabled. Port 25 is principally used for server-to-server delivery and is not the recommended authenticated client setting here.

4. Test both directions
Finish setup, open Inbox and compare a known message with webmail. Send a unique-subject test to an address you control. Check Sent and the actual recipient's Inbox and Junk. Reply from the external recipient and verify the response arrives. This last step checks external inbound delivery; that direction still needs a separate real-provider test in our lab.


Reference: our working Roundcube mailbox. This image shows webmail, not desktop-client setup screens.

5. Troubleshoot by symptom

• Certificate mismatch: use the certificate-covered hostname and check mail-service SSL deployment. Do not accept a mismatched certificate as the normal fix.
  
• Connection timeout: verify DNS, the intended port and both VPS/provider firewall rules.
  
• Login rejected: check the full address, mailbox password and enabled Status.
  
• Can read but cannot send: check SMTP authentication and STARTTLS 587 rather than changing IMAP settings.
  
• Message appears in Sent but not at the recipient: inspect delivery logs and the queue.
  

References: aaPanel mail protocol and port documentation · Mail-service SSL guide]]> https://adminsforum.com/Thread-guide-change-mailbox-quota-in-aapanel-free-edition Sun, 11 Oct 2026 20:25:23 +0800 DEV]]> https://adminsforum.com/Thread-guide-change-mailbox-quota-in-aapanel-free-edition Mailbox quota limits how much email one account can store. Increase it when more storage is needed, but check server disk space and the domain allowance first.

Tested: aaPanel Free Edition 8.0.6 with Mail Server 7.4.1. We changed admin@adminslab.com from 1 GB to 2 GB, verified the mailbox row, and restored 1 GB afterward. The password and enabled status were unchanged.

1. Check the current allowance
Open Mail Server → Mailboxes. Find the full email address, using Search Email if needed. Read its Quota column: our row changed from 0.00 B/1.00 GB to 0.00 B/2.00 GB. The first number is reported usage; the second is the limit. A rounded zero does not prove that the mailbox contains no messages.

Also inspect Mail Domain for the domain quota and default mailbox size. These are separate settings. Raising one mailbox limit does not create additional disk capacity. Check Home disk usage or run

Code:Copy

df -h /

on Ubuntu. Our lab had 29 GB available during this test.

2. Edit one mailbox
1. In the correct mailbox row, click Edit.
2. Verify the dialog says Edit Mailbox and shows the intended Email Address.
3. Keep Quota limit enabled.
4. Enter the new amount in Quota, then confirm the adjacent unit. We entered 2 with GB selected.
5. Keep the existing Name and User type unless those also need an intentional change.
6. Leave Email Password empty. The dialog explicitly says an empty value leaves the password unchanged.
7. Click Confirm once and wait for the mailbox list to update.

3. Verify the result
Check the same row again. Its allowance should now show the requested value and Status should remain enabled. If the old value remains, reopen Edit and check whether the setting actually saved before trying again. Test normal mailbox access through webmail.


Screenshot: the actual lab row after the successful 2 GB change. The lab was subsequently returned to 1 GB.

4. If the mailbox is already full
Increasing the allowance can help only when the underlying server has space. Review large attachments, Sent, Junk and Trash. Export or back up messages you need before permanent cleanup. Deleting a mailbox is not a quota adjustment: it can remove the account and its mail.

Do not reduce the allowance below current usage as a routine cleanup method. First reduce stored mail or choose a sufficient limit, then verify delivery with a new message.

5. Check quota notifications
Under Mail Server → Other Settings → Common settings, our panel showed Send email when quota exceeded enabled. Check your own setting and test the notification separately; we did not deliberately fill this mailbox or verify an over-quota alert.

Related: Create a user mailbox]]> Mailbox quota limits how much email one account can store. Increase it when more storage is needed, but check server disk space and the domain allowance first.

Tested: aaPanel Free Edition 8.0.6 with Mail Server 7.4.1. We changed admin@adminslab.com from 1 GB to 2 GB, verified the mailbox row, and restored 1 GB afterward. The password and enabled status were unchanged.

1. Check the current allowance
Open Mail Server → Mailboxes. Find the full email address, using Search Email if needed. Read its Quota column: our row changed from 0.00 B/1.00 GB to 0.00 B/2.00 GB. The first number is reported usage; the second is the limit. A rounded zero does not prove that the mailbox contains no messages.

Also inspect Mail Domain for the domain quota and default mailbox size. These are separate settings. Raising one mailbox limit does not create additional disk capacity. Check Home disk usage or run

Code:Copy

df -h /

on Ubuntu. Our lab had 29 GB available during this test.

2. Edit one mailbox
1. In the correct mailbox row, click Edit.
2. Verify the dialog says Edit Mailbox and shows the intended Email Address.
3. Keep Quota limit enabled.
4. Enter the new amount in Quota, then confirm the adjacent unit. We entered 2 with GB selected.
5. Keep the existing Name and User type unless those also need an intentional change.
6. Leave Email Password empty. The dialog explicitly says an empty value leaves the password unchanged.
7. Click Confirm once and wait for the mailbox list to update.

3. Verify the result
Check the same row again. Its allowance should now show the requested value and Status should remain enabled. If the old value remains, reopen Edit and check whether the setting actually saved before trying again. Test normal mailbox access through webmail.


Screenshot: the actual lab row after the successful 2 GB change. The lab was subsequently returned to 1 GB.

4. If the mailbox is already full
Increasing the allowance can help only when the underlying server has space. Review large attachments, Sent, Junk and Trash. Export or back up messages you need before permanent cleanup. Deleting a mailbox is not a quota adjustment: it can remove the account and its mail.

Do not reduce the allowance below current usage as a routine cleanup method. First reduce stored mail or choose a sufficient limit, then verify delivery with a new message.

5. Check quota notifications
Under Mail Server → Other Settings → Common settings, our panel showed Send email when quota exceeded enabled. Check your own setting and test the notification separately; we did not deliberately fill this mailbox or verify an over-quota alert.

Related: Create a user mailbox]]> https://adminsforum.com/Thread-guide-fix-reverse-dns-and-test-email-delivery Sun, 11 Oct 2026 20:17:15 +0800 DEV]]> https://adminsforum.com/Thread-guide-fix-reverse-dns-and-test-email-delivery Reverse DNS identifies your sending server. Verify its PTR record, then send an actual message through your mailbox and review the receiving tool's authentication results.

Verified lab result, 11 October 2026: AlphaVPS configured the PTR for 217.217.235.82 as mail.adminslab.com. Public forward and reverse lookups now match, and Postfix uses that same hostname. A real Roundcube message tested with SEOStackTools Email Tester scored 95/100, Grade A: 12 passed, 2 to improve, 0 errors. SPF, DKIM, DMARC, blacklist and PTR checks passed.

1. Understand forward and reverse DNS
Forward DNS maps mail.example.com to your VPS IP. Reverse DNS maps that IP back to a hostname through a PTR record. The VPS provider controls reverse DNS for its address space. Adding a PTR record in your ordinary Cloudflare domain zone does not update the provider's reverse zone.

Use a stable mail hostname that resolves to the sending IP. Our lab uses mail.adminslab.com for forward DNS, reverse DNS and the SMTP server hostname.

2. Request or set the PTR
Check the VPS provider's Reverse DNS/rDNS/PTR settings. If no control is available, open a technical-support request with the VPS IP and desired full hostname. For example: Please set the PTR for our VPS IP to mail.example.com. Its forward A record already points to that IP.

No root password is needed for a PTR request. After the provider confirms, check public DNS rather than relying only on the ticket's status.

3. Verify both directions
On Ubuntu, these commands query a public resolver:

Code:Copy

host YOUR_VPS_IPV4 1.1.1.1 host mail.example.com 1.1.1.1 postconf myhostname

The first should return the desired hostname; the second should return the sending IP. The last shows Postfix's hostname. In our lab, all three agreed. If an old result remains, allow cached DNS to expire and check again. An NXDOMAIN response means that resolver found no PTR record.

4. Test with SEOStackTools
1. Open SEOStackTools Email Tester.
2. Click Get My Test Address.
3. Copy the unique recipient shown. Each test has its own address; do not copy one from a tutorial image.
4. In your webmail, click Compose and send a normal message from the mailbox you want to test to that address.
5. Return to the tool and click Check My Score.
6. Wait for the report, then review Authentication, Content & Spam Signals, Technical and Email Headers.

Send from the server being tested to the external tester. A same-server local message cannot verify the complete external delivery path.

5. Interpret the measured result
Our report showed SPF Pass, valid DKIM and DMARC alignment Pass. Under Technical, the blacklist check was Clean and Reverse DNS was Found, identifying mail.adminslab.com for the sending IP.

The two suggestions concerned HTML/plain-text structure and a List-Unsubscribe header. This test was an ordinary plain-text mailbox message. Plain-text email is valid; multipart/alternative is useful when sending an HTML version. Unsubscribe headers apply to subscription/marketing mail and relevant bulk-sender requirements, rather than every personal reply. Review suggestions in the context of the message's purpose instead of changing the server simply to increase a score.

6. Diagnose missing messages
Check Postfix logs for the exact recipient and remote response. A queued message is still pending. SMTP 250 acceptance means the receiving server accepted it; it does not guarantee Inbox placement at every provider. PTR, authentication, reputation and content all contribute to delivery.

Current status: PTR verified and external receipt/authentication tested with SEOStackTools. External inbound delivery from another mailbox provider remains a separate test. The old pre-PTR Mail-Tester result was 8.9/10; it is historical and uses a different scoring system from SEOStackTools.

Screenshot: measured SEOStackTools report


Mail tutorial series
Add a Mail Domain in aaPanel Free Edition
Install SSL for aaPanel Mail Server
Configure Mail DNS Records in Cloudflare for aaPanel
Create a User Mailbox in aaPanel Mail Server
Install and Access Webmail in aaPanel Free Edition
Send and Receive Email in aaPanel Free Edition
Create Email Forwarding and Catch-All in aaPanel Free Edition]]> Reverse DNS identifies your sending server. Verify its PTR record, then send an actual message through your mailbox and review the receiving tool's authentication results.

Verified lab result, 11 October 2026: AlphaVPS configured the PTR for 217.217.235.82 as mail.adminslab.com. Public forward and reverse lookups now match, and Postfix uses that same hostname. A real Roundcube message tested with SEOStackTools Email Tester scored 95/100, Grade A: 12 passed, 2 to improve, 0 errors. SPF, DKIM, DMARC, blacklist and PTR checks passed.

1. Understand forward and reverse DNS
Forward DNS maps mail.example.com to your VPS IP. Reverse DNS maps that IP back to a hostname through a PTR record. The VPS provider controls reverse DNS for its address space. Adding a PTR record in your ordinary Cloudflare domain zone does not update the provider's reverse zone.

Use a stable mail hostname that resolves to the sending IP. Our lab uses mail.adminslab.com for forward DNS, reverse DNS and the SMTP server hostname.

2. Request or set the PTR
Check the VPS provider's Reverse DNS/rDNS/PTR settings. If no control is available, open a technical-support request with the VPS IP and desired full hostname. For example: Please set the PTR for our VPS IP to mail.example.com. Its forward A record already points to that IP.

No root password is needed for a PTR request. After the provider confirms, check public DNS rather than relying only on the ticket's status.

3. Verify both directions
On Ubuntu, these commands query a public resolver:

Code:Copy

host YOUR_VPS_IPV4 1.1.1.1 host mail.example.com 1.1.1.1 postconf myhostname

The first should return the desired hostname; the second should return the sending IP. The last shows Postfix's hostname. In our lab, all three agreed. If an old result remains, allow cached DNS to expire and check again. An NXDOMAIN response means that resolver found no PTR record.

4. Test with SEOStackTools
1. Open SEOStackTools Email Tester.
2. Click Get My Test Address.
3. Copy the unique recipient shown. Each test has its own address; do not copy one from a tutorial image.
4. In your webmail, click Compose and send a normal message from the mailbox you want to test to that address.
5. Return to the tool and click Check My Score.
6. Wait for the report, then review Authentication, Content & Spam Signals, Technical and Email Headers.

Send from the server being tested to the external tester. A same-server local message cannot verify the complete external delivery path.

5. Interpret the measured result
Our report showed SPF Pass, valid DKIM and DMARC alignment Pass. Under Technical, the blacklist check was Clean and Reverse DNS was Found, identifying mail.adminslab.com for the sending IP.

The two suggestions concerned HTML/plain-text structure and a List-Unsubscribe header. This test was an ordinary plain-text mailbox message. Plain-text email is valid; multipart/alternative is useful when sending an HTML version. Unsubscribe headers apply to subscription/marketing mail and relevant bulk-sender requirements, rather than every personal reply. Review suggestions in the context of the message's purpose instead of changing the server simply to increase a score.

6. Diagnose missing messages
Check Postfix logs for the exact recipient and remote response. A queued message is still pending. SMTP 250 acceptance means the receiving server accepted it; it does not guarantee Inbox placement at every provider. PTR, authentication, reputation and content all contribute to delivery.

Current status: PTR verified and external receipt/authentication tested with SEOStackTools. External inbound delivery from another mailbox provider remains a separate test. The old pre-PTR Mail-Tester result was 8.9/10; it is historical and uses a different scoring system from SEOStackTools.

Screenshot: measured SEOStackTools report


Mail tutorial series
Add a Mail Domain in aaPanel Free Edition
Install SSL for aaPanel Mail Server
Configure Mail DNS Records in Cloudflare for aaPanel
Create a User Mailbox in aaPanel Mail Server
Install and Access Webmail in aaPanel Free Edition
Send and Receive Email in aaPanel Free Edition
Create Email Forwarding and Catch-All in aaPanel Free Edition]]> https://adminsforum.com/Thread-guide-create-email-forwarding-and-catch-all-in-aapanel-free-edition Sun, 11 Oct 2026 20:16:02 +0800 DEV]]> https://adminsforum.com/Thread-guide-create-email-forwarding-and-catch-all-in-aapanel-free-edition An email forward sends mail for one address to another destination. Catch-all sends mail addressed to otherwise nonexistent users in a domain to a chosen mailbox.

Tested lab: support@adminslab.com forwarded to admin@adminslab.com with catch-all disabled. A separate message to tutorial-catchall-test@adminslab.com reached the same mailbox after catch-all was enabled. These were local delivery tests; forwarding to external providers needs an additional test.

1. Create the receiving mailbox first
Create and enable the destination, for example admin@example.com, and verify that it receives ordinary messages. A forwarding alias does not create a separate mailbox, password or storage allowance. Do not point an alias back to itself or build a circular forwarding chain.

2. Add a forwarding address
1. Open Mail Server → Other Settings.
2. Select Mail forward.
3. Click Add Forward.
4. Keep Status enabled.
5. In Forwarded users, enter the full source address: support@example.com.
6. In Domain, enter example.com.
7. In Receiving user, enter admin@example.com. For multiple destinations, the dialog instructs you to put each on a new line.
8. Click Confirm and wait for Mail forwarding added successfully.

Inspect the saved Address and Goto columns. The source must be the complete address. In our version, entering only support saved an incomplete Address value, so we disabled that test entry and created support@adminslab.com instead. A success notice alone does not validate the intended address.

3. Test forwarding independently
If catch-all is enabled, temporarily turn it off before the alias test. Otherwise it can conceal an incorrect alias by delivering any unknown address anyway. Send a message with a unique subject to the full alias, then refresh the receiving mailbox's Inbox.

Our isolated test reached admin@adminslab.com. Postfix logs recorded support@adminslab.com as the original recipient and the admin mailbox as the delivered recipient.

4. Enable catch-all for the domain
Open Mail Server → Mail Domain. Click the domain row's Catch All switch. In the Catch email dialog, enter an existing destination in Forward email and click Confirm. You can also set the Catch All destination through the domain's Edit dialog.

Check that the switch becomes enabled. In Mail forward, the resulting domain-wide entry appeared as @adminslab.com pointing to admin@adminslab.com in our lab. This is different from a specific support@ alias.

5. Test an unused address
Choose an address that is not a mailbox or alias, such as tutorial-catchall-test@example.com. Send a unique test message and verify it appears at the catch-all destination. Our test did. Existing mailboxes continue to have their own delivery rules; catch-all is intended for otherwise unknown addresses.

Manage and troubleshoot
Catch-all accepts typo addresses and can also collect unwanted mail, so use it when that behavior is useful and watch quota usage. Disable it with the domain switch when no longer needed. For a failed forward, check Status, the full source address, destination existence, loops and server logs. External forwarding may introduce SPF/DMARC complications; test that destination separately before relying on it.

Screenshot: catch-all destination


Prerequisite: Create a user mailbox]]> An email forward sends mail for one address to another destination. Catch-all sends mail addressed to otherwise nonexistent users in a domain to a chosen mailbox.

Tested lab: support@adminslab.com forwarded to admin@adminslab.com with catch-all disabled. A separate message to tutorial-catchall-test@adminslab.com reached the same mailbox after catch-all was enabled. These were local delivery tests; forwarding to external providers needs an additional test.

1. Create the receiving mailbox first
Create and enable the destination, for example admin@example.com, and verify that it receives ordinary messages. A forwarding alias does not create a separate mailbox, password or storage allowance. Do not point an alias back to itself or build a circular forwarding chain.

2. Add a forwarding address
1. Open Mail Server → Other Settings.
2. Select Mail forward.
3. Click Add Forward.
4. Keep Status enabled.
5. In Forwarded users, enter the full source address: support@example.com.
6. In Domain, enter example.com.
7. In Receiving user, enter admin@example.com. For multiple destinations, the dialog instructs you to put each on a new line.
8. Click Confirm and wait for Mail forwarding added successfully.

Inspect the saved Address and Goto columns. The source must be the complete address. In our version, entering only support saved an incomplete Address value, so we disabled that test entry and created support@adminslab.com instead. A success notice alone does not validate the intended address.

3. Test forwarding independently
If catch-all is enabled, temporarily turn it off before the alias test. Otherwise it can conceal an incorrect alias by delivering any unknown address anyway. Send a message with a unique subject to the full alias, then refresh the receiving mailbox's Inbox.

Our isolated test reached admin@adminslab.com. Postfix logs recorded support@adminslab.com as the original recipient and the admin mailbox as the delivered recipient.

4. Enable catch-all for the domain
Open Mail Server → Mail Domain. Click the domain row's Catch All switch. In the Catch email dialog, enter an existing destination in Forward email and click Confirm. You can also set the Catch All destination through the domain's Edit dialog.

Check that the switch becomes enabled. In Mail forward, the resulting domain-wide entry appeared as @adminslab.com pointing to admin@adminslab.com in our lab. This is different from a specific support@ alias.

5. Test an unused address
Choose an address that is not a mailbox or alias, such as tutorial-catchall-test@example.com. Send a unique test message and verify it appears at the catch-all destination. Our test did. Existing mailboxes continue to have their own delivery rules; catch-all is intended for otherwise unknown addresses.

Manage and troubleshoot
Catch-all accepts typo addresses and can also collect unwanted mail, so use it when that behavior is useful and watch quota usage. Disable it with the domain switch when no longer needed. For a failed forward, check Status, the full source address, destination existence, loops and server logs. External forwarding may introduce SPF/DMARC complications; test that destination separately before relying on it.

Screenshot: catch-all destination


Prerequisite: Create a user mailbox]]> https://adminsforum.com/Thread-guide-send-and-receive-email-in-aapanel-free-edition Sun, 11 Oct 2026 20:14:48 +0800 DEV]]> https://adminsforum.com/Thread-guide-send-and-receive-email-in-aapanel-free-edition Test sending and receiving separately. A message in Sent means the client submitted it; it does not prove delivery to an external user's Inbox.

Lab evidence: Roundcube submitted a message from admin@adminslab.com to the same lab mailbox, and it appeared in Inbox. A separate outbound message was accepted by SEOStackTools Email Tester and scored 95/100 (Grade A), with SPF, DKIM, DMARC and PTR passing. External inbound delivery from another provider has not yet been verified in this lab.

1. Check the setup before sending
You need an enabled mailbox, correct MX/A records, running Postfix and Dovecot, trusted mail TLS and working webmail or a configured email client. For external delivery, the provider must allow outbound SMTP traffic. PTR and sender reputation also affect acceptance.

Sign into your HTTPS webmail address with the full mailbox address and mailbox password. Our lab uses webmail.adminslab.com.

2. Compose a simple test
1. Click Compose in Roundcube's left menu.
2. Check From is your mailbox.
3. Enter a recipient address you control in To and press Enter so it becomes a recipient entry.
4. Enter a unique Subject, for example Mail test 01.
5. Enter a short normal message in Message Body.
6. Leave Save sent message in set to Sent.
7. Click Send once and wait for the result.

For an initial local test, send to your own lab mailbox. This checks submission and local storage without depending on another provider. Then repeat with an external address you control.

3. Check Sent and the destination
Open Sent and locate the unique subject. At the receiving account, check Inbox and Spam/Junk. If it arrives, reply from that external account to your aaPanel mailbox. This return message tests external inbound delivery.

In Roundcube, open Inbox and click Refresh. Open the received message and use Reply for a normal conversation test. Record which direction succeeds; avoid calling the whole setup verified when only one direction was tested.

4. Use a desktop client if required
Get your mailbox's connection details from Mail Server → Mailboxes → Login info → Copy. For our verified TLS endpoints, the hostname is mail.adminslab.com, IMAP uses 993 with SSL/TLS, and authenticated SMTP uses 587 with STARTTLS. Use the full mailbox address as username. Confirm these values against your own server configuration rather than copying the lab hostname.

5. Diagnose a missing message

• Send fails immediately: read the exact client error; check authentication, SMTP service and connection settings.
  
• Sent exists but remote delivery fails: inspect Postfix queue/logs for the recipient, status and remote rejection reason. A queued message remains pending.
  
• Incoming mail never arrives: verify public MX, the MX target's A record, inbound port 25, provider firewall and recipient spelling.
  
• Mail reaches Junk: inspect SPF/DKIM/DMARC alignment, PTR, content and reputation. Do not keep resending identical messages rapidly.
  

Next check: use SEOStackTools Email Tester to examine authentication and delivery deductions. Local receipt and an external 250 acceptance are useful evidence, but neither guarantees inbox placement at every provider.

Screenshot: working mailbox


Previous: Install and access webmail]]> Test sending and receiving separately. A message in Sent means the client submitted it; it does not prove delivery to an external user's Inbox.

Lab evidence: Roundcube submitted a message from admin@adminslab.com to the same lab mailbox, and it appeared in Inbox. A separate outbound message was accepted by SEOStackTools Email Tester and scored 95/100 (Grade A), with SPF, DKIM, DMARC and PTR passing. External inbound delivery from another provider has not yet been verified in this lab.

1. Check the setup before sending
You need an enabled mailbox, correct MX/A records, running Postfix and Dovecot, trusted mail TLS and working webmail or a configured email client. For external delivery, the provider must allow outbound SMTP traffic. PTR and sender reputation also affect acceptance.

Sign into your HTTPS webmail address with the full mailbox address and mailbox password. Our lab uses webmail.adminslab.com.

2. Compose a simple test
1. Click Compose in Roundcube's left menu.
2. Check From is your mailbox.
3. Enter a recipient address you control in To and press Enter so it becomes a recipient entry.
4. Enter a unique Subject, for example Mail test 01.
5. Enter a short normal message in Message Body.
6. Leave Save sent message in set to Sent.
7. Click Send once and wait for the result.

For an initial local test, send to your own lab mailbox. This checks submission and local storage without depending on another provider. Then repeat with an external address you control.

3. Check Sent and the destination
Open Sent and locate the unique subject. At the receiving account, check Inbox and Spam/Junk. If it arrives, reply from that external account to your aaPanel mailbox. This return message tests external inbound delivery.

In Roundcube, open Inbox and click Refresh. Open the received message and use Reply for a normal conversation test. Record which direction succeeds; avoid calling the whole setup verified when only one direction was tested.

4. Use a desktop client if required
Get your mailbox's connection details from Mail Server → Mailboxes → Login info → Copy. For our verified TLS endpoints, the hostname is mail.adminslab.com, IMAP uses 993 with SSL/TLS, and authenticated SMTP uses 587 with STARTTLS. Use the full mailbox address as username. Confirm these values against your own server configuration rather than copying the lab hostname.

5. Diagnose a missing message

• Send fails immediately: read the exact client error; check authentication, SMTP service and connection settings.
  
• Sent exists but remote delivery fails: inspect Postfix queue/logs for the recipient, status and remote rejection reason. A queued message remains pending.
  
• Incoming mail never arrives: verify public MX, the MX target's A record, inbound port 25, provider firewall and recipient spelling.
  
• Mail reaches Junk: inspect SPF/DKIM/DMARC alignment, PTR, content and reputation. Do not keep resending identical messages rapidly.
  

Next check: use SEOStackTools Email Tester to examine authentication and delivery deductions. Local receipt and an external 250 acceptance are useful evidence, but neither guarantees inbox placement at every provider.

Screenshot: working mailbox


Previous: Install and access webmail]]> https://adminsforum.com/Thread-guide-install-and-access-webmail-in-aapanel-free-edition Sun, 11 Oct 2026 20:13:38 +0800 DEV]]> https://adminsforum.com/Thread-guide-install-and-access-webmail-in-aapanel-free-edition Webmail lets a mailbox user read and send email in a browser. It is separate from the aaPanel administration dashboard and needs its own website address and HTTPS certificate.

Tested lab: aaPanel Free Edition 8.0.6, Mail Server 7.4.1, Roundcube installed on webmail.adminslab.com using PHP 8.4. The mailbox login worked over HTTPS, and a test message appeared in Inbox.

1. Prepare DNS and a mailbox
Create an A record named webmail pointing to your VPS IPv4 address. Our Cloudflare lab kept this record DNS only for installation and certificate validation. This web address is different from mail.example.com, the SMTP/IMAP hostname. Create an enabled mailbox before testing login.

2. Install through the mail-domain row
1. Open Mail Server → Mail Domain.
2. Find your domain and click Not Installed in the WebMail column.
3. In Install WebMail, enter webmail as the domain prefix. Check the complete address displayed beside the field.
4. Select an installed PHP version compatible with the bundled webmail. We used PHP-84; do not assume the newest PHP version is supported by every bundled application.
5. Click Confirm and wait for WebMail Installation Successful.

The domain row should change to Installed. The success notice directs you to Website → PHP Project, where the new webmail site can be managed. In this tested version, the older Other Settings WebMail controls were disabled and pointed back to Mail Domain. Use the domain-row installer instead.

3. Enable HTTPS on the webmail website
Open Website, find webmail.example.com and select its Not Set SSL button. Select Let's Encrypt → File Verification, check the webmail hostname and click Apply. Its DNS must point to the server, and port 80 must be reachable for this validation method.

Wait for Deployed and verify that the certificate's domain list includes webmail.example.com. Our certificate showed 89 days remaining. Mail-service TLS for mail.example.com does not automatically give this separate webmail website a matching certificate.

4. Sign into Roundcube
Open https://webmail.example.com. Enter the full mailbox address, such as admin@example.com, and that mailbox's password. Click Login. Do not use the VPS root password, panel username or aaPanel.com account.

A successful login displays Inbox, Drafts, Sent, Junk, Trash and Compose. Check the browser's hostname and certificate before entering credentials.

Troubleshooting

• Default website appears: check the webmail DNS record, site domain binding and HTTPS certificate.
  
• Login rejected: check the full email address, mailbox password and enabled Status.
  
• PHP warning or parsererror: our bundled Roundcube emitted an E_STRICT deprecation on PHP 8.4. We turned off public error display for this site's PHP configuration, kept error logging enabled and reloaded its PHP service. This restored inbox requests. Review logged compatibility issues and use a supported release; hiding public warnings is not a substitute for fixing application errors.
  

Result: webmail installed, HTTPS certificate deployed, mailbox login and local message receipt verified.

Screenshot: working Roundcube mailbox

Prerequisite: Create a user mailbox]]> Webmail lets a mailbox user read and send email in a browser. It is separate from the aaPanel administration dashboard and needs its own website address and HTTPS certificate.

Tested lab: aaPanel Free Edition 8.0.6, Mail Server 7.4.1, Roundcube installed on webmail.adminslab.com using PHP 8.4. The mailbox login worked over HTTPS, and a test message appeared in Inbox.

1. Prepare DNS and a mailbox
Create an A record named webmail pointing to your VPS IPv4 address. Our Cloudflare lab kept this record DNS only for installation and certificate validation. This web address is different from mail.example.com, the SMTP/IMAP hostname. Create an enabled mailbox before testing login.

2. Install through the mail-domain row
1. Open Mail Server → Mail Domain.
2. Find your domain and click Not Installed in the WebMail column.
3. In Install WebMail, enter webmail as the domain prefix. Check the complete address displayed beside the field.
4. Select an installed PHP version compatible with the bundled webmail. We used PHP-84; do not assume the newest PHP version is supported by every bundled application.
5. Click Confirm and wait for WebMail Installation Successful.

The domain row should change to Installed. The success notice directs you to Website → PHP Project, where the new webmail site can be managed. In this tested version, the older Other Settings WebMail controls were disabled and pointed back to Mail Domain. Use the domain-row installer instead.

3. Enable HTTPS on the webmail website
Open Website, find webmail.example.com and select its Not Set SSL button. Select Let's Encrypt → File Verification, check the webmail hostname and click Apply. Its DNS must point to the server, and port 80 must be reachable for this validation method.

Wait for Deployed and verify that the certificate's domain list includes webmail.example.com. Our certificate showed 89 days remaining. Mail-service TLS for mail.example.com does not automatically give this separate webmail website a matching certificate.

4. Sign into Roundcube
Open https://webmail.example.com. Enter the full mailbox address, such as admin@example.com, and that mailbox's password. Click Login. Do not use the VPS root password, panel username or aaPanel.com account.

A successful login displays Inbox, Drafts, Sent, Junk, Trash and Compose. Check the browser's hostname and certificate before entering credentials.

Troubleshooting

• Default website appears: check the webmail DNS record, site domain binding and HTTPS certificate.
  
• Login rejected: check the full email address, mailbox password and enabled Status.
  
• PHP warning or parsererror: our bundled Roundcube emitted an E_STRICT deprecation on PHP 8.4. We turned off public error display for this site's PHP configuration, kept error logging enabled and reloaded its PHP service. This restored inbox requests. Review logged compatibility issues and use a supported release; hiding public warnings is not a substitute for fixing application errors.
  

Result: webmail installed, HTTPS certificate deployed, mailbox login and local message receipt verified.

Screenshot: working Roundcube mailbox

Prerequisite: Create a user mailbox]]> https://adminsforum.com/Thread-guide-create-a-user-mailbox-in-aapanel-mail-server Sun, 11 Oct 2026 20:09:25 +0800 DEV]]> https://adminsforum.com/Thread-guide-create-a-user-mailbox-in-aapanel-mail-server A mail domain does not automatically create email users. Create a mailbox with its own password and storage quota before trying to sign into webmail or a mail client.

Tested lab: admin@adminslab.com was created, enabled and assigned a 1 GB quota with the General user type. No password is included in this guide.

1. Complete the domain prerequisites
Install and initialize Mail Server, add your mail domain and publish its mail-host A record and MX record. Configure trusted TLS for the mail hostname before sending credentials from an external client. The mailbox username, panel login and aaPanel.com account are three different accounts.

2. Open Add Mailbox
1. Select Mail Server.
2. Open Mailboxes.
3. Click Add Mailbox.

3. Enter the user's details

• Name: a readable name, such as Lab Admin.
  
• Quota limit: keep enabled when you want a storage cap.
  
• Quota: our lab chose 1 GB. Pick a limit appropriate to the available disk and total domain quota. A mailbox cap is not a backup policy.
  
• User type: our mailbox used General user. Do not grant administrative capabilities unless the person needs them.
  
• Email Address: enter the local part admin and select example.com from the domain selector. The resulting address is admin@example.com. Do not put the entire address into the local-part field.
  
• Email Password: create a unique password for this mailbox and save it securely. Avoid reusing the VPS or panel password.
  
• Status: keep enabled for a mailbox that should be able to log in.
  

Click Confirm. Wait for the success message before submitting again.

4. Verify the new row
The Mailboxes list should show the full address, masked password, quota, type and enabled status. Our row showed 0.00 B/1.00 GB and General user. Masked stars are expected; a screenshot does not need the real password.

The Copy control under Login info provides connection information. Check the actual server name and ports. Use the full address as the login username, the mailbox password, and the mail hostname covered by your certificate. Webmail installation is a separate task.

5. Test access and delivery separately
Successful login proves credentials work; it does not prove external email delivery. Send a message to an external address you control and reply back. Check Inbox, Spam and server logs. Keep an error's exact text if either direction fails.

Troubleshooting

• Domain missing: add it in Mail Domain before creating users.
  
• Invalid login: use the full email address, check Status, and use the mailbox password rather than the panel password.
  
• Quota exceeded: review mailbox and domain usage before raising limits.
  
• Forgotten password: use the mailbox Edit control to reset it and update the user's clients.
  

Screenshot: created and enabled mailbox

Before this step: Add a mail domain · Configure Cloudflare DNS]]> A mail domain does not automatically create email users. Create a mailbox with its own password and storage quota before trying to sign into webmail or a mail client.

Tested lab: admin@adminslab.com was created, enabled and assigned a 1 GB quota with the General user type. No password is included in this guide.

1. Complete the domain prerequisites
Install and initialize Mail Server, add your mail domain and publish its mail-host A record and MX record. Configure trusted TLS for the mail hostname before sending credentials from an external client. The mailbox username, panel login and aaPanel.com account are three different accounts.

2. Open Add Mailbox
1. Select Mail Server.
2. Open Mailboxes.
3. Click Add Mailbox.

3. Enter the user's details

• Name: a readable name, such as Lab Admin.
  
• Quota limit: keep enabled when you want a storage cap.
  
• Quota: our lab chose 1 GB. Pick a limit appropriate to the available disk and total domain quota. A mailbox cap is not a backup policy.
  
• User type: our mailbox used General user. Do not grant administrative capabilities unless the person needs them.
  
• Email Address: enter the local part admin and select example.com from the domain selector. The resulting address is admin@example.com. Do not put the entire address into the local-part field.
  
• Email Password: create a unique password for this mailbox and save it securely. Avoid reusing the VPS or panel password.
  
• Status: keep enabled for a mailbox that should be able to log in.
  

Click Confirm. Wait for the success message before submitting again.

4. Verify the new row
The Mailboxes list should show the full address, masked password, quota, type and enabled status. Our row showed 0.00 B/1.00 GB and General user. Masked stars are expected; a screenshot does not need the real password.

The Copy control under Login info provides connection information. Check the actual server name and ports. Use the full address as the login username, the mailbox password, and the mail hostname covered by your certificate. Webmail installation is a separate task.

5. Test access and delivery separately
Successful login proves credentials work; it does not prove external email delivery. Send a message to an external address you control and reply back. Check Inbox, Spam and server logs. Keep an error's exact text if either direction fails.

Troubleshooting

• Domain missing: add it in Mail Domain before creating users.
  
• Invalid login: use the full email address, check Status, and use the mailbox password rather than the panel password.
  
• Quota exceeded: review mailbox and domain usage before raising limits.
  
• Forgotten password: use the mailbox Edit control to reset it and update the user's clients.
  

Screenshot: created and enabled mailbox

Before this step: Add a mail domain · Configure Cloudflare DNS]]> https://adminsforum.com/Thread-guide-configure-mail-dns-records-in-cloudflare-for-aapanel Sun, 11 Oct 2026 20:07:56 +0800 DEV]]> https://adminsforum.com/Thread-guide-configure-mail-dns-records-in-cloudflare-for-aapanel aaPanel generates your mail-domain record values; Cloudflare publishes them when Cloudflare hosts your domain's authoritative DNS.

Tested: The lab's A, MX, SPF, DKIM and DMARC records were published in Cloudflare. Public DNS lookups returned them, and a real outbound message passed SPF, DKIM and DMARC at Mail-Tester.

1. Get the values from aaPanel
Open Mail Server → Mail Domain → DNS Record for your domain. Keep this screen open. It shows the mail hostname, MX priority, SPF text, unique DKIM public key and DMARC value. You must use your own generated DKIM key.

2. Open Cloudflare DNS
Select your domain in Cloudflare, then DNS → Records. Inspect existing records first. If you already use another mail provider, changing MX and SPF changes that existing setup; plan the migration before replacing records. Our lab had no previous MX record.

3. Add the mail A and MX records
Click Add record. Select type A, name mail, and your VPS IPv4 address. Turn proxy status off so it reads DNS only, then Save.

Add another record: type MX, name @, mail server mail.example.com, priority 10, TTL Auto. The MX target is a hostname, not an IP address or an https:// URL. Save.

4. Add sender-authentication TXT records
Add each separately:

• SPF: type TXT, name @, content copied from aaPanel. Our dedicated lab used
  
  Code:Copy

  v=spf1 +a +mx -all
  This permits the A/MX senders; it is not a universal value for domains using other services. Maintain one SPF policy per name and include all legitimate senders in that policy.
  
• DKIM: type TXT, name default._domainkey in our lab, content copied in full from our domain's aaPanel screen. Your selector may differ. Copy the complete v=DKIM1 value, without the Copy button label. This publishes a public key; the private signing key stays on the server.
  
• DMARC: type TXT, name _dmarc. Our lab used
  
  Code:Copy

  v=DMARC1;p=quarantine;rua=mailto:admin@example.com
  Replace the report mailbox with an address you control. For a domain with existing senders, start by assessing alignment and a monitoring policy before enforcing quarantine/reject.
  

Our SMTP hostname also received a separate TXT SPF record at mail:

Code:Copy

v=spf1 ip4:YOUR_VPS_IPV4 -all

This describes the HELO hostname's permitted sender; it does not replace the root-domain SPF record.

5. Verify public resolution
Check A, MX and each TXT name through a public DNS resolver. Then return to aaPanel and use Already set, Verify domain name resolution. aaPanel can temporarily display a cached Not Set result; check actual public DNS before changing correct records again.

What comes next
Create the mailbox and mail TLS certificate. PTR/reverse DNS belongs to the VPS provider, not this Cloudflare zone. Finally send a real test message: published records alone do not prove SPF/DKIM/DMARC pass on an actual message.

Screenshot: Cloudflare records used by the lab

Prerequisite: Add your mail domain in aaPanel]]> aaPanel generates your mail-domain record values; Cloudflare publishes them when Cloudflare hosts your domain's authoritative DNS.

Tested: The lab's A, MX, SPF, DKIM and DMARC records were published in Cloudflare. Public DNS lookups returned them, and a real outbound message passed SPF, DKIM and DMARC at Mail-Tester.

1. Get the values from aaPanel
Open Mail Server → Mail Domain → DNS Record for your domain. Keep this screen open. It shows the mail hostname, MX priority, SPF text, unique DKIM public key and DMARC value. You must use your own generated DKIM key.

2. Open Cloudflare DNS
Select your domain in Cloudflare, then DNS → Records. Inspect existing records first. If you already use another mail provider, changing MX and SPF changes that existing setup; plan the migration before replacing records. Our lab had no previous MX record.

3. Add the mail A and MX records
Click Add record. Select type A, name mail, and your VPS IPv4 address. Turn proxy status off so it reads DNS only, then Save.

Add another record: type MX, name @, mail server mail.example.com, priority 10, TTL Auto. The MX target is a hostname, not an IP address or an https:// URL. Save.

4. Add sender-authentication TXT records
Add each separately:

• SPF: type TXT, name @, content copied from aaPanel. Our dedicated lab used
  
  Code:Copy

  v=spf1 +a +mx -all
  This permits the A/MX senders; it is not a universal value for domains using other services. Maintain one SPF policy per name and include all legitimate senders in that policy.
  
• DKIM: type TXT, name default._domainkey in our lab, content copied in full from our domain's aaPanel screen. Your selector may differ. Copy the complete v=DKIM1 value, without the Copy button label. This publishes a public key; the private signing key stays on the server.
  
• DMARC: type TXT, name _dmarc. Our lab used
  
  Code:Copy

  v=DMARC1;p=quarantine;rua=mailto:admin@example.com
  Replace the report mailbox with an address you control. For a domain with existing senders, start by assessing alignment and a monitoring policy before enforcing quarantine/reject.
  

Our SMTP hostname also received a separate TXT SPF record at mail:

Code:Copy

v=spf1 ip4:YOUR_VPS_IPV4 -all

This describes the HELO hostname's permitted sender; it does not replace the root-domain SPF record.

5. Verify public resolution
Check A, MX and each TXT name through a public DNS resolver. Then return to aaPanel and use Already set, Verify domain name resolution. aaPanel can temporarily display a cached Not Set result; check actual public DNS before changing correct records again.

What comes next
Create the mailbox and mail TLS certificate. PTR/reverse DNS belongs to the VPS provider, not this Cloudflare zone. Finally send a real test message: published records alone do not prove SPF/DKIM/DMARC pass on an actual message.

Screenshot: Cloudflare records used by the lab

Prerequisite: Add your mail domain in aaPanel]]> https://adminsforum.com/Thread-guide-install-ssl-for-aapanel-mail-server Sun, 11 Oct 2026 20:06:53 +0800 DEV]]> https://adminsforum.com/Thread-guide-install-ssl-for-aapanel-mail-server Mail clients need a trusted certificate covering the server hostname they connect to, such as mail.example.com. A certificate covering only example.com and www.example.com is not sufficient for mail.example.com.

Lab result: A certificate for mail.adminslab.com was issued and deployed to the mail services. IMAP on port 993 and SMTP STARTTLS on port 587 both passed hostname and certificate-chain verification. The web site continued returning HTTP 200.

1. Check DNS and the certificate names
Create the mail hostname A record pointing to your VPS and keep it DNS only on Cloudflare. Check whether you already have a valid certificate that explicitly includes mail.example.com. Do not select the website certificate merely because it belongs to the same parent domain.

2. Issue a hostname certificate
Our lab used an HTTP-01 certificate issued through aaPanel's Website feature:
1. Open Website and click Add site.
2. Enter mail.example.com as the domain.
3. Use a separate directory for this hostname. Do not replace an existing website's files.
4. Leave FTP and database creation disabled for a validation-only site.
5. Keep Apply for SSL selected and submit.
6. Wait until the site appears with a valid certificate and a remaining-days value.

Port 80 must be reachable for HTTP-01 validation. If you cannot use HTTP-01, aaPanel also offers DNS verification under Domains → SSL Certificate → Let's Encrypt. Manual DNS validation requires adding the exact challenge TXT record and needs a renewal plan; aaPanel warns that manually resolved certificates do not support automatic renewal.

3. Deploy the certificate to Mail Server
Open Mail Server → Mail Domain and select the SSL status on the domain row. The dialog offers Other certificate and Apply for SSL.

If an existing matching certificate is offered, inspect its certificate-domain list before selecting Deploy. In our lab that automatic selection initially offered only the root/www certificate, so we did not deploy that mismatched certificate.

For a separately issued mail-host certificate, use Other certificate: paste its matching private key into KEY and its full certificate chain into CRT/PEM, then save. Obtain both from the same certificate entry. Never share the private key or put it in a tutorial screenshot. Our lab deployment was performed through the official mail plugin's certificate method; the encrypted-service checks below confirmed the result.

4. Test the mail endpoints
Configure clients with mail.example.com, not the bare IP. Check IMAP TLS on 993 and SMTP STARTTLS on 587. The certificate should be trusted, unexpired and valid for that exact hostname. A working HTTPS website alone does not verify these mail endpoints.

Renewal and troubleshooting
Monitor expiry and confirm that renewed files are redeployed to Postfix and Dovecot. Issuing a renewed website certificate does not by itself prove the mail-service copy was refreshed. Retest both endpoints after renewal.

A name mismatch means the certificate lacks the hostname used by the client. An incomplete chain means intermediate certificates may be missing. A connection timeout requires checking the service, server firewall and provider firewall. Do not disable certificate verification to conceal an error.

Screenshot: mail-domain SSL status

Start here: Add a Mail Domain in aaPanel Free Edition]]> Mail clients need a trusted certificate covering the server hostname they connect to, such as mail.example.com. A certificate covering only example.com and www.example.com is not sufficient for mail.example.com.

Lab result: A certificate for mail.adminslab.com was issued and deployed to the mail services. IMAP on port 993 and SMTP STARTTLS on port 587 both passed hostname and certificate-chain verification. The web site continued returning HTTP 200.

1. Check DNS and the certificate names
Create the mail hostname A record pointing to your VPS and keep it DNS only on Cloudflare. Check whether you already have a valid certificate that explicitly includes mail.example.com. Do not select the website certificate merely because it belongs to the same parent domain.

2. Issue a hostname certificate
Our lab used an HTTP-01 certificate issued through aaPanel's Website feature:
1. Open Website and click Add site.
2. Enter mail.example.com as the domain.
3. Use a separate directory for this hostname. Do not replace an existing website's files.
4. Leave FTP and database creation disabled for a validation-only site.
5. Keep Apply for SSL selected and submit.
6. Wait until the site appears with a valid certificate and a remaining-days value.

Port 80 must be reachable for HTTP-01 validation. If you cannot use HTTP-01, aaPanel also offers DNS verification under Domains → SSL Certificate → Let's Encrypt. Manual DNS validation requires adding the exact challenge TXT record and needs a renewal plan; aaPanel warns that manually resolved certificates do not support automatic renewal.

3. Deploy the certificate to Mail Server
Open Mail Server → Mail Domain and select the SSL status on the domain row. The dialog offers Other certificate and Apply for SSL.

If an existing matching certificate is offered, inspect its certificate-domain list before selecting Deploy. In our lab that automatic selection initially offered only the root/www certificate, so we did not deploy that mismatched certificate.

For a separately issued mail-host certificate, use Other certificate: paste its matching private key into KEY and its full certificate chain into CRT/PEM, then save. Obtain both from the same certificate entry. Never share the private key or put it in a tutorial screenshot. Our lab deployment was performed through the official mail plugin's certificate method; the encrypted-service checks below confirmed the result.

4. Test the mail endpoints
Configure clients with mail.example.com, not the bare IP. Check IMAP TLS on 993 and SMTP STARTTLS on 587. The certificate should be trusted, unexpired and valid for that exact hostname. A working HTTPS website alone does not verify these mail endpoints.

Renewal and troubleshooting
Monitor expiry and confirm that renewed files are redeployed to Postfix and Dovecot. Issuing a renewed website certificate does not by itself prove the mail-service copy was refreshed. Retest both endpoints after renewal.

A name mismatch means the certificate lacks the hostname used by the client. An incomplete chain means intermediate certificates may be missing. A connection timeout requires checking the service, server firewall and provider firewall. Do not disable certificate verification to conceal an error.

Screenshot: mail-domain SSL status

Start here: Add a Mail Domain in aaPanel Free Edition]]> https://adminsforum.com/Thread-guide-add-a-mail-domain-in-aapanel-free-edition Sun, 11 Oct 2026 20:05:27 +0800 DEV]]> https://adminsforum.com/Thread-guide-add-a-mail-domain-in-aapanel-free-edition Add your email domain to aaPanel Mail Server, then assign the hostname that email clients and receiving servers will use.

Tested lab: Ubuntu 22.04.5, aaPanel Free Edition 8.0.6, Mail Server 7.4.1. We added adminslab.com with the hostname mail.adminslab.com. Replace these examples with your own domain and VPS IP.

1. Prepare the domain and hostname
The mail domain is the part after @ in an address: example.com in admin@example.com. The mail hostname is a server name such as mail.example.com. These are different fields. Install and initialize Mail Server first, and sign into the separate aaPanel.com account if the dashboard requests it.

In your DNS provider, create an A record named mail pointing to the VPS public IPv4 address. On Cloudflare, select DNS only for this mail hostname. Wait until a public DNS lookup returns the correct IP before adding the domain. An orange-cloud proxy does not proxy ordinary SMTP or IMAP connections.

2. Open Add Domain
1. Sign into your VPS aaPanel.
2. Select Mail Server in the left menu.
3. Open Mail Domain.
4. Click Add Domain.
5. Select Manual for DNS records when you will manage the records yourself. Automatic mode requires a configured DNS-provider integration; do not assume it is connected.

3. Fill the fields

• Domain name: example.com, without https://, a path or an email username.
  
• A record: mail.example.com, whose A record points to this VPS.
  
• Domain quota: total storage allowance for the mail domain. Our lab used 5 GB. This is a quota, not disk space reserved automatically.
  
• Mailboxes: permitted mailbox count. Our lab left the default 50; this is not 50 created users.
  
• Catch All: leave blank initially. Create a real destination mailbox before configuring catch-all forwarding.
  

Click Confirm once and wait for the adding-domain message to finish.

4. Verify the result
The domain must appear in the Mail Domain table. Check its spelling, quota and mailbox limit. In our lab the new row showed adminslab.com, a 5 GB quota and a limit of 50. No mailbox is created by this operation.

Click DNS Record on the domain row. aaPanel displays the domain-specific MX, SPF, DKIM and DMARC values. Use that screen for the next DNS lesson. DKIM keys are unique; never copy another site's key.

Troubleshooting

• A record resolution failed: verify the exact hostname, VPS IP, DNS-only setting and public DNS resolution.
  
• Domain exists: inspect the existing row instead of adding it again.
  
• SSL Not Set: configure a certificate covering the mail hostname; adding the domain alone does not complete TLS.
  

Next: Configure the required DNS records, create a mailbox and test encrypted connections. This guide ends at successful domain creation.

Screenshot: completed lab domain

The screenshot shows the later completed setup: SSL and WebMail are separate follow-up steps.]]> Add your email domain to aaPanel Mail Server, then assign the hostname that email clients and receiving servers will use.

Tested lab: Ubuntu 22.04.5, aaPanel Free Edition 8.0.6, Mail Server 7.4.1. We added adminslab.com with the hostname mail.adminslab.com. Replace these examples with your own domain and VPS IP.

1. Prepare the domain and hostname
The mail domain is the part after @ in an address: example.com in admin@example.com. The mail hostname is a server name such as mail.example.com. These are different fields. Install and initialize Mail Server first, and sign into the separate aaPanel.com account if the dashboard requests it.

In your DNS provider, create an A record named mail pointing to the VPS public IPv4 address. On Cloudflare, select DNS only for this mail hostname. Wait until a public DNS lookup returns the correct IP before adding the domain. An orange-cloud proxy does not proxy ordinary SMTP or IMAP connections.

2. Open Add Domain
1. Sign into your VPS aaPanel.
2. Select Mail Server in the left menu.
3. Open Mail Domain.
4. Click Add Domain.
5. Select Manual for DNS records when you will manage the records yourself. Automatic mode requires a configured DNS-provider integration; do not assume it is connected.

3. Fill the fields

• Domain name: example.com, without https://, a path or an email username.
  
• A record: mail.example.com, whose A record points to this VPS.
  
• Domain quota: total storage allowance for the mail domain. Our lab used 5 GB. This is a quota, not disk space reserved automatically.
  
• Mailboxes: permitted mailbox count. Our lab left the default 50; this is not 50 created users.
  
• Catch All: leave blank initially. Create a real destination mailbox before configuring catch-all forwarding.
  

Click Confirm once and wait for the adding-domain message to finish.

4. Verify the result
The domain must appear in the Mail Domain table. Check its spelling, quota and mailbox limit. In our lab the new row showed adminslab.com, a 5 GB quota and a limit of 50. No mailbox is created by this operation.

Click DNS Record on the domain row. aaPanel displays the domain-specific MX, SPF, DKIM and DMARC values. Use that screen for the next DNS lesson. DKIM keys are unique; never copy another site's key.

Troubleshooting

• A record resolution failed: verify the exact hostname, VPS IP, DNS-only setting and public DNS resolution.
  
• Domain exists: inspect the existing row instead of adding it again.
  
• SSL Not Set: configure a certificate covering the mail hostname; adding the domain alone does not complete TLS.
  

Next: Configure the required DNS records, create a mailbox and test encrypted connections. This guide ends at successful domain creation.

Screenshot: completed lab domain

The screenshot shows the later completed setup: SSL and WebMail are separate follow-up steps.]]> https://adminsforum.com/Thread-guide-install-mail-server-in-aapanel-free-edition Sun, 11 Oct 2026 19:28:11 +0800 DEV]]> https://adminsforum.com/Thread-guide-install-mail-server-in-aapanel-free-edition Install the official Mail Server app in aaPanel Free Edition before adding your email domain or creating mailboxes. This lesson covers the installation task and service verification; DNS, certificates and delivery are separate lessons.

Test environment: Ubuntu 22.04.5, aaPanel Free Edition 8.0.6, 2 vCPU, 4 GB RAM and a 40 GB disk. The app offered Mail Server 7.4.1 on 11 October 2026.

1. Check the VPS before installation
Use a test server or take a recoverable backup first. Installing a mail server adds services and uses disk and memory; it is not just an extra button in the panel. Confirm that you have administrator access, free disk space and a domain whose DNS you control. Our lab had roughly 29 GB disk space available and 3 GB memory available before installation.

Check whether another mail server already occupies the SMTP/IMAP ports. Do not stop an existing production mail service merely to make a new installer work. Our initial listener check showed no existing SMTP or IMAP service.

Check outbound TCP port 25 with your provider. Our lab received an SMTP greeting from Google's receiving server, so that one outbound connection worked. This does not prove inbound port 25, recipient acceptance or inbox delivery. Providers can restrict port 25 independently of your local firewall.

2. Find the official Mail Server app
1. Sign in to the aaPanel installed on your VPS.
2. Select App Store in the left menu.
3. Enter Mail in the app search box and press Enter.
4. Find Mail Server with developer official and price Free.
5. Check the supported operating systems in that row. Our Ubuntu 22 server is listed.
6. Click Install on the Mail Server row.

The separate Anti-Spam Gateway search result is a different app. Do not install it instead of Mail Server.

3. Start the installation task
The installation window in our lab displayed Mail Server 7.4.1. Read the version, description and dependency warning before proceeding. If the plugin already exists, the installer warns that its files will be replaced.


Installation window: check the official app and version, then select Install Now.

Click Install Now once. aaPanel opens its Messages Box and adds Install[mail_sys-7.4.1] to the task queue. Open its execution log to follow progress. The app downloads software and installs dependencies, so this can take several minutes.

Do not click Install repeatedly. A Waiting install label or a successful task-queue message means the task was queued; neither is a completed installation. Compilation output also does not mean the queue is frozen.

4. Verify the installed services
Verified result, 11 October 2026: The installed plugin metadata reports Mail Server 7.4.1. Postfix, Dovecot and Rspamd report active. Redis responds but requires authentication. The lab website still responds successfully over HTTPS. No mailbox or external mail delivery is claimed at this stage.

After the task completes, return to the app list and open the Mail Server management screen. Record the actual service state. Check any initialization or missing-dependency messages rather than assuming all mail services are ready because the plugin appears installed. In our lab the new Mail dashboard requires an aaPanel vendor account before its configuration controls become available. The VPS panel login alone does not satisfy that separate account requirement.

5. Sign in to the separate aaPanel account
Open Mail Server from the left menu after the installation finishes. In our tested version, the management screen required an aaPanel.com account. This is different from the username/password used to enter your VPS panel. It is also different from the mailbox account you will create later.

If you already have an aaPanel.com account, use its email address and password in the vendor sign-in window. If you register a new account, use an email address that already receives messages. Do not use an address on the new mail domain before you have configured that domain and created its mailbox. Complete any verification requested by the vendor. Our lab used an existing working email and the account was bound successfully.

6. Initialize the mail-server environment
On the Mail dashboard, follow the environment Install or restore prompt if it appears. The Restoring the mail server environment dialog checks HostName, Postfix, Dovecot, Redis, Rspamd, SQLite support and SELinux. Read every row before pressing Submit.

Our lab initially failed HostName because it was only websrv. A mail hostname should be a full hostname, such as mail.example.com. Choose the name you will later use for the mail DNS A record. Our lab uses mail.adminslab.com. On our Ubuntu 22.04 lab, we set the static hostname over SSH:

Code:Copy

sudo hostnamectl set-hostname --static mail.example.com hostname -f

Replace mail.example.com with your own hostname. This command changes the operating-system hostname; it does not create a DNS record or a PTR record. Existing servers may depend on their hostname, so check those dependencies before changing one.


Environment check: all nine rows are Ready before selecting Submit.

Return to the initialization dialog and click Refresh. All nine checks displayed Ready in our lab. Click Submit once and let the initialization log finish. aaPanel writes the mail-service configuration and starts the environment.

7. Confirm the installation outcome
After initialization, open Mail Domain. The Add Domain button should be available. An empty domain list is expected at this stage: you have installed the mail server, but have not added a mail domain yet.

For an additional service check on our Ubuntu lab, we used:

Code:Copy

systemctl is-active postfix dovecot rspamd

All three returned active. These are installation checks. An active service does not prove that Internet email will arrive or reach an inbox. Domain, DNS, TLS and delivery tests follow in separate lessons.
What installation does not complete
You still need a mail hostname, the domain's MX record, mailbox users, mail certificates and sender-authentication records. Reverse DNS is configured by the VPS provider. A website working over HTTPS does not prove email works.

Troubleshooting

• Still installing: Read the latest execution-log lines. If dependencies are downloading or compiling, let the active task finish.
  
• Download or package error: Record the exact failing URL/package and error. Check connectivity and disk space before retrying.
  
• Port conflict: Identify the service already listening. Preserve an existing mail deployment rather than removing it blindly.
  
• Mail features ask for an aaPanel account: This vendor account is separate from the VPS panel login and the email mailbox. Follow the actual account flow if required.
  

Next lesson: Add adminslab.com to Mail Server and configure mail.adminslab.com. Do not send verification emails to admin@adminslab.com until the mailbox and receiving DNS are ready.]]> Install the official Mail Server app in aaPanel Free Edition before adding your email domain or creating mailboxes. This lesson covers the installation task and service verification; DNS, certificates and delivery are separate lessons.

Test environment: Ubuntu 22.04.5, aaPanel Free Edition 8.0.6, 2 vCPU, 4 GB RAM and a 40 GB disk. The app offered Mail Server 7.4.1 on 11 October 2026.

1. Check the VPS before installation
Use a test server or take a recoverable backup first. Installing a mail server adds services and uses disk and memory; it is not just an extra button in the panel. Confirm that you have administrator access, free disk space and a domain whose DNS you control. Our lab had roughly 29 GB disk space available and 3 GB memory available before installation.

Check whether another mail server already occupies the SMTP/IMAP ports. Do not stop an existing production mail service merely to make a new installer work. Our initial listener check showed no existing SMTP or IMAP service.

Check outbound TCP port 25 with your provider. Our lab received an SMTP greeting from Google's receiving server, so that one outbound connection worked. This does not prove inbound port 25, recipient acceptance or inbox delivery. Providers can restrict port 25 independently of your local firewall.

2. Find the official Mail Server app
1. Sign in to the aaPanel installed on your VPS.
2. Select App Store in the left menu.
3. Enter Mail in the app search box and press Enter.
4. Find Mail Server with developer official and price Free.
5. Check the supported operating systems in that row. Our Ubuntu 22 server is listed.
6. Click Install on the Mail Server row.

The separate Anti-Spam Gateway search result is a different app. Do not install it instead of Mail Server.

3. Start the installation task
The installation window in our lab displayed Mail Server 7.4.1. Read the version, description and dependency warning before proceeding. If the plugin already exists, the installer warns that its files will be replaced.


Installation window: check the official app and version, then select Install Now.

Click Install Now once. aaPanel opens its Messages Box and adds Install[mail_sys-7.4.1] to the task queue. Open its execution log to follow progress. The app downloads software and installs dependencies, so this can take several minutes.

Do not click Install repeatedly. A Waiting install label or a successful task-queue message means the task was queued; neither is a completed installation. Compilation output also does not mean the queue is frozen.

4. Verify the installed services
Verified result, 11 October 2026: The installed plugin metadata reports Mail Server 7.4.1. Postfix, Dovecot and Rspamd report active. Redis responds but requires authentication. The lab website still responds successfully over HTTPS. No mailbox or external mail delivery is claimed at this stage.

After the task completes, return to the app list and open the Mail Server management screen. Record the actual service state. Check any initialization or missing-dependency messages rather than assuming all mail services are ready because the plugin appears installed. In our lab the new Mail dashboard requires an aaPanel vendor account before its configuration controls become available. The VPS panel login alone does not satisfy that separate account requirement.

5. Sign in to the separate aaPanel account
Open Mail Server from the left menu after the installation finishes. In our tested version, the management screen required an aaPanel.com account. This is different from the username/password used to enter your VPS panel. It is also different from the mailbox account you will create later.

If you already have an aaPanel.com account, use its email address and password in the vendor sign-in window. If you register a new account, use an email address that already receives messages. Do not use an address on the new mail domain before you have configured that domain and created its mailbox. Complete any verification requested by the vendor. Our lab used an existing working email and the account was bound successfully.

6. Initialize the mail-server environment
On the Mail dashboard, follow the environment Install or restore prompt if it appears. The Restoring the mail server environment dialog checks HostName, Postfix, Dovecot, Redis, Rspamd, SQLite support and SELinux. Read every row before pressing Submit.

Our lab initially failed HostName because it was only websrv. A mail hostname should be a full hostname, such as mail.example.com. Choose the name you will later use for the mail DNS A record. Our lab uses mail.adminslab.com. On our Ubuntu 22.04 lab, we set the static hostname over SSH:

Code:Copy

sudo hostnamectl set-hostname --static mail.example.com hostname -f

Replace mail.example.com with your own hostname. This command changes the operating-system hostname; it does not create a DNS record or a PTR record. Existing servers may depend on their hostname, so check those dependencies before changing one.


Environment check: all nine rows are Ready before selecting Submit.

Return to the initialization dialog and click Refresh. All nine checks displayed Ready in our lab. Click Submit once and let the initialization log finish. aaPanel writes the mail-service configuration and starts the environment.

7. Confirm the installation outcome
After initialization, open Mail Domain. The Add Domain button should be available. An empty domain list is expected at this stage: you have installed the mail server, but have not added a mail domain yet.

For an additional service check on our Ubuntu lab, we used:

Code:Copy

systemctl is-active postfix dovecot rspamd

All three returned active. These are installation checks. An active service does not prove that Internet email will arrive or reach an inbox. Domain, DNS, TLS and delivery tests follow in separate lessons.
What installation does not complete
You still need a mail hostname, the domain's MX record, mailbox users, mail certificates and sender-authentication records. Reverse DNS is configured by the VPS provider. A website working over HTTPS does not prove email works.

Troubleshooting

• Still installing: Read the latest execution-log lines. If dependencies are downloading or compiling, let the active task finish.
  
• Download or package error: Record the exact failing URL/package and error. Check connectivity and disk space before retrying.
  
• Port conflict: Identify the service already listening. Preserve an existing mail deployment rather than removing it blindly.
  
• Mail features ask for an aaPanel account: This vendor account is separate from the VPS panel login and the email mailbox. Follow the actual account flow if required.
  

Next lesson: Add adminslab.com to Mail Server and configure mail.adminslab.com. Do not send verification emails to admin@adminslab.com until the mailbox and receiving DNS are ready.]]>