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/>
Hi
I'm aware that to get environment variable we can use `$env(varname)` however this require to load pv module first, eg: below:
```
loadmodule "pv"
#!substdef "/DBRWUSER/$env(DBRWUSER)/g"
#!substdef "/DBRWPW/$env(DBRWPW)/g"
```
in some case we need to get variable at the beginning (or convenient way or modern application), example:
```
alias=$getenv(DOMAIN)
listen="$getenv(PRIVATE_IP)" advertise "$getenv(PUBLIC_IP)"
```
** $getenv just name of new function is similar to $env but not require pv
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3558
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3558(a)github.com>
<!-- Kamailio Pull Request Template -->
<!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable branch
- backports to stable branches must be done with 'git cherry-pick -x ...'
- code is contributed under BSD for core and main components (tm, sl, auth, tls)
- code is contributed GPLv2 or a compatible license for the other components
- GPL code is contributed with OpenSSL licensing exception
-->
#### Pre-Submission Checklist
<!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply -->
<!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above-->
<!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list -->
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [ ] Small bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
<!-- Go over all points below, and after creating the PR, tick the checkboxes that apply -->
- [x] PR should be backported to stable branches
- [ ] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
<!-- Describe your changes in detail -->
Adding TLS capability to connections between Kamailio and configured peers. Configuration done via kamailio.cfg.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3548
-- Commit Summary --
* cdp: adding TLS capability to peer connections
* cdp: documenting TLS capability related parameters
-- File Changes --
M src/modules/cdp/Makefile (2)
M src/modules/cdp/cdp_mod.c (27)
A src/modules/cdp/cdp_tls.c (196)
A src/modules/cdp/cdp_tls.h (51)
M src/modules/cdp/doc/cdp_admin.xml (97)
M src/modules/cdp/receiver.c (73)
M src/modules/cdp/receiver.h (3)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3548.patchhttps://github.com/kamailio/kamailio/pull/3548.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3548
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3548(a)github.com>