24 ms·
Does this prevent the whole custom@domain.com via name@gmail.com thing?
by anon1094 5y ago
Does this prevent the whole custom@domain.com via name@gmail.com thing?
- charcircuit 5y agoI'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.
- krono 5y agoYou 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!
- krehl 5y agoI 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.
- minerva23 5y agoYes
- feupan 5y agoThat 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 "me@example.com via example@gmail.com" text regardless. My setup: 1. log into example@gmail.com 2. set up "Send as me@example.com" with alias 3. enter example@gmail.com as the SMTP username Headers: ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of example@gmail.com designates 209.85.220.41 as permitted sender) smtp.mailfrom=example@gmail.com Return-Path: <example@gmail.com> From: Me <me@example.com>