Re: [mailop] supp...@gmail.com doesn't accept email.
On Sat, Jan 20, 2018 at 9:51 PM, John Levine wrote: > In article > you > write: >>See RFC 2142: "3. BUSINESS-RELATED MAILBOX NAMES >> >> These names are related to an organization's line-of-business >> activities." … >> >>"SUPPORTCustomer ServiceProblems with product or service" > > What? Someone didn't perfectly implement a 20 year old RFC? Alert > the Network Police! > > R's, > John L, ima!johnl > > PS: Somehow I fear they don't have a USENET or FTP mailbox either. Report them to the RFC Ignorant blocking list immediately! That will teach them! ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Heads Up
On Sat, Jan 20, 2018 at 9:41 AM, Ken O'Driscoll via mailop wrote: > On Sat, 2018-01-20 at 11:14 +1100, Michelle Sullivan wrote: >> One can only conclude, they either have a leak in their API, or they >> altered the permissions to give out emails when specifically denied, or >> they got hacked and didn't disclose it. > > They had bug for over a year between ~2012-2013 where contact details > (including email) were unintentionally exposed. Can't your friends see your email address on Facebook? Wouldn't that mean that literally anybody could be responsible for leaking this address? ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] supp...@gmail.com doesn't accept email.
Pretty sure we're already on son of RFC ignorant because their testing program uses non-rfc5321 compliant messages for testing. *shrug* Postmaster does get about 10 messages a day from a single person complaining that our abuse address actually has av and spam protection on and rejects his messages. In addition to the folks who think they need to report messages in their Gmail spam label to the Gmail abuse address. Or that forwarding their spam to 20 abuse addresses including the ftc is a scalable solution. And the recent spate of spamcop reports which claim to be new but the links only lead to 5y old messages that don't involve Gmail in any way. Brandon On Sun, Jan 21, 2018, 8:48 AM Charles McKean wrote: > On Sat, Jan 20, 2018 at 9:51 PM, John Levine wrote: > > In article < > caeydrt_gv1bl70edjcv0t51bh4mgpet-bjoohjr4hkpukni...@mail.gmail.com> you > write: > >>See RFC 2142: "3. BUSINESS-RELATED MAILBOX NAMES > >> > >> These names are related to an organization's line-of-business > >> activities." … > >> > >>"SUPPORTCustomer ServiceProblems with product or service" > > > > What? Someone didn't perfectly implement a 20 year old RFC? Alert > > the Network Police! > > > > R's, > > John L, ima!johnl > > > > PS: Somehow I fear they don't have a USENET or FTP mailbox either. > > Report them to the RFC Ignorant blocking list immediately! That will teach > them! > > ___ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop > ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
Re: [mailop] Heads Up
On 2018-01-21 09:40, Charles McKean wrote: On Sat, Jan 20, 2018 at 9:41 AM, Ken O'Driscoll via mailop wrote: On Sat, 2018-01-20 at 11:14 +1100, Michelle Sullivan wrote: One can only conclude, they either have a leak in their API, or they altered the permissions to give out emails when specifically denied, or they got hacked and didn't disclose it. They had bug for over a year between ~2012-2013 where contact details (including email) were unintentionally exposed. Can't your friends see your email address on Facebook? Wouldn't that mean that literally anybody could be responsible for leaking this address? This is configurable at the user level. ___ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
