@dashrender said in Local SMTP relay?:

@pete-s said in Local SMTP relay?:

@voip_n00b said in Local SMTP relay?:

@pete-s said in Local SMTP relay?:

Do you have any pointers on how to configure postfix for this?

Lots of guides when googling "postfix smtp relay"

Here is one:
https://www.lisenet.com/2018/configure-postfix-to-relay-mail-to-an-external-smtp-server-on-centos-7/

Thanks! It looks simple enough and I hope it is.

When I looked at the postfix documention it seems like it's a lot more complicated than that.

is CentOS still where people want to be for things like this?

Not generally and never CentOS 7.

@IRJ said in How to configure automatic updates on Ubuntu 18.04 LTS:

Scripted a bit for anyone interested

FWIW, this line didn't work for me --

sed -i '/Unattended-Upgrade::Skip-Updates-On-Metered-Connections "true"/a\\ "${distro_id}:${distro_codename}-updates"; ' /etc/apt/apt.conf.d/50unattended-upgrades

I believe this is due to the line being inserted outside the Unattended-Upgrade::Allowed-Origins grouping.

@JaredBusch said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

@wrx7m said in Resolved - Postfix on Fedora 29 - Why Can't I Send Mail?:

It applied to the instance (multiple servers)

FFS no. That is not what anything is.

It applied to the Account. Which contains multiple instances.
Instances that could be servers or desktops or WTF ever.

My apologies. I meant to put account.

@jaredbusch said in Postfix having trouble sending to IPv6:

@fuznutz04 said in Postfix having trouble sending to IPv6:

@dustinb3403 said in Postfix having trouble sending to IPv6:

@fuznutz04 said in Postfix having trouble sending to IPv6:

@dustinb3403 said in Postfix having trouble sending to IPv6:

That would indicate that IPv6 isn't supported.

Not supported on PostFix itself, or in the actual server network config?

Just taking a guess, I would say via the networking.

So I will try this with both IPv4 AND IPv6 listed and see what happens. Specifying IPv4 only works, but I will try both.

Thanks guys.

The point here is does your server have routable IPv6 available to it?

✔ The postfix instance seems to have IPv6 enable.

✔ Your DNS seems to return IPv6 information.

:question_mark: Does your router have IPv6 enabled?

:question_mark: Does your ISP support IPv6?

This server is a Vultr box. Not using the Vultr Firewall. I just noticed in the Vultr manage page, that IPv6 is available, but no subnet has been assigned. That will do it!

@zachary715 said in How to receive e-mail alerts from internal devices:

Do you guys go beyond the SPF records and also implement DKIM or DMARC? I've looked into these briefly but not much. DKIM looks fairly straightforward with Office 365.

I've checked them both. I will not implement DKIM anytime soon. It adds little on top of SPF.

DMARC is a layer on top of SPF and/or DKIM you cannot use DMARC without one of the other in place.

All DMARC does is tell the recipient system what to do with a message that fails the SPF/DKIM check. Instead of letting the recipient system decide what to do about it.

@jaredbusch Lol. Spoken like a true IT generalist

@JaredBusch before this post
0_1513632960663_before.jpg

@JaredBusch after this post
0_1513632969516_after.jpg

@scottalanmiller said in FreePBX Send Mail Error on Vultr:

@JaredBusch said in FreePBX send mail error:

Did you request smtp be unblocked by vultr?

It's blocked by default, so if you forget to request this on any server, outbound emails won't work.

The block is account level. Not per server.

And there goes a successful mail test.

Mar 7 11:25:24 relay01 postfix/smtpd[2206]: connect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/smtpd[2206]: CB2E6C0C82CB: client=owncloud.domain.local[10.201.1.17] Mar 7 11:25:24 relay01 postfix/cleanup[2208]: CB2E6C0C82CB: message-id=<[email protected]> Mar 7 11:25:24 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: from=<[email protected]>, size=591, nrcpt=1 (queue active) Mar 7 11:25:24 relay01 postfix/smtpd[2206]: disconnect from owncloud.domain.local[10.201.1.17] Mar 7 11:25:26 relay01 postfix/smtp[2209]: CB2E6C0C82CB: to=<[email protected]>, relay=domain-com.mail.protection.outlook.com[216.32.181.170]:25, delay=2.1, delays=0.05/0/0.62/1.4, dsn=2.6.0, status=sent (250 2.6.0 <[email protected]> [InternalId=42704859829911, Hostname=SN1PR0201MB1854.namprd02.prod.outlook.com] 7564 bytes in 0.244, 30.254 KB/sec Queued mail for delivery) Mar 7 11:25:26 relay01 postfix/qmgr[1665]: CB2E6C0C82CB: removed

@JaredBusch Awesome. Tks Jared. Tested and works beautifully!

@cronsloth Woot

@Mike-Davis said in Troubleshooting Postfix Authentication to Relay:

@jt1001001 said in Troubleshooting Postfix Authentication to Relay:

is there some sort of anti-spoofing settings with Intermedia?

That's probably what is going on. I was working with their support last night and they said they couldn't transfer me to a level 2 tech because I wasn't listed on the account. This tech also told me that they allow anonymous emails on port 25, so I knew I was working with the wrong guy.

Yes, bottom line here is that Intermedia is incompetent. Which has been a question for a long time - why would anyone use Intermedia when Office 365 does the same stuff for lower cost but has Microsoft themselves backing it?

@g.jacobse said:

I don't have centOS running, and we don't have an internal Exchange - but I am curious to see if this will link into Office 365.

To set this up with Office 365, you have two choices.

Configure Postfix to send as an authenticated user. And then give that user send as rights to all accounts that will use the mail relay.

White list the public IP address that your mail relay is on in your office 365 to allow unauthenticated email to be sent through it.

Setting Postfix up as a smarthost's pretty straightforward. I've done it in reverse as an inbound mail gateway instead of using an MS Exchange Edge Transport role. I'm guessing you'd be allowing access based on IP?

While you want to keep it simple, I can't stress strongly enough to use at least outbound spam filtering. That way, in case you do somehow start churning out spam, it'll get caught before your IP gets blacklisted.