1 Topic by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 31,747

Topic: iRedMail Enterprise Edition (EE) v1.8.3 has been released

Dear all,

iRedMail Enterprise Edition (EE) v1.8.3 has been released. All customers are recommended to upgrade.

- Full list of changes: https://docs.iredmail.org/ee.changelog.html
- Upgrade: https://docs.iredmail.org/upgrade.ee.html
- Deploy a new server: https://docs.iredmail.org/install.ee.html
- Features and pricing: https://www.iredmail.org/ee.html

Migration Guides

- Migrate from a server deployed with the downloadable iRedMail installer:
  https://docs.iredmail.org/iredmail.to.ee.html

- Migrate from a server deployed with iRedMail Easy:
  https://docs.iredmail.org/easy.to.ee.html

Best regards,
The iRedMail Team

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by Davesworld (edited by Davesworld Today 12:15:13)

  • Davesworld
  • Member
  • Offline
  • Registered: 2013-04-15
  • Posts: 27

Re: iRedMail Enterprise Edition (EE) v1.8.3 has been released

Since I have both IPv4 and IPv6 working on my server now, I tried sending a test email from my Google account to see if the IPv6 address showed up. Looking at the mail log, it hung. The cause was the full IPv6 address under my networks =  line. After truncating it back to end at :: and reloading Postfix, the IPv6 mail came through. The subnet remains at /64 after the brackets.

Here is an abbreviated example of correct and incorrect:

Incorrect: [fd4d:6169:6c63::5]/64
Correct: [fd4d:6169:6c63::]/64

Shouldn't redeploying Postfix fix this in the future?