Current Setup
I use Google Apps for personal / non-transactional emails. MX records for my domain point to google.
I have a dedicated IP for my LAMP server, and the SMTP port is available. I use cPanel to manage the server. I have created an email account through cPanel.
Goal
I want to use my host's native SMTP for sending transactional emails. I cannot use Google Apps SMTP because of per-day limit. These transactional emails need neither be saved in sent items nor replies to such emails be monitored.
Problem Area
I am not able to send transactional mails using host's native SMTP (not able to set this up, so no errors yet!)
Q1. Is the goal (using both host's native SMTP and Google Apps)
achievable? Looking at this and this, I believe it should be.
Q2. If yes, how should I setup in my cPanel? Please let me know if more [relevant] information about server setup is required to answer this.
Q1: Yes.
Q2: Same as if you were setting it up without Google Apps. Sending mail does not require any special setup. If you are still having difficulty, you need to check with your provider or ask the question of a cpanel expert -- the problem is unrelated to Google Apps.
What you didn't ask but need to know:
Cannot deliver email to Google Apps address; Gmail receives the same email fine
Why can't my server send outgoing email?
Related
In development, I am using java mail sender to send mail notification.
But one issue till I found is, google algorithms use suspicious algorithm to check.
And in java mail sender I saw it some time. Till that time, you can't send email. Until you go to that machine from where you are calling and in-browser login with that credential and review activity in any system.
Is there any free version?
Best paid version I can think of Amazon AWS own SMTP server.
While migrating from AWS EC2 instances to Google Compute Engine instances we got problems with sending emails via SMTP (Sendgrid).
I read a lot about it and read that the ports (587, 462, 25) of SMTP are blocked... And to read this article.
https://cloud.google.com/compute/docs/tutorials/sending-mail/#sending_mail_through_corporate_mail_servers
Questions:
For my understanding we should open a Cloud Launcher of SendGrid?
If (1) = yes, then I see it (the cloud launcher) does not support C# and our code today of sending emails is based on C#. So that we will have to change the code to one of those: Node.js, Python, Ruby, Go & PHP?
Is there any way to unblock this outbound connections on port 587 (or 462, 25)? Without Cloud Launcher.
Thanks in advance
1) Yes, if you want to use it through google. If not I recommend directly going to one of the smtp providers such as sendgrid, spakpost, mandrill... to get and account and use their smtp service to send mail.
2) You can use C# by simply not using the Cloud Launcher and purchasing an account directly from the vendor and usning their SMTP service.
3) No, port 2525 is free to send outbound emails to smtp providers through GCP so I highly recommend using that since it can be used for sendgrid as well.
I've just setup several instances on Google Compute Engine and getting trouble with email delivery system since GCE blocks outbound connections on ports 25, 465, and 587.
GCE provides details solution at: https://developers.google.com/compute/docs/networking#mailserver to using postfix to send email via smtp.gmail.com using Google Account.
The problem is Gmail has its own sending limits and it will be a big problem for high traffic website which need to send email notifications heavily.
Is there anyone has a solution to send more higher sending limits for GCE instances?
Thanks in advance.
Best Regards,
T
From the same page:
Blocked Traffic
Traffic on these ports to and from the Internet are blocked or
restricted for all Google Compute Engine instances. If you think you
have a compelling reason to allow this traffic, please contact the
Google Compute Engine team at gc-team#google.com.
All outgoing traffic to port 25 (SMTP) is blocked
Most outgoing traffic to port 465 or 587 (SMTP over SSL) is blocked except
for known Google IP addresses
https://developers.google.com/compute/docs/networking#blockedtraffic
It looks like you'll need to have a compelling reason to allow the traffic for your application; I'm presuming that hitting GMail delivery limits might be a reason. Note that companies like SendGrid also offer email delivery and management (bulk email as a service) with an HTTP interface that you could call from GCE.
We've updated our documentation to include SendGrid as an additional option. You probably want to take another look.
https://developers.google.com/compute/docs/sending-mail?hl=en
Your best option is to sign up for Amazon SES and get the API credentials and endpoint to send mail from google cloud without any google limitations.
You can use any similar API as well.
I have a site that uses SMTP to send outgoing messages, but I'm having trouble integrating this with our exchange server.
I have an external company which hosts our exchange server, so when I setup our web site I set in the web hosts MX record to point to our exchange server. Now all emails that go to our domain get shuffled along to our exchange server, which works well.
The problem is that when I set my webhost to use the custom MX record, it switches off all email services they provide, which includes SMTP email. Now that I am setting up some forms which will use SMTP, it seems like I can't send outgoing mail.
So, with this kind of setup in mind, would it be crazy to assume that if I tell the SMTP server to send using localhost, it would look at the MX record and find the exchange server and use that to send the email? Or should I still be pointing it somewhere specific?
This might sound like I'm asking a question specific to the webhost, but I'm wondering more about the general idea of how a setup like this normally works.
Thoughts?
Generally you just point your SMTP component to the actual DNS name / IP Address of the Exchange server. You don't need to set up an MX record.
Additionally, you need to enable relaying on your exchange server for the server running your site.
I am trying to setup windows server 2008 smtp server to relay emails to gmail smtp. Everything appears to be setup but it is not sending emails. Could you please help me figure out whats wrong.
Below is the setup:
Windows server 2008 with SMTP server
feature installed. Need SMTP server
to forward all messages to gmail smtp
server to send.
I have google apps setup for my
domain, also I can send emails
throught my test app using
gmail smtp.
SMTP Server Configuration: By default has default smtp server virtual directory.
In Properties of that virtual smtp server changed following.
Fully qualified domain name = mydomain.com
smart host = smtp.gmail.com
TCP Port = 587
Out Bound Security = Basic Authentication(my username password for google apps email account)
In domains list under virtual smtp server. I have one default domain that's server dns. I added another one for my domain name.
With above setup i am trying to redirect all email to gmail smtp.
I tested connection to smtp.gmail.com from server on port 587 through telnet and it works.
I am trying to use above server from my web application also by just dropping emails in pickup directory. It get's picked up and also accepts request form web application but never sends an email.
I can see that it adds those emails in queue folder but it stays there forever.
When i try to send emails from web app to above server it rejects if To address is other than my domain.(Am i missing something in list of domains)
Thanks for all answers, finally found solution there is a property for maximum sessions which value was 0 by default. Changed it to 100 and it send all pending emails immediately.
Possible reasons are that some SMTP servers block the outgoing messages if there domain name mismatch, possible to prevent spam mails from being sent. So for example, I will not be able to send my email with an address abc#mydomain.com from my domain yourdomain.com.
Hope that helps.
Ensure your sending domain is the same as the google apps domain
Ensure your sending address is a real address and not just an alias
IIRC you need to use STARTTLS (SSL) not basic authentication
This souds like a DNS issue. Check your /badmail directory. It will have .bad and .bdp files in there. You can open these in notepad (there will be some binary in there).
However, it may point to the possible problem.
You may also want to try and enable logging on the SMTP service. There may be something in there.