On Mon, Sep 7, 2026, at 13:35, Kevin Fenzi wrote: > So, we could setup an smtp gateway service, but I'd really prefer not > to. :) > > Say we setup a endpoint that allowed 'fedora contributors' to auth and > relay email out: > > - I don't think very many people will use it. There's a small number of > folks on this list who might, but I suspect the number would be pretty > small. Most folks think of this for incoming emails/to allow folks to > email them, not sending... > > - Just one spammer or contributor thats compromised to send spam would > result in all our emails getting blocked by major providers. This has > happened several times ( spam post to mailing list, they > just stops accepting email to us for a few days or more). This would > be harder to stop than list posts. > > - I suspect it would be a large source of suport costs... helping people > set things up, debugging when it went wrong, etc. > > I think the current status quo is the best we can do. >
There are a couple of other factors which would need to be dealt with: 1. How are the separate password/keys stored and reset in FAS? The current system would likely require every email to use 2 factor for anyone who has it set up which means knowing how to make it work in any email system. 2. The routing of the email and other items would need to be dealt with. Currently incoming email to @fedoraproject.org goes to ssmoogen@ravenfog1 09 % host -t MX redhat.com redhat.com mail is handled by 10 us-smtp-inbound-2.mimecast.com. redhat.com mail is handled by 10 us-smtp-inbound-1.mimecast.com. ssmoogen@ravenfog1 09 % host -t MX fedoraproject.org fedoraproject.org mail is handled by 20 us-smtp-inbound-2.mimecast.com. fedoraproject.org mail is handled by 10 us-smtp-inbound-1.mimecast.com. to allow for spam filtering and dealing with things from the 2008 incident. This currently gets managed by whatever group inside of IBM does that. KDE uses a different system to send email which goes to letterbox.kde.org which also seems to handle mail.kde.org and other filtering. They have a fairly well thought out structure for this with kdemail.net for just aliases and kde.org just for specific developers. The majority of email is set up to just forward versus allow for setting. Going from the help pages, a person must request and get an allowance for sending to occur for kdemail.net. Getting email systems set up would probably require 6-9 months of work with reviews on how email would be handled, changes to FAS and related services, where any forwarding host would be, how that is setup, getting the services set up, getting the approvals to firewall changes and any dealing with post incident requirements for auditing. It is a significant amount of work and I think would probably end up going to the Council for 'this is something we want done and this is what we aren't doing to get this done'. -- Stephen J Smoogen. Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
