Set up email notifications but it's not happening

[thusband]

I installed Proxmox 8.1.3 with one (so far) container. Things work great except I don't get Gmail notifications after a backup. I tried another email address (duck.com) and got the same thing.

What do I need to change? The backups are there. Just no email confirmation.

Many thanks.


Syslog shows:

Nov 27 06:29:02 pve postfix/qmgr[801]: 1CD47240E3E: from=<root@pve.home>, size=1827, nrcpt=1 (queue active)
Nov 27 06:29:02 pve postfix/smtp[121200]: connect to gmail-smtp-in.l.google.com[64.233.184.27]:25: No route to host
Nov 27 06:29:02 pve postfix/smtp[121200]: connect to gmail-smtp-in.l.google.com[2a00:1450:400c:c0b::1a]:25: Network is unreachable
Nov 27 06:29:02 pve postfix/smtp[121200]: connect to alt1.gmail-smtp-in.l.google.com[142.250.153.26]:25: No route to host
Nov 27 06:29:02 pve postfix/smtp[121200]: connect to alt1.gmail-smtp-in.l.google.com[2a00:1450:4013:c16::1b]:25: Network is unreachable
Nov 27 06:29:02 pve postfix/smtp[121200]: connect to alt2.gmail-smtp-in.l.google.com[142.251.9.26]:25: No route to host
Nov 27 06:29:02 pve postfix/smtp[121200]: 1CD47240E3E: to=<my.email@gmail.com>, relay=none, delay=139046, delays=139046/0.01/0.05/0, dsn=4.4.1, status=deferred (connect to alt2.gmail-smtp-in.l.google.com[142.251.9.26]:25: No route to host)

 

[sb-jw]

What does your resolv.conf look like?

What do you get with ping google.de and ping -6 google.de

 

[LordVader]

I have the same issue. Sending test email from Proxmox works though.

 

[LordVader]

SOLVED!

"There are 2 notification modes for backups. The first one is the 'old' one (legacy-sendmail), which will just send an email to the specified email address in case of failure or always, depending on the setting.
There is also a new setting (notification-system), where instead of sending an email to the configured address, the system will publish a notification to the new notification system. The decision if and where the notification will be routed is determined entirely by the notification system configuration. The old 'on-failure'/'always' setting has no effect there (which is not super obvious in the UI I admit, but there are already some improvements for that in the pipeline [1] that have not been merged yet.

The 'auto' setting is a bit of a hybrid, it will use the old system when an email address is configured, and a new system if not.

So I assume, that your backups do not have an email address configured, and thus the new system will be used. The default built-in configuration for the notification system is to send all notifications to the email address for root@pam."

 

[Dataninja]

SOLVED!

"There are 2 notification modes for backups. The first one is the 'old' one (legacy-sendmail), which will just send an email to the specified email address in case of failure or always, depending on the setting.
There is also a new setting (notification-system), where instead of sending an email to the configured address, the system will publish a notification to the new notification system. The decision if and where the notification will be routed is determined entirely by the notification system configuration. The old 'on-failure'/'always' setting has no effect there (which is not super obvious in the UI I admit, but there are already some improvements for that in the pipeline [1] that have not been merged yet.

The 'auto' setting is a bit of a hybrid, it will use the old system when an email address is configured, and a new system if not.

So I assume, that your backups do not have an email address configured, and thus the new system will be used. The default built-in configuration for the notification system is to send all notifications to the email address for root@pam."

I'm getting the same error message in the syslog. How did you resolve the issue? Did you just end up using an email address in the legacy-sendmail under backups?

Dec 13 20:26:36 pve1 postfix/smtp[907366]: connect to gmail-smtp-in.l.google.com[142.250.141.27]:25: Connection timed out
Dec 13 20:26:36 pve1 postfix/smtp[907366]: connect to gmail-smtp-in.l.google.com[2607:f8b0:4023:c03::1b]:25: Network is unreachable
Dec 13 20:26:36 pve1 postfix/smtp[907366]: connect to alt1.gmail-smtp-in.l.google.com[2607:f8b0:4003:c15::1a]:25: Network is unreachable
Dec 13 20:27:06 pve1 postfix/smtp[907366]: connect to alt1.gmail-smtp-in.l.google.com[64.233.171.26]:25: Connection timed out
Dec 13 20:27:36 pve1 postfix/smtp[907366]: connect to alt2.gmail-smtp-in.l.google.com[142.250.152.27]:25: Connection timed out

 

[LordVader]

Sorry for late reply. Did you solve it?

 

[LordVader]

 

[thusband]

View attachment 59968

Thanks, no, I still haven't figured it out but, hopefully, this will help. I re-installed Proxmox to clear up the log (I didn't have any VMs or containers yet). I didn't go for SMTP previously which was probably the reason.

So copying your example will get me there? The default port is different where you're using 587. Also what should Username and Password be? My Gmail login?

Thanks again, I appreciate your patience.

 

[LordVader]

Yes, username is your email address. But password, if you use 2FA as I do, must be generated at Google. See link below, it's easy

https://support.google.com/mail/answer/185833?hl=en

"An app password is a 16-digit passcode that gives a less secure app or device permission to access your Google Account. App passwords can only be used with accounts that have 2-Step Verification turned on."

 

[thusband]

Thanks again, you've been a great help.

 

[LordVader]

Your welcome. Glad I could help, been struggling myself with this, and other issues.