On Thu, Aug 14, 2025 at 1:05 PM Russell Clemings via mailop <[email protected]> wrote: > > I run the mail server for a non-profit organization with about 2,300 members. > Since the mid-1990s (10 years before I was involved), the organization has > offered email forwarding to its members. Exactly 1,096 members currently have > forwarding addresses set up. So somebody (probably me) would have to set up > 1,096 mailboxes, set up new ones and disable old ones as members come and go, > and worry about disk space, security, etc. And the organization, already > starved for resources, would have to pay for that work. >
I grant that if you went down a path that required making a thousand mailboxes, that would suck. But, that's only one of multiple optional paths (including getting out of the forwarding business). I'm sympathetic to having to do more work no matter what, but to some degree, such is the way of the universe. Unless you still run telnet instead of ssh and haven't implemented SSL certs for your webserver. I have my own heavy dollop of legacy forwarding addresses myself that I used to manage using /etc/aliases, and I have since moved to deal with it with a very small shell script that rewrites the headers to be DMARC compliant before re-injecting the message, just like a mailing list manager would. I can't even remember when I initially set it up. Maybe 8 years ago? Cheers, Al -- Al Iverson // 312-725-0130 // Chicago http://www.spamresource.com // Deliverability http://www.aliverson.com // All about me https://xnnd.com/calendar // Book my calendar _______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
