Re: Mailing List Future

"Joshua C. Colp" <[email protected]> Fri, 5 Jan 2024 06:33:38 -0400
Newsgroups gmane.comp.telephony.pbx.asterisk.devel
Message-ID <CAM0A2Z20C9o4mUw35XnHVC2p0kEfVMmFE=j3iBh_wW9rzrvAvA@mail.gmail.com>
--===============4267923843981729390==
Content-Type: multipart/alternative; boundary="00000000000047386a060e3062fc"

--00000000000047386a060e3062fc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Jan 5, 2024 at 6:21=E2=80=AFAM Paul Kudla <[email protected]> wrote:

>
> I think we are getting off track here,
>
> email can come from anywhere
>
> like mine when i send an email it comes from "Paul Kudla <[email protected]>"
> which is perfectly normal, if i sent an email from :
>
> "Paul Kudla <[email protected]>"
>
> that would be wrong because the email address does not exist and would
> eventually bounce on most system or more importantly get blocked in
> someone's spam filter because it is unknown to the end user.
>
> Again trying to help
>
>
> the issue creeps in when a mail system tries to send with a different
> send email address then what is in the headers.
>
> My or any other system does not block ordinary email, and the tmda (in
> my case) will trap it for approval. I can catch and kinda approve these
> but its one at a time when headers get messed with.
>
> The issues being found here is email from for example
>
> Asterisk Developers Mailing List <[email protected]>
>
> is now show as
>
> Asterisk Developers Mailing List <[email protected]>
>
> which in its self kinda correct but but group.io should really be a
> proper domain related to asterisk like the
>
> "<[email protected]"
>
> was
>
> fyi
>
>
> Hope this clarifies, asterisk mailing list really needs to come from an
> asterisk domain (or sub domain) NOT groups.io
>
> can you get n asterisk.groups.io
> (like the digium one? - lists.digium.com)
>
> this would resolve to identy issues.
>

Possibly? I created a subgroup which moved things to an
asterisk-dev.groups.io subdomain, whether that is sufficient for your
purposes I do not know.

--=20
Joshua C. Colp
Director of Engineering | Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org

--00000000000047386a060e3062fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Fri, Jan 5, 2024 at 6:21=E2=80=AFAM Pa=
ul Kudla &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><br>
I think we are getting off track here,<br>
<br>
email can come from anywhere<br>
<br>
like mine when i send an email it comes from &quot;Paul Kudla &lt;<a href=
=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a>&gt;&quot; <br>
which is perfectly normal, if i sent an email from :<br>
<br>
&quot;Paul Kudla &lt;<a href=3D"mailto:[email protected]" target=3D"_blank">pau=
[email protected]</a>&gt;&quot;<br>
<br>
that would be wrong because the email address does not exist and would <br>
eventually bounce on most system or more importantly get blocked in <br>
someone&#39;s spam filter because it is unknown to the end user.<br>
<br>
Again trying to help<br>
<br>
<br>
the issue creeps in when a mail system tries to send with a different <br>
send email address then what is in the headers.<br>
<br>
My or any other system does not block ordinary email, and the tmda (in <br>
my case) will trap it for approval. I can catch and kinda approve these <br=
>
but its one at a time when headers get messed with.<br>
<br>
The issues being found here is email from for example<br>
<br>
Asterisk Developers Mailing List &lt;<a href=3D"mailto:[email protected]=
igium.com" target=3D"_blank">[email protected]</a>&gt;<br>
<br>
is now show as<br>
<br>
Asterisk Developers Mailing List &lt;<a href=3D"mailto:[email protected]=
o" target=3D"_blank">[email protected]</a>&gt;<br>
<br>
which in its self kinda correct but but <a href=3D"http://group.io" rel=3D"=
noreferrer" target=3D"_blank">group.io</a> should really be a <br>
proper domain related to asterisk like the<br>
<br>
&quot;&lt;<a href=3D"mailto:[email protected]" target=3D"_blank=
">[email protected]</a>&quot;<br>
<br>
was<br>
<br>
fyi<br>
<br>
<br>
Hope this clarifies, asterisk mailing list really needs to come from an <br=
>
asterisk domain (or sub domain) NOT <a href=3D"http://groups.io" rel=3D"nor=
eferrer" target=3D"_blank">groups.io</a><br>
<br>
can you get n <a href=3D"http://asterisk.groups.io" rel=3D"noreferrer" targ=
et=3D"_blank">asterisk.groups.io</a><br>
(like the digium one? - <a href=3D"http://lists.digium.com" rel=3D"noreferr=
er" target=3D"_blank">lists.digium.com</a>)<br>
<br>
this would resolve to identy issues.<br></blockquote><div><br></div><div>Po=
ssibly? I created a subgroup which moved things to an <a href=3D"http://ast=
erisk-dev.groups.io">asterisk-dev.groups.io</a> subdomain, whether that is =
sufficient for your purposes I do not know.</div></div><div><br></div><span=
 class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><div dir=3D"ltr=
"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div style=3D"font-fam=
ily:tahoma,sans-serif"><font color=3D"#073763">Joshua C. Colp</font></div><=
div style=3D"font-family:tahoma,sans-serif"><font color=3D"#073763">Directo=
r of Engineering | Asterisk Project Lead</font></div><div style=3D"font-fam=
ily:tahoma,sans-serif"><font color=3D"#073763">Sangoma Technologies</font><=
/div><div style=3D"font-family:tahoma,sans-serif"><font color=3D"#073763">C=
heck us out at <a href=3D"http://www.sangoma.com" target=3D"_blank">www.san=
goma.com</a> and <a href=3D"http://www.asterisk.org" target=3D"_blank">www.=
asterisk.org</a></font><br></div></div></div></div></div></div></div></div>=
</div></div>
</div>

--00000000000047386a060e3062fc--


--===============4267923843981729390==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwotLSBCYW5kd2lkdGggYW5kIENvbG9jYXRpb24gUHJvdmlkZWQgYnkg
aHR0cDovL3d3dy5hcGktZGlnaXRhbC5jb20gLS0KCmFzdGVyaXNrLWRldiBtYWlsaW5nIGxpc3QK
VG8gVU5TVUJTQ1JJQkUgb3IgdXBkYXRlIG9wdGlvbnMgdmlzaXQ6CiAgIGh0dHA6Ly9saXN0cy5k
aWdpdW0uY29tL21haWxtYW4vbGlzdGluZm8vYXN0ZXJpc2stZGV2

--===============4267923843981729390==--