Why Isn't Google Apps Email Address Receiving Email From Magento Website? - php

Ok, I've been working with this Magento 1.7.0.2 website:
http://www.kharmakhare.com
There are two forms currently on the website. If I change either form to any kharmakhare.com email address, the email is never received. If I change either form to my email address, I get the email just fine.
Yes, I HAVE checked spam. The Kharma Khare email address will not receive emails from Magento. I thought it had to do with the Google Apps not being installed correctly... except when I logged into the email there were already tons of emails in there.
They don't have any problem receiving emails, they just don't receive any emails from the website. I've searched online for an answer. All I can find is problems sending emails through Google Apps, not receiving them.
My client already did set up the SPF records as well. In addition, last time I was in Google Apps (at least a year ago) it looked completely different, so I don't know where anything is anymore.
The first form is on the contact page (this uses Magento's default contact module):
http://www.kharmakhare.com/contact-us
The other is opened by clicking on the "Free Sample" tab on the upper right side of the screen. After spending hours working on this over a couple days I finally figured out how to do what would've been a 10-minute job in wordpress; creating an alternate email form. -_-
Regardless, although I know both forms work, neither one will send to the email address it actually needs to get sent to, and its driving me nuts. Does anyone have any idea what might be causing this problem?

Switch off the mailserver for that domain.
The reason they are not getting the emails and you are is that the sending address is something#kharmakhare.com and the receiving address is somethingelse#kharmakhare.com. The MX records offloading the email to Google Apps are not used in this instance as the server will look for the local mailserver first.

Related

Pixel Email Tracking not working for Gmail [duplicate]

I was implementing pixel tracking for a gmail web service, but since today google has changed the gmail client to proxy linked images !
Is there any work around, as the proxy is giving my server a fake/masked ip and location?
This is true. gmail has been proxying all user content via it thus showing Mountain View,CA as its REMOTE_ADDR. This is true only for gmail clients. The same logic has not been working on Gmail via outlook or any other mail client.
Most email tracking companies rely on these details to differentiate the recepients of the mail.
I dont think there is a work around. But if there is one we would find out soon given that these companies have a lot to lose.
Meanwhile, you could try using HTTP_X_FORWARDED_FOR or disposition notification headers. But given that this can be messed with, there isnt much option left but just go back to making people click on links!!!
In my experience as of Aug 5 2018 my emails sent with a tracking pixel are blocked by google. I uncheck the send tracking pixel box in my crm and the message arrives instantly. The tracked email never arrives.
I made a video to show but its exactly as I just described and quite boring to watch lol. BUt you get the point. Obviously this is just in my experience but it's too bad because knowing if my clients read it is only way know not to keep sending the same message in a different way assuming it went to spam.
Looks to me like they're caching, not just proxying.. I whipped up a PHP file to output a random image selected out of a collection of 5 images... It's the same image each time.. Testing against Yahoo! mail and outlook, both of which change each time the email is opened..

Php mail() to GSuite/GMail Deliverability Issue, Not all GSuite Domains Impacted [duplicate]

This question already has answers here:
PHP mail function doesn't complete sending of e-mail
(31 answers)
can't send email to addresses at my own domain
(19 answers)
Closed 4 years ago.
I've run into a quirky GSuite/Gmail deliverability issue from a PHP mail() form on one of my websites. Here's the scenario in as much detail as I can give:
We have two businesses (A and B), each with its own domain. Both domains are set up in our corporate GSuite instance with BusinessA.com being primary.
I recently built a new website for BusinessB.com. The contact form on the site is programmed with PHP's mail() to email the form responses to 2 BusinessB.com addresses, however, the emails are not coming through. We've done the obligatory spam checks, and I've set up a new test account for BusinessB.com (testb#BusinessB.com). No BusinessB.com form response make it to the inbox. (Regular inbound and outbound email is working properly.)
To troubleshoot I added my BusinessA.com email along with an external (non-GSuite) Gmail address to the recipient list, both receive the form submissions with no issue.
Next, I added the alias testb#BusinessA.com to the testb#BusinessB.com test email address. When I add this alias to the recipient list, the form submission also comes through with no issue.
Last, I tested an existing BusinessA.com GSuite Group that forwards to the two original BusinessB.com addresses. The form responses sent to this group forward on to the two original recipients with no issue at all. (This is currently in place as a work-around, but I still need to resolve the issue)
Since the BusinessA.com address, the external Gmail address, the alias address, and the Gsuite Group all receive the email, I don't believe it is a result of a coding error.
It is important to note that prior to Business B's new domain and website they had a different domain, which resides also on the same hosting provider and is also set up as a domain in our corporate GSuite instance. There had been no form deliverability issues previously.
This leads me to believe it is something in GSuite on the domain level.
Are there domain specific settings that I am missing? Could it be a DNS record is needed? Am I thinking through this wrong?
UPDATE - solved the issue. After multiple additional attempts at rephrasing my search, I ran across this: can't send email to addresses at my own domain, while not the same question per se, #user2428118‘s answer did the trick. It was a setting in cpanel that made the difference. I already had the MX records that he mentioned so it was as easy as selecting the option of ‘remote mail exchanger’.

Specify the "send via"- or "on behalf of"-value in Mandrill

I'm using Mandrill to send E-Mails in my PHP Project and integrated it via the API. So far so good E-Mails go out and arrive their recipient, but something bothers me about the missing SPF and DKIM entries.
When the E-Mails are opened in outlook the "on behalf of" issue occurs (FAQ from mandrills KB). But I can't fix this, since too many of our customers do not have the necessary skills/ access-rights to create a SPF entry for their domain, so we learned to live with that.
We verified our own domain at mandrill to use it as custom sending-domain to get rid of the
from: reallyLongString#mandrillapp.com on behalf of customerName#customerDomain.com
and exchange it with
from: mailbot#ourDomain.com on behalf of customerName#customerDomain.com
but somehow I can't get this to work!
I cannot find an option to set "mailbot" as sender. Even worse, Mandrill makes up a phantasy e-mail-address consisting of customerName#ourDomain.com. If some customer gets the idea to send to this address we've got a disaster upcoming. Also the API does not specify anything like that in the "Messages"-Section.
How can I configure mandrill to send E-Mails with a from-field appearing in outlook like this:
mailbot#ourDomain.com on behalf of customerName#customerDomain.com
? Really cannot find anything in the docs or the web. Thanks in advance!
As Sanuel Jackson already indicated, there is no way to do this WITHOUT doing the whole certification process of creating a SPF entry.
Also confirmed by Mandrill support (which was quite fast AND competent in responding)
I'm now sending with a proper reply-to address and hope, that our customer's customers ignore the funky e-mail adresses... In case they do mind them, our customers are free to engage us regarding a SPF-entry ;-)

how to receive and validate incoming mail for web based mails in php

We are developing a email web site.but we are facing problem in receiving and validating the mail.i have the following doubts.can you please help me in clarifying these???
one more important thing is we are not using squrrelmail, qmail etc.
how do we receive emails for users in email web site?
do we save all the received emails in admin's mail box or in database as per the username
(my idea on email web site is,all the incoming mail are stored in admin's mail box and after the email mail is stored in database,and then the mail deleted in admin's mail box.Is it correct.if not how to store the emails in database directly in web site)
what is the technique behind the receiving mail???i think there are various techniques like email piping etc.
is there any special process of creating users for email web site,i mean do we need to create mailbox(i think mail account) for each user at the time of registration.if we need to create mail box for user,can we create it with imap_createmailbox() function.
are the users gmail,yahoomail etc are accessig database or their mail accounts at the time their login??
can we do all these things with imap functions in php??
There are many different solutions to this problem, polling existing servers, adding scripts to run when a message is received or using a gateway like CloudMailin. I wrote a blog post relating to this (it's for rails but almost all applies to php too).
The other problems almost all span from how you setup the first thing. In many cases you could just log the emails directly to your database and retrive them based on the recipient address. I think you need to explain exactly what you want to do with the email? Are you just providing email hosting for your users or are you providing an additional service? If you're just providing hosting then there are simpler approaches available.

PHP - Send email from other domain without being spam!

this was ask over and over and still no good solution!
When someone sends an email using php and placing another domain in "from" it will end up in spam.
Solutions normally are:
- Use your "from" and place the domain you want in the "reply-to";
- Have your domain whitelisted by main mail services.
The 1st its not really a solution and I was never able to make 2nd, because its impossible to reach hotmail.com, yahoo.com, etc..
I see lots of sites today having the option to email article to someone from the user email. How can I achieve this?
Thx,
Telmo Cardoso
When someone sends an email using php
and placing another domain in "from"
it will end up in spam.
This is not neccessarily true.
Check which mail servers identify your message as spam. Also check with your hosting company for their preferred method to send out mail.
Try to be straightforward with your message. Offer the users a short textarea (with your default masage), which they can change and customize. Also give the possibility to enter real name of the participants with their e-mail addresses.
Just be senible and your messas will go thru.
Send the email from your webserver and add a reply-to header like you have mentioned.
Make sure you have SPF setup for your server to help get yourself into the gMail, Live Mail and Yahoo accounts.
A nice and cheap alternative is to send your emails via Amazon SES to avoid having to warm your own IPs etc.
I would go with the Amazon SES (or a similar service) and leave the worrying about getting the server setup right to the experts. Make ensuring deliverability someone elses problem.
This article is a nice starting point:
http://www.codinghorror.com/blog/2010/04/so-youd-like-to-send-some-email-through-code.html
The problem is related to the header of the email. not neccessarily the 'from' address domain. Some spam filters (i.e. cox.net incoming spam filters) will perform a reverse lookup on the IP address that the email came from. If the domain name returned on the reverse lookup is not the domain name of the sending address. Then they will liekly mark it as spam.

Categories