I will like to know if there is any SMTP tunnel that you can setup to run on localhost:25 and have it forward mails to Amazon SES (TLS/SMTPS) using a username and password that you specify in the SMTP tunnel settings.
My problem is that I have an old program that I want to move over to Amazon EC2 and I want it to use Amazon SES as SMTP. But it only allows me to change the SMTPServerName setting. The username and password are empty and cannot be changed.
This user documentation will help you.
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SMTP.MTAs.html
Related
I have configured the coturn servers with long term cred (basic authen) in aws autoscaling group and placed it behind an AWS NLB.
Below is my coturn configuration in turnserver.conf
listening-port=3478
external-ip=$MY_AWS_NLB_ENDPOINT
min-port=32355
max-port=65535
fingerprint
lt-cred-mech
user=$MY_USERNAME:$MY_PASSWORD
stale-nonce
no-stdout-log
syslog
no-multicast-peers
no-cli
no-tlsv1
no-tlsv1_1
#no-tlsv1_2
However, when I placed it behind the NLB, the app connects to the NLB and works just fine, except there is no authentication part, even if I configure wrong username password in my app.
What is wrong with my coturn config?
Thanks everyone.
I have a virtual machine (local program) that works through a proxy, but does not support entering the login and password for the proxy. My proxy has a username and password. I need connect to the proxy from login and password so my virtual machine (local programm) from the intermediate server receives ready-made authorized traffic. That is, I need an analogue of the router in the local port.
I found it, but iyt not work for me
https://github.com/sjitech/proxy-login-automator
Please tell me some solutions for me.
Anybody here has experience with configuration SMTP on Cpanel host by AWS EC2.
After I have done configurations, DKIM is valid, SPF is valid, but PTR is not valid (reverse DNS). Then when I sent a test email to mail-tester.com, it was 3/10. Here is the error message
We didn't find a server (A Record) behind your hostname ip-172-31-1-135.ap-southeast-1.compute.internal.
You may want to publish a DNS record (A type) for the hostname
ip-172-31-1-135.ap-southeast-1.compute.internal or use a different hostname in your mail software.
I'm a newbie for DNS stuff, if you need more information, please give me a comment.
You should configure your mail server software to use your custom hostname (for example mail.example.com), not the AWS assigned default (such as ip-172-31-1-135.ap-southeast-1.compute.internal)
You need to contact AWS support to have PTR record configured https://aws.amazon.com/blogs/aws/reverse-dns-for-ec2s-elastic-ip-addresses/
Keep in mind that Amazon EC2 throttles traffic on port 25 of all EC2 instances by default, but you can request for this throttle to be removed: https://aws.amazon.com/premiumsupport/knowledge-center/ec2-port-25-throttle/
If you want to receive emails on this server you can't change port number from 25 to something else as other servers will try to connect on this port to deliver emails. You also have to ask AWS to remove throttle on port 25 as stated before.
If you haven't already, create A DNS record for cpanel.mydomain.com pointing to your elastic IP (it is important that you have elastic IP not automatically assigned public IP)
Finally, I got 9.8/10 after tweaking some configuration and waiting for AWS Support to map Elastic IP to my domain name, then I can get 10/10
Most importantly, have to make sure hostname has to your my domain
1. set hostname
sudo hostname cpanel.mydomain.com
Set it automatically
cd /etc/dhcp/dhclient-exit-hooks.d/
sudo nano set-hostname.sh
file set-hostname.sh
#!/bin/sh
hostname cpanel.mydomain.com
/scripts/fixetchosts
For more detail, please free to reference here
I have FTP server on Amazon EC2 which I can access by giving this URL: ftp.websitename.com:4522
after that username and password to accessing the files from this location.
Now I want to convert into secure FTP like if I will give sftp.websitename.com:4522 then it will ask me for username and password and allow me to login into the application.
First of all is this possible?
I tried below instructions for installing vsftd1 vsftd2 but didn't help me.
after doing the changes into this two link I tried to login through WinSCP and selected file protocol as SFTP and typed ftp.websitename.com, in port number 4522 and given username and password but didn't allowed me to log in.
edit 1 :
i have my amazon ec2 instance in centos 64bit.
someone else set-up the ftp connection and now i am taking forward from that point,i will get all the details and will try to modify my question in more specific way.
You didn't specify, what OS are you running. But from a reference to vsftpd, I assume some *nix flavor. You didn't specify, what FTP server you have running, and how did you set it up. Your question is pretty vague. But I'll try to give some hints.
The vsftpd is an FTP server only. It does not support the SFTP. It supports the FTPS (FTP over TLS) though. Do not get confused by its name. While the vsftpd stands for "very secure FTP daemon", it just means, it aims to implement FTP securely, not that it implements the SFTP".
Note that virtually all *nix servers come with an SSH/SFTP server built-in (OpenSSH). It runs on port 22.
For instructions how to connect to the EC2 SFTP server with WinSCP, see (my) guide:
Connecting Securely to Amazon EC2 Server with SFTP.
Also make sure you understand the difference between the SFTP and the FTPS.
From where do I get the correct syntax to create a proper SPF record for EC2 amazon server? I understand how to create a dns entry but I have no idea what to put in place for the SPF record.
This is very easy to do:
Provision an Elastic IP for your server
Setup an "A" record for the server which will be sending mail with your favorite registrar- a good practice to follow is to include "svr" somewhere in the hostname, as in, app-svr-01.youdomain.com
Click here to contact amazon and ask for a reverse dns record for the IP
add the following somewhere in your SPF record and you should be good to go:
a:app-svr-01.youdomain.com
Note: if you need to relay mail through this server from your other AWS servers, or communicate between servers in any other way, you shoukd not use this new FQDN, but rather the AWS FQDN from the AWS console (it will look like ec2-xxx-xxx-xx-xx.compute-1.amazonaws.com).
Using your custom domain name will route through the "WAN" and incur bandwidth charges.
You can use the Amazon Simple Email Service (SES). If you only use this service (and not directly), then your SPF can be as simple as described in the FAQ:
http://docs.amazonwebservices.com/ses/latest/DeveloperGuide/SPF.html
maybe changing it to a definite fail on mismatch:
v=spf1 include:amazonses.com -all
Creating an SPF record for an EC2 instance is a waste of time. Every major ISP and blacklist will blackhole mail from an EC2 IP no matter what you do. Since anyone can spin up an instance, get a new IP, send spam and disappear, nobody trusts their mail.
Use an external mail server, like SendGrid.