I came across a very strange feature of Gmail, I am not 100% sure whether it is a feature or not.
The below email address are valid for a given email address devank007#gmail.com:
devank.007#gmail.com
devank0.07#gmail.com
How many such cases are there where any email provider accepts these?
Google doesn't treat the . as a character in their email addresses. Hence hikingfan#gmail.com, hiking.fan#gmail.com or hi.kin.g.fan#gmail.com refer to the same email address.
And somewhat similar is true with using + in your Gmail addresses, for example, hikingfan+banks#gmail.com, hikingfan+coding#gmail.com or hikingfan#gmail.com refer to the same email address.
These features of Gmail might help you easily create various filters. Note that the same might not be true for other email service providers.
Source: googleblog
Related
I'm sending emails via this custom email address sales#decorbunny.a2hosted.com that I have but all the emails are ending up in spam. i have done all of the following authentications
DKIM (Domain Key Identified Mail)
SPF (Sender Policy Framework)
DMARC – requires you to already be using DKIM and SPF
I also tested the emails score here at https://www.mail-tester.com/ and its 10/10. But still the emails end up in spam. Can anybody please tell what can be the issue?
If you're sending bulk emails make sure the list your using isn't bad and that your email address isn't marked as a spam address by services.
If your emails contain links to fishy/sketchy websites then it can be marked as spam.
Your using too many images or too much images with too little text.
You're sending too many attachments.
Your recipient marked you as spam.
Your outgoing email information is incorrect/bad
If you're using a hosting service then contact your provider and see if something is up or if they can provide any insight! Email's are next to printer's in how fun it is to troubleshoot. Goodluck! If it's just one email your sending to that is marking you as spam then check it's settings if you can, or ask that email address owner to whitelist you, that is if your not sending bulk. Don't go asking 100+ people to whitelist your address lol
I have a verified domain configured in SES. When I send an email with no-reply#my.domain, SES is not sending the email. If I use a valid email address from that domain, SES delivers them.
Does anyone know why this is happening? If my memory doesn't fail me, this used to work just fine as I've had this setup for years. Did something change recently in the AWS SES service?
I have looked for any mention regarding this and all I found is that the domain needs to be verified which it is.
Any help/insight would be greatly appreciated.
According to AWS SES documentation, such emails are hight not recommended
Avoid using a no-reply address, such as no-reply#example.com, as your
"From" or "Reply-to" address. Using a no-reply# email address sends
your recipients a clear message: that you aren't offering them a way
to contact you, and that you're not interested in their feedback.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/tips-and-best-practices.html
In addition to the domain being verified, the sender email address that you want to use should be verified too. AWS will send you a mail to this address to confirm that it exists. If it doesn't exist, you can create a email receiving rule that will save the email into S3. You can then dig the verification link from there.
I recently realiased a change of the email address of a someone I have been emailing for ages. Her email address used to be like amy#company.com. Now Gmail cannot deliver the email and the email address should be amy#company.com.fr. She said she never changed anything.
So, are these two email addresses different i..e can they co-exist? And why would it work before?
The email addresses are different - unless the same company owns both domains and forwards them to the same accounts.
Does anyone know if you can hide or modify some of the header fields from the sent email via the Gmail web interface?
such as:
X-Gmail-Original-Message-ID: xxxxxxxxxxxx#mail.gmail.com
Message-ID: xxxxxxxxxxxxx#mail.gmail.com
My idea would be to completely fake (hide the fact) that the said email was sent from the Gmail web interface. The goal of that would be simple - use Gmail even if the company you work for, does not allow it.
Perhaps there is a Gmail extension for that?
AFAIK, you can only change the from email when sending email from Gmail. Take a look at Send emails from a different address or alias.
Also, there are techniques to really find out where an email came from; forging email headers and/or spoofing emails is something that spammers do and will get your IP address blacklisted by your ISP.
You can also check How can I find out where an email really came from?. The headers can also be put in SpamCop and let them do the trace work with an option of sending a SPAM notice to the responsible sysadmin.
If I have a temporary email address that hides a real address, would it be possible for someone to find out the real address?
One possible way I can think of could be tracking a read receipt by sending over a pixel by pixel image and tracking the email address that loads it.
Are there any other ways or would this be pretty good at hiding the address from spammers?
No, you usually can't identify the "real address" behind a temporary one, unless the recipient replies to your message using its real email address (whether it's a manual response, or an automatic one like a read receipt).
That's especially true when your temporary email address is provided by a disposable email provider. However, if your temporary address is indeed an alias on the same email server as the real address, the SMTP VRFY command may be used to resolve an alias to its real email address. But that SMTP feature is disabled on most email server, for obvious security reasons.
As CBroe pointed out, including an image or a link in your email wouldn't help you finding the real email address. Because mail content would be HTML, displayed by the brower, and not at all related to the email context. At most, it would tell you that the email was received and its content scanned. That's not even a guarantee that a human opened it, since some antispam filters resolve URLs to ensure they're not a threat.