I am configuring postfix and my ISP blocks port 25. To suplement i use gmails smtp server as a relay host. it works fine except that it replaces the sender address with the gmail email. I tried changing the header but it does not change it. Is there a way to get around this?
the solution is to go into your gmail account and in settings add your mail address.
then set it to default.
https://confluence.atlassian.com/confkb/when-using-gmail-as-an-smtp-server-the-from-address-is-wrong-710837471.html
Related
I have an IoT device (SEL). I want to send an email to a company gmail email (random.email#mycomp.com).
The IoT device requires the numerical IP address of the server, but I was informed that the IP address of the Gmail server always changes. How could I get the fixed IP address of the Gmail server?
Thanks.
With the limitation of this device, I am afraid you will need a proper mail server/service that you can send to (specifying an ip) and that will send the email to the gmail servers.
you can find the ip address of gmail servers with the dig command under linux
dig +short gmail.com MX
dig +short gmail-smtp-in.l.google.com A
or online : https://www.digwebinterface.com/
but it is most likely that gmail will flat out refuse your email for a few reasons; lack of spf record, lack of dkim record lack of reverse dns and lack of a matching A record and if the email comes from a redidential ip, although it is not part of the email standards, it might also get refused.
if you can authenticate as an existing existing user in gmail (with user and password) (the screenshot provided does not show if it is a possibility) then you might be able to send as this specific user.
My web server and mail server are one in the same and are on an AWS server. I set up postfix to route email to from my domain to my ISP email address. It has worked fine for many months. Recently, an SSL certificate was installed for my webserver and now I am unable to receive email. However I can still send email from the linux user account for which mail should be forwarded just fine. AWS is set up to receive SMTP connections on port 25 and SMTPS on port 465. I'm pretty sure the problem is with the SSL certificate, but not sure of the exact issue. It is a wild card SSL Cert. Any ideas?
I simply just restarted the server. That worked for me.
I've got postfix setup and running on my production server. Rather than installing another copy on my dev machine i'd like to just use the production server to send email in testing, but i'm getting "Relay access denied" errors. How do I configure postfix to allow outgoing mail from a different (my specific machine, not just any random ip of course) machine?
Does it have something to do with the relayhost param in main.cf? If so what do I add there? Any other settings need to be configured?
I just had to add my local ip to the mynetworks param.
mynetworks = a.b.c.d, .e.f.g.h
I was getting confused about using relay instead. Apparently relay is to tell postfix to use a different ip to send messages. What I needed was to tell it to accept outgoing from a different ip.
I have moved my classic asp websites from vps to dedicated server(windows server 2012). All the emails are going to spam instead of inbox(gmail and hotmail), emails are not at all receiving at yahoo. I have properly configured smtp on windows server.
Most receiving email servers are quite picky about where your email is sent from. They check your sending IP address and can choose to classify your email as spam or reject it all together unless all of the following things are true:
reverse-DNS for you IP address should give a proper name (and not look like a dynamic or dial-up address)
the reverse-DNS should again forward resolve to the same IP address
your IP address must not be on any blocklist or have a bad reputation. The problem here is that there are may different blocklists and you do not necessarily know what lists they check. You could test your IP address at http://multirbl.valli.org and see if there are any known issues
the domain-name of your sender email address can have SPF policies published in DNS that explicitly tells the world what IP addresses are allowed to send emails for that domain, and if your IP address is not included you are considered a fake sender
And there can be any number of other anti-spam/forgery checks in place that cause trouble for you. The best bet would be for you to relay your outgoing emails via an official mail server (for the domain your are trying to send from), as that already has the above things covered, but that usually requires some authentication mechanism or other agreement with the real mail server you want to use.
All these checks by the receiving end are there to stop spam and other unwanted emails. In order to not be classified as a spammer, you cannot just set up a random server at a random address and start sending emails from a random email address (or email address that normally are sent from some more official email server).
Trying to setup a SMTP send adapter in BizTalk 2010. When I specify the server name along with the port also (ex: mailserver.xxx.com:8989), mails do not go out. Otherwise they do. I couldn't find anything online about an issue with specifying the port in the servername. Can anyone confirm that we can not provide the port number in SMTP server name?
In SSIS- Send Mail task, same behavior. We are not allowed to append the port number. Could this be a related issue?
Unfortunately, specifying a custom port for the SMTP Send Adapter is not possible.
To note, the BizTalk SMTP Adapter and the Send Mail task are completely different implementations so it's just an unhappy coincidence if neither support this.
One possible solution is to configure the Windows/IIS SMTP Service somewhere in the Group and let it relay the messages.