Hello everyone,

I'm happy to have discovered iRedMail and the community surrounding it.  We're a small hosting company located in Florida, USA and have had issues with our upstream email host for several years now.  I'll not mention them here, but message me if you want the details.  Recently they decided to triple our wholesale cost for mail services, which pretty much made it a loss to host email.  I decided to set up a trial version of iRedMail EE on Amazon Web Services and have been very happy with the system so far.  We only have basic features enabled for our clients, but we plan to offer the full SoGo experience in the future as we become more acquainted with iRedMail and how it interfaces with AWS.

We used imapsync to move our client emails over to the new server.  I'll just put the idea out here that it would be really keen if this was built into iRedMail to migrate in new accounts.

So far everyone's been pleased with the performance of their mail hosting and my support staff is very happy with the well-made admin interface.

Great job!

#
# Running Roundcube as a subfolder on an existing virtual host
#
# Block access to default directories and files under these directories

#Tiffany: Delete block rules because in Roundcube 1.7, public_html directory becomes the explicit default.

# Redirect URI `/mail` to `/mail/`.
location = /mail {
    return 301 /mail/;
}

location ~ ^/mail/(.*\.php)$ {
    include /etc/nginx/templates/hsts.tmpl;
    include /etc/nginx/templates/fastcgi_php.tmpl;
    fastcgi_param SCRIPT_FILENAME /opt/www/roundcubemail/public_html/$1;
}

location ~ ^/mail/(.*) {
    alias /opt/www/roundcubemail/public_html/$1;
    index index.php;
}

And yes, Roundcube works fine after that.
3. I did get another domain working that i want to use to access Roundcube and iRedAdmin with following in `/etc/nginx/sites-available/tranz.conf`:

server {
server_name tranzhex.net;
listen [::]:443 ssl http2;
ssl_certificate /opt/cfcerts/tranz.crt;
ssl_certificate_key /opt/cfcerts/tranz.key;
    include /etc/nginx/templates/misc.tmpl;
#    include /etc/nginx/templates/ssl.tmpl;
    include /etc/nginx/templates/iredadmin.tmpl;
    include /etc/nginx/templates/roundcube.tmpl;
    include /etc/nginx/templates/sogo.tmpl;
    include /etc/nginx/templates/netdata.tmpl;
    include /etc/nginx/templates/php-catchall.tmpl;
    include /etc/nginx/templates/stub_status.tmpl;
}

4. In the attached photo, the ipv6 address field is overflown with the iredadmin promo. you might need to reduce the left and right padding on the page.
That's all for my feedback, props to iRedMail developers for making self-hosters life easier, and see you if i ever have any problems

They wanted to be a little more "self-service" but need serious hand-holding and are afraid of using a terminal emulator (or I'd whip up a quick little menu-driven front-end for maillist_admin.py), so I created
a system whereby they can send a limited set of commands by email and get responses back.

I am pleased with the result, and thought I'd share it here.
A copy of the script (with installation instructions in the comments) is attached.
For security, any command but "help" requires that the requester be registered as a moderator,owner,etc. for that list.

Obviously, you shouldn't blindly follow my instructions and install stuff on your server if you can't understand what it's doing.  Certainly this could be abused (esp. since it executes shell commands with little filtering), though I think that the way I've set it up the risk is minimal if you trust your moderators. (If you have ideas for improvement, please feel free to share them with me.)

The Pro version of iRedMail has a great Web UI  for managing mailing lists, including viewing/updating membership.  Even were I using that, though (I'm on the free version), I don't think I want to give these folks that much power to shoot themselves in the foot -- to view/maintain list membership they'd need to be a domain admin and they'd be able to mess w/ email accts and list settings. (I don't think there's granular enough security to let them only do what I want to allow and nothing else.)

I am doing this with the reverse setup of yours -- my main server is "in the cloud" and my relay at home.

In 2019, after running my own from-scratch server at home for 15 years, I installed iRedMail on a hosted VM because I was going to be traveling for a few months and didn't want to chance hardware problems w/ house-sitters.  It's been great! Nice compromise between ease of installation/maintenance and flexibility.

3 years ago, Microsoft kept blacklisting my IP address block at Linode, but unlike many big email providers, they don't mind mail coming from my home address w/ a small-town ISP.  So, I built a VM at home running opensmtpd (no -extras), and any of my mail destined for MS-owned domains gets relayed through that server, while everything else is sent directly from my iRM server.  It's worked well ever since.

Port 25 on WAN must be open, because it's used for communication between email servers.

Hi Zhang, thanks for the prompt answer and glad to see that the server and installation process has much improved in the last 7 years. Keep up the great work.

I'm opening port 2525 and mapping it to port 25 on the server that iRedMail is listening to.
So the transports in PMG is set to homelab.my.domain:2525, that is the CNAME that points to the my local router dynamic IP. Everything that gets to port 2525 is then mapped to port 25 on server mail.home.

In theory, iRedMail is listening to port 25, as if it was in the Internet.

My concern is that if the different host/domain names are going to be an issue, since the packages are sent to homelab.my.domain, but the actual server is mail.home. I´m concerned that this mismatch could somehow impact mail delivery.

I want to move all my mail to be managed in my homelab, instead of the cloud, but since I use broadband, port 25 is blocked and also have a dynamic public IP. Have to PMAP incoming 2525 WAN side to 25 LAN side.

The idea is to have my own Relay in the Internet with a fixed IP that would be a proxy for all the incoming and outgoing emails.

Proxmox Mail Gateway will be the frontend (MX) and iRedMail to be the backend.
I added a DDNS service and mapped the DDNS domain to a CNAME in my DNS. All mail services, except the MTA <> MTA, will be provided only internally (iMAP, POP3...) accessing the iRedMail via VPN services.

In my homelab I have my own local domain and iRedMail have it's own host and domain, that is not the on in the public DNS.

The question is, does the iRedMail host/domain configured in the server must be the same defined in the CNAME record as the relay destination?

2025031101 (Backend: mariadb, Date: 2025-03-18 11:41:40) iRedMail Enterprise Edition: https://www.iredmail.org/easy.html
1.7.2 MARIADB edition.

- Deployed with iRedMail Easy or the downloadable installer?
- Linux/BSD distribution name and version:

Ubuntu 22.04.5 LTS

- Store mail accounts in which backend (LDAP/MySQL/PGSQL):

MySQL

- Web server (Apache or Nginx):

NGINX

- Manage mail accounts with iRedAdmin-Pro?

YES

- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Our agency has used numerous solutions over the years and had been on the lookout for an email system that combined robust features, seamless scalability, and uncompromising security. Enter iRedMail, an exceptional open-source email platform that has truly revolutionized the way we manage and operate email services.

From the moment we deployed iRedMail in 2013, its streamlined setup and intuitive interface stood out as a breath of fresh air. The ease of use, coupled with its comprehensive documentation, ensured a smooth integration into our infrastructure. This simplicity belies its underlying capability to handle demanding loads at scale, making it a powerhouse solution for organizations of any size.

Security is at the forefront of iRedMail’s design, providing a highly secure environment that instills confidence, especially when handling sensitive data across public, private, and critical sectors. The platform offers maximum control over configurations, empowering administrators to tailor the system to their precise needs while maintaining peak performance.

But what truly sets iRedMail apart are its outstanding features, from robust spam filtering to multi-domain hosting. Its versatility and reliability ensure uninterrupted communication, a critical requirement for both day-to-day operations and high-stakes scenarios.

As a tool trusted in diverse sectors, iRedMail has proven itself to be a reliable companion for businesses, non-profits, and governmental institutions alike. Whether it’s the public sector seeking mission-ready email solutions or private entities aiming for operational efficiency, iRedMail consistently exceeds expectations.

In summary, iRedMail is an amazing open-source tool that successfully merges user-friendliness with enterprise-grade functionality. We couldn't be more satisfied with its performance and recommend it wholeheartedly to anyone in need of a robust, secure, and scalable email platform.

Thanks to Huangbin and the iRed team for all they do!

Mailinglist
(inside an interesting link for some literature, famous NY Times articel too)

Congratulations!

Regarding me, by the incredible script of iRedMail I'm using postfix at private mail server since over 14 years and switched over to my new installation right last week... ;-)

(fresh installations at 2009, 2013, 2017...(new world)...2023)