Why is PostFix sending mail using the email address of the smtp account?
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Gmail offers port 465 with SSL for its smtp.gmail.com server, although it rewrites the from address on any email sent that way to identify you by your Gmail address, unless you set another email address as your default in Gmail’s settings (see more on this at Lifehacker). Not always a good look.
Well, I will take a look at the gmail settings but I don't think that is the issue because as I mentioned, the tool that is running on my server to block intruders, sends me an email every ip that is blocked. The address that shows from where it was sent from contains the email@example.com address and it is indeed sending it through the gmail smtp server as well. So that doesn't mean that it is the gmail settings.
Is there any way to re-write the header when postfix is sending mail so the the reply to from: address is the firstname.lastname@example.org instead of the gmail email address? This has to be how the tool on my server is sending messages.
Yes they do have one for me to use but the server rejects the FROM: email address as it is not from the ISP's domain. Meaning, if I try to send from email@example.com the server will indicate that it is not a valid account. The originating email must come from firstname.lastname@example.org.
I would need an SMTP server to relay through that does not have any restrictions like that.
Yes, my ISP blocks outgoing port 25. I'm trying to figure out how to get this port forwarding tool I just installed to forward any outgoing mail from port 25 to port 587 instead. They havn't blocked that. By default postfix will only send directly through port 25. Wish I knew how to change that.
Maybe you can help me with this one the, I have a shell account that has an open outbound mail server and submission port 587 open. I've configured sasl authentication to connect but it keeps rejecting the relay do to authentication. I telnet'd into the account and then telnet'd to the local host on port 587 and I was able to send myself an email using the standard SMTP commands. The email I received did come from email@example.com. It sent it no problem. For some reason when I try to telnet to the same port on this other server from my local machine, it won't let me authenticate after I start with "HELO". If I start with "EHLO durhamnetwork.sytes.net", it accepts the domain and lets me continue. Problem is that I don't know how to get the encrypted user name and password to authenticate afterwards, so I don't know how it is trying to authenticate at this point.
Feb 8 03:09:25 durhamnetwork postfix/master: daemon started -- version 2.3.3, configuration /etc/postfix
Feb 8 03:10:23 durhamnetwork postfix/smtpd: connect from localhost[127.0.0.1]
Feb 8 03:10:23 durhamnetwork postfix/smtpd: 54C605E018F: client=localhost[127.0.0.1]
Feb 8 03:10:23 durhamnetwork postfix/smtpd: disconnect from localhost[127.0.0.1]
Feb 8 03:10:23 durhamnetwork postfix/pickup: 5EF285E0191: uid=100 from=<firstname.lastname@example.org>
Feb 8 03:10:23 durhamnetwork postfix/cleanup: 5EF285E0191: message-id=<Pine.LNX.email@example.com>
Feb 8 03:10:23 durhamnetwork postfix/qmgr: 5EF285E0191: from=<firstname.lastname@example.org>, size=591, nrcpt=1 (queue active)
Feb 8 03:10:23 durhamnetwork postfix/smtp: 5EF285E0191: to=<email@example.com>, relay=trifocus.net[184.108.40.206]:587, delay=0.45, delays=0.07/0.03/0.35/0, dsn=5.7.0, status=bounced (SASL authentication failed; server trifocus.net[220.127.116.11] said: 535 5.7.0 authentication failed)
Feb 8 03:10:23 durhamnetwork postfix/cleanup: CB9C95E0192: message-id=<20070208081023.CB9C95E0192@durhamnetwork.sytes.net>
Feb 8 03:10:23 durhamnetwork postfix/qmgr: CB9C95E0192: from=<>, size=2554, nrcpt=1 (queue active)
Feb 8 03:10:23 durhamnetwork postfix/bounce: 5EF285E0191: sender non-delivery notification: CB9C95E0192
Feb 8 03:10:23 durhamnetwork postfix/qmgr: 5EF285E0191: removed
Feb 8 03:10:23 durhamnetwork postfix/local: warning: dict_nis_init: NIS domain name not set - NIS lookups disabled
Feb 8 03:10:23 durhamnetwork postfix/local: CB9C95E0192: to=<firstname.lastname@example.org>, relay=local, delay=0.04, delays=0.01/0.02/0/0.01, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail)
Feb 8 03:10:23 durhamnetwork postfix/qmgr: CB9C95E0192: removed