This may be a dumb question, but how do I configure my SMTP email to identify my website by domain name rather than IP address?
I'm currently running Tiki Wiki (certified by Bitnami) on Google Cloud Compute. I had no major issues setting up Mailgun, but when my website sends emails, the only indication that it's from my website is in the sender address. Everything else identifies the website by IP address.
Is there something I need to change in MyPhPAdmin? Or with Mailgun?
If you're using Tiki mail sending in SMTP mode, then you can specify the "Local server name" on the General Control Panel (zend_mail_smtp_helo), might that be what you're looking for?
Related
So basically i have a website where people can login via google sign in api, i've configured the api purely. The software is made out of php and twig. But i wanted to know if i can restrict sign in from google. Like, 2 people can't log in to the website simultaneously at a moment. Suppose, i have an email logged in via google named email#gmail.com and im gonna log in to the same email from another place with another ip address. Can i restrict that?
I am trying to send email from my Django application. For this, I have used Twilio SendGrid service. Though my application can send the email, it ends up in spam folder. So, I have followed this tutorial to authenticate my domain which I bought from AWS route 53. In sendgrid, the domain authentication status shows 'verified' but the emails are still sent to spam folder. I have not created any MX or TXT record in DNS setting as the tutorial says it was created automatically during domain authentication in sendgrid.
One thing I have noticed that the email still shows, 'via.sendgrid.net' message (attached an image below) with the email. Whereas it should be my authenticated domain name. I have created sendgrid account with an outlook email and using that address to send email from Django app. Is this the reason my emails are going to spam? Or can anyone please help me to find a solution for this problem? Thanks in advance.
FYI: I have done 'Single Sender Verification' in sendgrid during developing this app. But now I have deployed it in aws. I guess this feature is still working instead of 'Domain Authentication'.
Have took 2 day, can't find a good method.
1.AWS Linux instance have pre-install sendmail, I only need to send out email. But don't how to configure sendmail and other package.
2.Try to use AWS SES, however it needs to verify domain, which means I need to deal with AWS Router 53. After reading very complicated document and "create hosted zone", the AWS SES domain verification still "pending" after 24 hours. I am guessing maybe the default EIP domain name, like "ec2-***-amazonaws.com" is not a qualified/Registered domainn ?
As a newbie for SMTP setting, really don't know what to do? Since even if using a free mail server, it seems still need to 'verify domain', if aws default domain name "ec2-***-amazonaws.com" is invalid, how can I pass the domain verification?
By the way, since sendmail is pre-install, and this website is very simple, small group used, how to set configuration and other package to do email server on this instance itself?
Any suggestion is appreciated!
Thank you
It's much easier if you configure email from your Django app directly to a third party email provider, effectively by-passing the local sendmail configuration altogether. Trying to set up an email connection to AWS/SES on the server itself is also a pain, it's also much easier to configure the Django app to connect directly to AWS/SES
You have three very popular choices to setup email from Django:
Set up a connection to Gmail/Google apps .- If you'll be sending a lot of email volume I wouldn't recommend this option, because they block you easily if you use it to relay a lot of email.
Set up a connection to AWS/SES.- You mention you already tried this, but now try to set the connection inside Django using the Python packages boto and django-ses, this will make the email setup much easier. In addition, boto is also useful if you plan to use some other AWS service like S3.
Set up a connection to Mandrill.- This is another provider, not as big as Google or AWS, but they provide good service with decent free email volume and you can also set up a connection directly from Django.
Take a look at this article -- which I wrote -- that describes all the set up steps for all three providers in detail:
http://www.webforefront.com/django/setupdjangoemail.html
Recently discovered in our Google Admin Portal that: Per User outbound Gateway is turned on, checking with other people I work with, no one knows why its turned on and when it was turned on.
I have been digging through the Google admin sdk and have not found a way to check to see if any users is using this setting.
In short, does anyone know how I can check to see if a user in our domain has a secondary smtp connection or a "Send Mail As" option in use?
So, the setting 'allow per user outbound gateway' does indeed give users permissions to add a 'From' address external to your domain. However if anyone is using this, they'll likely need to configure it as a send-mail as address inside Gmail.
You can list all 'Send as addresses' via the Email settings API as per https://developers.google.com/admin-sdk/email-settings/#retrieving_send-as_alias_settings. Note that the code examples provided will not work as they're out of date and showing client Login which has been disabled for months now. I'd be advising you to Auth with Oauth 2.0, call the endpoint with wget or CURL(probably wget since recursive)
My Django application sends email out to users. On localhost, it was using my gmail account that i set via settings.py. However, when porting the app onto Openshift, all the headers were ignored. Instead of using the application from, reply-to email addresses, email coming from application on Openshift is FROM no-reply#rhcloud.com and no Reply-to email address.
Here is what I later found:
All e-mails routed through our servers have their From header rewritten. This will continue to function this way until we support e-mail as an "official" feature. Relaying through an external mail server should not overwrite this header." by Sumana Annam, Red Hat, Inc.
https://www.openshift.com/forums/openshift/sending-email-from-jboss-by-defect-the-from-is-no-replyrhcloudcom
Does anyone find a way of sending email from Openshift where the email header does not get rewritten?
Greatly appreciate any help/direction.
The official answer is that you would need to use a third party library to remove the no-reply#rhcloud.com. There is no way to change that header on email that is relayed through openshift's email servers.