[asterisk-dev] Mailing List Future
Paul Kudla
paul at scom.ca
Thu Jan 4 06:28:27 CST 2024
ok
i will post examples if/when this happens then for better clarificastion
unless groups.io is uniqe to asterisk ?
being an isp mailing lists / open systems are the first to get hacked !
Have A Happy Thursday !!!
Thanks - Paul Kudla (Manager SCOM.CA Internet Services Inc.)
Scom.ca Internet Services <http://www.scom.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email paul at scom.ca
On 1/4/2024 7:21 AM, Joshua C. Colp wrote:
> On Thu, Jan 4, 2024 at 8:07 AM Paul Kudla <paul at scom.ca
> <mailto:paul at scom.ca>> wrote:
>
>
> because the sender address (what a spam filter or in my case tmda would
> use)
>
> is : bounce at groups.io <mailto:bounce at groups.io>
>
> which is a universal email sending address from groups.io
> <http://groups.io> (ie their mail
> system)
>
> currently you are using : asterisk-dev at lists.digium.com
> <mailto:asterisk-dev at lists.digium.com>
>
> 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.
>
> --
> Joshua C. Colp
> Director of Engineering | Asterisk Project Lead
> Sangoma Technologies
> Check us out at www.sangoma.com <http://www.sangoma.com> and
> www.asterisk.org <http://www.asterisk.org>
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
More information about the asterisk-dev
mailing list