Re: Mailing List Future

--===============8839285423578161743==
Content-Type: multipart/alternative; boundary="00000000000046647f060e1dc5ba"

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

On Thu, Jan 4, 2024 at 8:07=E2=80=AFAM Paul Kudla <[email protected]> wrote:

>
> because the sender address (what a spam filter or in my case tmda would
> use)
>
> is : [email protected]
>
> which is a universal email sending address from groups.io (ie their mail
> system)
>
> currently you are using : [email protected]
>
> which is unique to Asterisk.
>

Okay, so you are saying that theoretically because it is a shared domain
name someone could theoretically receive spam from that domain name in the
future causing a deliverability issue for them for the new asterisk-dev
mailing list? I don't foresee that being an issue but if it becomes one
then I will investigate.

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Jan 4, 2024 at 8:07=E2=80=AFAM Pa=
ul Kudla &lt;<a href=3D"mailto:[email protected]">[email protected]</a>&gt; wrote:<br=
></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><br>
because the sender address (what a spam filter or in my case tmda would <br=
>
use)<br>
<br>
is : <a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]=
</a><br>
<br>
which is a universal email sending address from <a href=3D"http://groups.io=
" rel=3D"noreferrer" target=3D"_blank">groups.io</a> (ie their mail <br>
system)<br>
<br>
currently you are using : <a href=3D"mailto:[email protected]" =
target=3D"_blank">[email protected]</a><br>
<br>
which is unique to Asterisk.<br></blockquote><div><br></div><div>Okay, so y=
ou are saying that theoretically because it is a shared domain name someone=
 could theoretically receive spam from that domain name in the future causi=
ng a deliverability issue for them for=C2=A0the new asterisk-dev mailing li=
st? I don&#39;t foresee that being an issue but if it becomes one then I wi=
ll investigate.</div></div><div><br></div><span class=3D"gmail_signature_pr=
efix">-- </span><br><div dir=3D"ltr" class=3D"gmail_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-family:tahoma,sans-serif"><fon=
t color=3D"#073763">Joshua C. Colp</font></div><div style=3D"font-family:ta=
homa,sans-serif"><font color=3D"#073763">Director of Engineering | Asterisk=
 Project Lead</font></div><div style=3D"font-family:tahoma,sans-serif"><fon=
t color=3D"#073763">Sangoma Technologies</font></div><div style=3D"font-fam=
ily:tahoma,sans-serif"><font color=3D"#073763">Check us out at <a href=3D"h=
ttp://www.sangoma.com" target=3D"_blank">www.sangoma.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>

--00000000000046647f060e1dc5ba--


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

LS0gCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwotLSBCYW5kd2lkdGggYW5kIENvbG9jYXRpb24gUHJvdmlkZWQgYnkg
aHR0cDovL3d3dy5hcGktZGlnaXRhbC5jb20gLS0KCmFzdGVyaXNrLWRldiBtYWlsaW5nIGxpc3QK
VG8gVU5TVUJTQ1JJQkUgb3IgdXBkYXRlIG9wdGlvbnMgdmlzaXQ6CiAgIGh0dHA6Ly9saXN0cy5k
aWdpdW0uY29tL21haWxtYW4vbGlzdGluZm8vYXN0ZXJpc2stZGV2

--===============8839285423578161743==--