Ask HN: What are options to replace “G Suite legacy” when it's retired in May?

Re:Ask HN: What are options to replace “G Suite legacy” when... by anon1094 on Thursday January 20, 2022 @03:43AM (#30006383)

Does this prevent the whole [email protected] via [email protected] thing?

[ Parent | on HN ]

Re:Ask HN: What are options to replace “G Suite legacy” when... by charcircuit on Thursday January 20, 2022 @04:59AM (#30006886)

I'm not sure what you are talking about so I don't think it's a problem as my emails look normal in gmail and it doesn't show anything weird.

[ Parent | on HN ]

Re:Ask HN: What are options to replace “G Suite legacy” when... by krono on Thursday January 20, 2022 @07:32AM (#30008071)

You might want to go over some of your email/message/security headers and look for anything unexpected (e.g. actual email address, device names, locations, etc.). The web-interface won't display most of what you'll find in there, with good reason.

Finding a way to access those headers from gmail will be a challenge though. Don't think I've ever found that button in the same place twice!

[ Parent | on HN ]

Re:Ask HN: What are options to replace “G Suite legacy” when... by krehl on Thursday January 20, 2022 @05:26AM (#30007059)

I don't think that this will enable you to send emails that conform to the DMARC standard (using DKIM and SPF). Might be ok for a side project, but in my opinion not enough for a small business.

[ Parent | on HN ]

Re:Ask HN: What are options to replace “G Suite legacy” when... by minerva23 on Thursday January 20, 2022 @05:39AM (#30007149)

Yes

[ Parent | on HN ]

Re:Ask HN: What are options to replace “G Suite legacy” when... by feupan on Monday January 24, 2022 @01:25AM (#30054265)

That didn't work for me.

My domain is still set up with G Suite with SPF and all so Google is technically fully capable of sending emails on my domain’s behalf, but if I got the "[email protected] via [email protected]" text regardless.

My setup:

    1. log into [email protected]
    2. set up "Send as [email protected]" with alias
    3. enter [email protected] as the SMTP username

Headers:

    ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of [email protected] designates 209.85.220.41 as permitted sender) [email protected]
    Return-Path: <[email protected]>
    From: Me <[email protected]>

[ Parent | on HN ]