Re: [mlmmj] Roadmap for 1.5
Baptiste Daroussin <[email protected]> Sun, 5 May 2024 00:22:27 +0200
| Newsgroups | org.mlmmj.mlmmj |
|---|---|
| Message-ID | <wvm4k5n7y7wuaezsx7mskdw3n3npdkzsbu2nsecjn4ccjjpls6@pqxp6qjngkjx> |
Hi, if there is a strong request for this I would add it, but again this is not necessary including with people having a reject policy like yahoo.com. In the FreeBSD project for the mailing list we use mlmmj, we don't never munge the from, we make sure we don't alter fields that are used for dkim signatures, meaning no control/prefix control/footer and we have plenty of subscribers from yahoo.com without any problem. Best regards, Bapt On Sun 05 May 09:39, Kent wrote: > Hi Baptiste, > > With the enforcement of SPF / DKIM / DMARC, acting as a mailing list where senders aren't on the same mail server as you host is problematic for mailing lists where you are essentially forwarding/sending email on behalf of someone on another domain. > > I raised this issue on this mailing list recently and you replied that it's semi possible when using 1.4.1, but would need to configure something before mlmmj like rspamd. > > I appreciate that From-munging is a horrible workaround (I personally don't like it either) - but this is the approach that Google takes with their mailing lists and it's the only workaround I've identified that works if the senders SPF / DKIM / Dmarc records for their domain are set to reject email from other domains. > > > Do you think this is something you could add to mlmmj in 1.5 ? > > I'm thinking this would be a 'frommungle' file flag. And when present, automatically: > - replaces the 'FROM' with the from specified within the file. > - strips any of the original senders headers that are part of the original senders SPF / DMARC / DKIM checks. > - perhaps adds a X-Original-From header with the original senders email address. > > > > Cheers > Kent > > > > > On 4 May 2024, at 2:39 AM, Baptiste Daroussin <[email protected]> wrote: > > > > Hello everyone, > > > > Now that mlmmj 1.4 seems to have properly settle, I would like to propose a roadmap for mlmmj 1.5, > > please find here: > > > > https://codeberg.org/mlmmj/mlmmj/issues?type=all&sort=&state=open&labels=&milestone=4774&project=0&assignee=0&poster=0 > > > > The list of tasks I plan to do before releasing mlmmj 1.5.0 > > > > Do not hesitate to comment, discuss and propose other tasks. > > > > Basically 1.4 was mostly: modernize the code base (this is not finished, but advanced enough) and provide a test suite. for 1.5 I plan to cleanup features which in my opinion do not make sense anymore because they break fields used for DKIM signatures and implement the feature that has been requested by people here over the last year. > > > > I have no ETA for 1.5.0 it will be released when it will be released. > > > > Extra note, I would really love to get access to mlmmj.org to fix the mailing list with dkim and to be able to update the website or point it to codeberg. > > > > Best regards, > > Bapt > > > > >