kamailio-announce

Download

kamailio-announce@lists.kamailio.org

September 2023

2 participants
2 discussions

Kamailio SIP Server v5.7.2 stable released
by Fred Posner 27 Sep '23

27 Sep '23

Greetings, Kamailio SIP Server v5.7.2 stable is out – a minor release including fixes in code and documentation since v5.7.1. The configuration file and database schema compatibility is preserved, which means you don't have to change anything to update. Kamailio v5.7.2 is based on the latest source code of GIT branch 5.7 and it represents the latest stable version. We recommend those running previous 5.7.x or older versions to upgrade. There is no change that has to be done to configuration file or database structure comparing with the previous releases of the v5.7 branch. Thank you to Daniel-Constantin Mierla and all those contributing and using Kamailio. As always, thanks for flying Kamailio! * https://www.kamailio.org/w/2023/09/kamailio-v5-7-2-released/ Regards, Fred Posner

1 0

Change in mailing list configuration related to DMARC spam filtering
by Henning Westerholt 22 Sep '23

22 Sep '23

Hello, due to some changes from certain cloud infrastructure provider related to spam filtering with DMARC, we need to change the list manager "mailman" configuration for the following lists: * sr-users * sr-user-es * sr-dev * business * sr-docs * kamailio-announce * the administrative mailing list The change will impact the "From" that is displayed in your email program. Without that change large e-mail providers (Gmail, Microsoft O365) will reject messages from a sender with certain strict DMARC policy. This is already affecting several people on the lists (for example with GitHub notice mails), but over time the problem will certainly increase. Regarding the technical change: We will munge the From: header so it doesn't contain the domain that triggers the DMARC rejection. Essentially, the Mailman list takes ownership of the message and injects its own address into the From: header. This can affect reply-to-sender, although we add the original From: address in the Reply-To: header (or sometimes the Cc: header) to reduce the impact of this. We plan to do this for all emails unconditionally, regardless of their sender DMARC policy, to have an identical behaviour for all users. Please refer to this [1] page for more details. For a general description of DMARC refer to this page [2]. This change should have not a big impact for you, but some users might need to adapt some mail filters. Therefore, we would like to gather feedback on that change from you. We expect that the most visible change is that It will be not possible anymore to just reply by e-mail to mails from GitHub and have them "automatically" added to the discussed issue. This feature was so far used rarely and only from a few people. We plan to implement this change by the end of this week, when its done it will be also shortly announced. Best regards, Henning Westerholt [1] https://wiki.list.org/DEV/DMARC [2] https://dmarc.org/overview/ -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/>

1 1