If you have multiple servers on a network, do you install postfix on each one
-
Looks like it does. Just set up postfix to use your email and password to send mail out.
-
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
My root issue, I guess, if that I cannot get dnf-automatic to send e-mail to any public e-mail servers. Not Office365, for example.
This is because Office365, Google, etc email does not accept and send out emails for just any random email server.
They require authentication.
This is why you need to use, in the case of dnf-automatic, an SMTP server that is set up and authenticated with Office365. That way when dnf-automatic sends out an email as [email protected], it goes to your SMTP server to authenticate, then sends via whatever account info the SMTP server is authenticating by... whether it's a global "[email protected]" address or whatever.
Actually they do. Both O365 and GMail accept without any of that stuff. Specifically, both of those we test with this all the time. Many email systems do require that, but not those.
I've tested in the last 30 minutes from a new install, in fact.
So you're saying that Gmail will let me send an email as [email protected] or whatever yoru gmail is (if you have one) without me having to authenticate? I can guarantee you it will not. This must mean you took what I said the wrong way.
-
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
Looks like it does. Just set up postfix to use your email and password to send mail out.
I swear I send email from [email protected] to [email protected] from dnf-automatic via a postfix system that does not log into gmail.
-
@jaredbusch said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
Looks like it does. Just set up postfix to use your email and password to send mail out.
I send email from [email protected] to [email protected] from dnf-automatic via a postfix system that does not log into gmail.
Wtf... how can Gmail let you send emails as someone without knowing their credentials?
That means I can start sending emails as [email protected] or w/e you email is, without knowing yoru passwor.d
-
That just doesn't make sense.
-
@jaredbusch said in If you have multiple servers on a network, do you install postfix on each one:
that does not log into gmail
-
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
My root issue, I guess, if that I cannot get dnf-automatic to send e-mail to any public e-mail servers. Not Office365, for example.
This is because Office365, Google, etc email does not accept and send out emails for just any random email server.
They require authentication.
This is why you need to use, in the case of dnf-automatic, an SMTP server that is set up and authenticated with Office365. That way when dnf-automatic sends out an email as [email protected], it goes to your SMTP server to authenticate, then sends via whatever account info the SMTP server is authenticating by... whether it's a global "[email protected]" address or whatever.
Actually they do. Both O365 and GMail accept without any of that stuff. Specifically, both of those we test with this all the time. Many email systems do require that, but not those.
I've tested in the last 30 minutes from a new install, in fact.
So you're saying that Gmail will let me send an email as [email protected] or whatever yoru gmail is (if you have one) without me having to authenticate? I can guarantee you it will not. This must mean you took what I said the wrong way.
That's an unrelated thing that you are attempting. I said that you can send email TO Gmail, not pretend to BE Gmail!
-
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
My root issue, I guess, if that I cannot get dnf-automatic to send e-mail to any public e-mail servers. Not Office365, for example.
This is because Office365, Google, etc email does not accept and send out emails for just any random email server.
They require authentication.
This is why you need to use, in the case of dnf-automatic, an SMTP server that is set up and authenticated with Office365. That way when dnf-automatic sends out an email as [email protected], it goes to your SMTP server to authenticate, then sends via whatever account info the SMTP server is authenticating by... whether it's a global "[email protected]" address or whatever.
Actually they do. Both O365 and GMail accept without any of that stuff. Specifically, both of those we test with this all the time. Many email systems do require that, but not those.
I've tested in the last 30 minutes from a new install, in fact.
So you're saying that Gmail will let me send an email as [email protected] or whatever yoru gmail is (if you have one) without me having to authenticate? I can guarantee you it will not. This must mean you took what I said the wrong way.
That's an unrelated thing that you are attempting. I said that you can send email TO Gmail, not pretend to BE Gmail!
Yeah that's not what I"m talking about then.
Yeah you can send email to any email. But I'm talking about sending as.
-
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@scottalanmiller said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
My root issue, I guess, if that I cannot get dnf-automatic to send e-mail to any public e-mail servers. Not Office365, for example.
This is because Office365, Google, etc email does not accept and send out emails for just any random email server.
They require authentication.
This is why you need to use, in the case of dnf-automatic, an SMTP server that is set up and authenticated with Office365. That way when dnf-automatic sends out an email as [email protected], it goes to your SMTP server to authenticate, then sends via whatever account info the SMTP server is authenticating by... whether it's a global "[email protected]" address or whatever.
Actually they do. Both O365 and GMail accept without any of that stuff. Specifically, both of those we test with this all the time. Many email systems do require that, but not those.
I've tested in the last 30 minutes from a new install, in fact.
So you're saying that Gmail will let me send an email as [email protected] or whatever yoru gmail is (if you have one) without me having to authenticate? I can guarantee you it will not. This must mean you took what I said the wrong way.
That's an unrelated thing that you are attempting. I said that you can send email TO Gmail, not pretend to BE Gmail!
Yeah that's not what I"m talking about then.
Yeah you can send email to any email. But I'm talking about sending as.
Okay, but none of us are talking about sending AS. We are talking about email delivery, not trying to operate an email server as an imposter on its own system.
-
@jaredbusch said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
Looks like it does. Just set up postfix to use your email and password to send mail out.
I swear I send email from [email protected] to [email protected] from dnf-automatic via a postfix system that does not log into gmail.
ah nope, I remembered incorrectly. I send from [email protected] to [email protected].
And my SPF for bundystl.com allows from the IP in question. -
I think that the core issue here is that there is a huge bit of confusion about email, how email works, and that a vendor marking received email as SPAM is after delivery has happened successfully and is a totally different and unrelated discussion.
We've all been talking about email (SMTP), but @BRRABill is actually wanting to ask questions about post-email mailbox filtering and approval by specific hosted services vendors. Which is not really about email, but about working out how to identify SPAM after it has been received.
Mixing those two concepts together as if they are one will always lead to massive confusion and a misinterpretation of events.
-
@jaredbusch said in If you have multiple servers on a network, do you install postfix on each one:
@jaredbusch said in If you have multiple servers on a network, do you install postfix on each one:
@tim_g said in If you have multiple servers on a network, do you install postfix on each one:
Looks like it does. Just set up postfix to use your email and password to send mail out.
I swear I send email from [email protected] to [email protected] from dnf-automatic via a postfix system that does not log into gmail.
ah nope, I remembered incorrectly. I send from [email protected] to [email protected].
And my SPF for bundystl.com allows from the IP in question.Exactly my point.
-
So, in my attempt to just dummy down this whole thing.
I was just saying if you send from dnf-automatic to public servers, it will not e-mail the server, be accepted by the server, and then delivered to your inbox without some work.
So far, in using postfix, I have not had any of these issues. Install postifx, works perfectly.
-
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
So, in my attempt to just dummy down this whole thing.
I was just saying if you send from dnf-automatic to public servers, it will not e-mail the server, be accepted by the server, and then delivered to your inbox without some work.
So far, in using postfix, I have not had any of these issues. Install postifx, works perfectly.
/sigh FFS
-
@scottalanmiller said
We've all been talking about email (SMTP), but @BRRABill is actually wanting to ask questions about post-email mailbox filtering and approval by specific hosted services vendors. Which is not really about email, but about working out how to identify SPAM after it has been received.
Mixing those two concepts together as if they are one will always lead to massive confusion and a misinterpretation of events.
Yes...
I used the phrase "dnf cannot e-mail me at gmail"
when the correct @scottalanmiller phrase is
"dnf cannot email me at gmail, have it accepted by gmail, and then delivered into my inbox by gmail"
-
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
@scottalanmiller said
We've all been talking about email (SMTP), but @BRRABill is actually wanting to ask questions about post-email mailbox filtering and approval by specific hosted services vendors. Which is not really about email, but about working out how to identify SPAM after it has been received.
Mixing those two concepts together as if they are one will always lead to massive confusion and a misinterpretation of events.
Yes...
I used the phrase "dnf cannot e-mail me at gmail"
when the correct @scottalanmiller phrase is
"dnf cannot email me at gmail, have it accepted by gmail, and then delivered into my inbox by gmail"
Of course it can. You need to stop saying things "can or can't" because we will FFS every one of those.
Everything works. All of it. You just have to set it up to do so.
-
The reason postfix is working for you is because you are sending via postfix directly, postfix is the relay. Your dnf-automatic I'm guessing you have told GMail to be your relay but haven't worked this out with GMail. So they are denying you relay access.
-
@scottalanmiller said You need to stop saying things "can or can't" because we will FFS every one of those.
Only one person here will.
-
@brrabill said in If you have multiple servers on a network, do you install postfix on each one:
So, in my attempt to just dummy down this whole thing.
I was just saying if you send from dnf-automatic to public servers, it will not e-mail the server, be accepted by the server, and then delivered to your inbox without some work.
dnf-automatic acts as a client, not an MTA, even though it has SMTP. So it is attaching to whatever server you are telling it is the relay and trying to relay through it. If you haven't told the server in question to accept relay access, it will fail. If you tell it to accept access, it will work.
-
Remember, Jared was telling you that with dnf-automatic that you still needed postfix, but not one postfix PER SERVER. Postfix is the relay that will work. If you want to send with zero postfix, then you need to get Google or whoever to be your relay and they have to agree to that.
The original thread is one postfix per network or one per server. If you use mailx, you need one per server. If you use dnf-automatic, you need one per network (but one per server works, too.) In both cases, GMail can't tell the difference.
