[sr-dev] Re: Change in mailing list configuration related to DMARC spam filtering

[Henning Westerholt via sr-dev]

Hello,

there has been no feedback regarding this change, so the setting was done some 
minutes ago.

In case of unforeseen issues, just follow up on the sr-users lists for further 
discussions.

Thanks,

Henning


--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com

From: Henning Westerholt
Sent: Dienstag, 19. September 2023 10:11
To: Kamailio (SER) - Users Mailing List ; Kamailio 
(SER) - Devel Mailing List ; 
busin...@lists.kamailio.org; sr-d...@lists.kamailio.org; 
kamailio-annou...@lists.kamailio.org; sr-users...@lists.kamailio.org
Subject: Change in mailing list configuration related to DMARC spam filtering

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


___
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org

[sr-dev] Re: [kamailio/kamailio] Nonexisted route in KEMI python causes "ksr_request_route not found or is not callable" (Issue #3572)

[ShadoWalkeR31 via sr-dev]

I am at conference in other city, on next week i will return on work and test 
patch

-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3572#issuecomment-1731212115
You are receiving this because you are subscribed to this thread.

Message ID: ___
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org

[sr-dev] git:master:90cb4c8a: app_python: use global parameter for request route callback

[Daniel-Constantin Mierla via sr-dev]

Module: kamailio
Branch: master
Commit: 90cb4c8a3376b967960a2185b3acc669734f5e33
URL: 
https://github.com/kamailio/kamailio/commit/90cb4c8a3376b967960a2185b3acc669734f5e33

Author: Daniel-Constantin Mierla 
Committer: Daniel-Constantin Mierla 
Date: 2023-09-22T14:11:04+02:00

app_python: use global parameter for request route callback

---

Modified: src/modules/app_python/apy_kemi.c

---

Diff:  
https://github.com/kamailio/kamailio/commit/90cb4c8a3376b967960a2185b3acc669734f5e33.diff
Patch: 
https://github.com/kamailio/kamailio/commit/90cb4c8a3376b967960a2185b3acc669734f5e33.patch

---

diff --git a/src/modules/app_python/apy_kemi.c 
b/src/modules/app_python/apy_kemi.c
index d163a792c16..c9addc7600a 100644
--- a/src/modules/app_python/apy_kemi.c
+++ b/src/modules/app_python/apy_kemi.c
@@ -60,7 +60,7 @@ int sr_kemi_config_engine_python(
ret = apy_exec(
msg, rname->s, (rparam && rparam->s) ? 
rparam->s : NULL, 0);
} else {
-   ret = apy_exec(msg, "ksr_request_route", NULL, 1);
+   ret = apy_exec(msg, kemi_request_route_callback.s, 
NULL, 1);
}
} else if(rtype == CORE_ONREPLY_ROUTE) {
if(kemi_reply_route_callback.len > 0) {

___
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org

[sr-dev] SIP to websocket routing problems

[Centelles Martin, Joel via sr-dev]

Hello everybody,

we've  a kamailio setup as a SIP proxy/SBC that we use to route incoming 
request into our system . We also need to support web browser clients, so, we 
properly enabled and configured the websocket module according to its module's 
documentation: 
https://www.kamailio.org/docs/modules/devel/modules/websocket.html#idm37

This solution is working fine for both TLS SIP clients and incoming websocket 
INVITEs but, when we try to route a SIP call from a SIP client to a registered 
websocket client, our SBC is unable to find the proper socket connection even 
if the proper IP, port and transport is received in the Request-URI or the 
Route header:

Received request URI looks like:


  *   INVITE sip:b80snduq@185.41.96.32:54510;transport=wss SIP/2.0

while the Route header looks like:

  *   Route: 


My only guess is that the transport parameter, for some reason, is not being 
properly parsed but I've been debugging core/forward.c with no luck as it seems 
that the request is not even being forwarded.

Any suggestion about what code I should look into?  Is the destination IP, port 
and protocol usually set in the core parsing or might this be a nathelper 
module error?

Thank you very much in advance for your help.

BR,
Joel.

___
Kamailio (SER) - Development Mailing List
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org