[TUTORIAL] Get Postfix to Send Notifications (Email) Externally

PeterAndersson said:
For those of you using zoho as smtp server I managed to get it working with the following:
/etc/postfix/main.cf
Code: 
# See /usr/share/postfix/main.cf.dist for a commented, more complete version

myhostname=proxmox.domain.com

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = $myhostname, localhost.$mydomain, localhost
# relayhost =
mynetworks = 127.0.0.0/8
inet_interfaces = loopback-only
recipient_delimiter = +

compatibility_level = 2

relayhost = smtp.zoho.com:465
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/Entrust_Root_Certification_Authority.pem
smtp_tls_session_cache_database = btree:/var/lib/postfix/smtp_tls_session_cache
smtp_tls_session_cache_timeout = 3600s
sender_canonical_classes = envelope_sender, header_sender
sender_canonical_maps = regexp:/etc/postfix/sender_canonical
smtp_header_checks = regexp:/etc/postfix/smtp_header_checks

/etc/postfix/sasl_passwd
smtp.zoho.com user@domain.com:PASSWD

/etc/postfix/sender_canonical
/.+/ user@domain.com

/etc/postfix/smtp_header_checks
/^From:.*/ REPLACE From: Proxmox alert <user@domain.com>

/etc/postfix/tls_policy
smtp.zoho.com:465 encrypt

Then run the following to apply the changes
Bash: 
chmod 600 /etc/postfix/sasl_passwd
postmap /etc/postfix/sasl_passwd
postmap /etc/postfix/tls_policy
apt-get install libsasl2-modules
postfix reload && systemctl restart postfix.service
Click to expand...
Thank you. This works perfectly over port 465. What would need to change to make it work over port 587 with startTLS besides just changing the ports in the setup above?

Just changing the ports doesn't work. The log says warning: TLS library problem: error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331:
 
PeterAndersson said:
d
Click to expand...

PeterAndersson said:
For those of you using zoho as smtp server I managed to get it working with the following:
/etc/postfix/main.cf
Code: 
# See /usr/share/postfix/main.cf.dist for a commented, more complete version

myhostname=proxmox.domain.com

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = $myhostname, localhost.$mydomain, localhost
# relayhost =
mynetworks = 127.0.0.0/8
inet_interfaces = loopback-only
recipient_delimiter = +

compatibility_level = 2

relayhost = smtp.zoho.com:465
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/Entrust_Root_Certification_Authority.pem
smtp_tls_session_cache_database = btree:/var/lib/postfix/smtp_tls_session_cache
smtp_tls_session_cache_timeout = 3600s
sender_canonical_classes = envelope_sender, header_sender
sender_canonical_maps = regexp:/etc/postfix/sender_canonical
smtp_header_checks = regexp:/etc/postfix/smtp_header_checks

/etc/postfix/sasl_passwd
smtp.zoho.com user@domain.com:PASSWD

/etc/postfix/sender_canonical
/.+/ user@domain.com

/etc/postfix/smtp_header_checks
/^From:.*/ REPLACE From: Proxmox alert <user@domain.com>

/etc/postfix/tls_policy
smtp.zoho.com:465 encrypt

Then run the following to apply the changes
Bash: 
chmod 600 /etc/postfix/sasl_passwd
postmap /etc/postfix/sasl_passwd
postmap /etc/postfix/tls_policy
apt-get install libsasl2-modules
postfix reload && systemctl restart postfix.service
Click to expand...

Hi Peter,

Thanks for the info as I'm trying to setup my email notification with zoho. The one area in get stuck in the authentication faild

Code: 
SASL authentication failed; server smtp.zoho.com[136.143.190.56] said: 535 Authentication Failed)

I'm using a app password and the from and to address is my account, but still having no luck. I was hoping you could point me in the right direction.

Thanks
 
I got problem with the config over a fresh prox install iso. While if i set a msmtp it work to direclty send mail.. i can't pass the notification using msmtp. So i try again on a new install with default postfix, but i always got this error message, from config with the 465 or 587 port :

pve74 postfix/smtp[24277]: 75DFE40E1E: SASL authentication failed; server smtp.emailprovider.com[xx.xxx.xx.ip] said: 535 5.7.0 authentication failed

config added:

Code: 
relayhost = smtp.providermail.com:465
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
# for 465: add tls_policy  3line:
smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt
smtp_tls_policy_maps = hash:/etc/postfix/tls_policy
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/Entrust_Root_Certification_Authority.pem
#smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
smtp_tls_session_cache_database = btree:/var/lib/postfix/smtp_tls_session_cache
smtp_tls_session_cache_timeout = 3600s

and with or without the : #mydestination = $myhostname, localhost.$mydomain, localhost and with or without : default_transport = smtp

============
or with this one :
Code: 
#mydestination = $myhostname, localhost.$mydomain, localhost
relayhost = [smtp.providermail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

Do we just need to install: libsasl2-modules or something else ?
*i don't put . canonical file.. as not sure what to put inside the file and if a postmap is needed too.. and no header put either.
 
Seed said:
I'm not sure I did this in the proxmox way but I couldn't get email to relay to me and some posts were dated or didn't work for me, so I did the following:

Gmail for example:

Change /etc/postfix/main.cf to include/change these lines:
Code: 
relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

#mydestination = $myhostname, localhost.$mydomain, localhost

Be sure there are no dupes as the main.cf may have smtp_sasl_security_options = {} , and relayhost = {}. Just delete or comment those lines.

Create an /etc/postfix/sasl_passwd file with:
Code: 
[smtp.gmail.com]:587    testmehere@gmail.com:PASSWD

run
Code: 
chmod 600 /etc/postfix/sasl_passwd
postmap /etc/postfix/sasl_passwd

install for passwd support:
Code: 
apt-get install libsasl2-modules

Restart service:
Code: 
systemctl restart postfix.service

Test:
Code: 
echo "Test mail from postfix" | mail -s "Test Postfix" test@test.com

Test from PVE:
Code: 
echo "test" | /usr/bin/pvemailforward


Logs:​
Code: 
/var/log/mail.warn
is helpful as well as
Code: 
/var/log/mail.info



Customize From:
This is nice so it's not from "root"​

Create smtp_header_checks file, this changes all outgoing mail:
Code: 
/^From:.*/ REPLACE From: HOSTNAME-alert <HOSTNAME-alert@something.com>

Add to main.cf:
Code: 
smtp_header_checks = pcre:/etc/postfix/smtp_header_checks

Don't forget to run postmap on the header file

#note. For pcre support you'll need to install apt install postfix-pcre and restart postfix service
Click to expand...

This was exactly what I was looking for, thanks for putting it together for the community
 
I followed the instructions above, but it didn't work for me. Maybe I missed something.

relayhost = [smtp.mail.yahoo.com]:465 smtp_use_tls = yes smtp_sasl_auth_enable = yes smtp_sasl_security_options = noanonymous smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

/etc/postfix/sasl_passwd file:
[smtp.mail.yahoo.com]:465 myemailaccount@yahoo.com:myYahooAppGeneratedPassword


When testing PVE:
echo "test" | /usr/bin/pvemailforward I receive an error "No such file or directory"

Also the logs also state "No such file or directory"
/var/log/mail.warn /var/log/mail.info
 
ikeurb said:
When testing PVE:
echo "test" | /usr/bin/pvemailforward I receive an error "No such file or directory"

Also the logs also state "No such file or directory"
/var/log/mail.warn /var/log/mail.info
Click to expand...
in 2023 testing with the PVE script should be done with :
Code: 
echo "test" | /usr/bin/proxmox-mail-forward

Logging is now handled by systemd's Journal.
use the command journalctl to show the system log (including postfix messages)
To jump to the end of log, press shift+g
 
bitsofzero said:
Thanks. The tutorial was much appreciated. I've configured my servers to use a third party mail relay service.

I encountered one problem that was readily fixed:

postfix/smtp[1415]: SMTPS wrappermode (TCP port 465) requires setting "smtp_tls_wrappermode = yes", and "smtp_tls_security_level = encrypt" (or stronger)

I merely had to add these two lines into the main.cf, restart postfix, and after that, things worked as expected.

smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt

Thanks again.
Click to expand...
Thank you very much, that solved my problem. I use a Mailserver via Mailu-Docker-Container(s).
Here is my main.



# See /usr/share/postfix/main.cf.dist for a commented, more complete version

myhostname=proxmox07.example01.at

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = $myhostname, localhost.$mydomain, localhost
#relayhost =
mynetworks = 127.0.0.0/8,192.168.13.0/24
inet_interfaces = loopback-only
recipient_delimiter = +

compatibility_level = 2

####################################################
relayhost = [example02.com]:465
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt
inet_protocols = ipv4
smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt
#mydestination = $myhostname, localhost.$mydomain, localhost

and my sasl_passwd (I used a auth token - Authentifizierungs-Tokens in mailu-admin-gui - instead of the password):

[example02.com]:465 proxmoxtest@example02.com:3ba51059d223a4f086a671391e74bf71

If i changed the sasl_passwd file:
I also had the thing, that the syslog-log (in PVE click on the node -> system -> syslog) said, that the sasl_passwd.db is older than the sasl_passwd file - i just deleted the sasl_passwd.db file and restartet the postfix twice and sent after every restart a testmail. After that, the sasl_passwd.db file got recreated.
 
I was a happy user of this tutorial. I recently discovered that with Proxmox 8.1 a new notification system has been implemented, which supports configuring an SMTP endpoint to send emails (rather than having to configure postfix to relay via a preferred SMTP endpoint).

So here's my journey in migrating to this new notification system.

First, "undo" what was done by this tutorial:
I was able to undo the changes in main.cf (in my case, I just restored the default main.cf provided with proxmox), and remove the sasl_passwd (and sasl_passwd.db) file, and restart the postfix service.

Then, configure the new notification system to use SMTP: via the GUI -> Datacenter -> Notifications I did the following:
- Add a new notification target of type SMTP. Configure all the parameters much like you had for the postfix relay
- Add a new notification matcher, matching all notifications (or define filters as required), but using the newly created SMTP notification target

A note about backup notifications: it appears that to make the transition smoother to the new notification infrastructure, backup notifications will use the legacy "sendmail" (that is: postfix) if you defined an explicit email address in the Datacenter -> Backup entries. So, to switch to the new notification system for backup notifications, you have to edit each of your backup jobs and:
- either make the "send email to" field blank (that's what I did -- I assume the Send email field has no effect since the new matcher is used)
- or select "Notification System" in the "Notification mode" field

Hope this helps!
 
  • Like
Reactions: i_am_jam, Lantis, Vox and 6 others
Hi.
I´ve managed to get my "ve" installation working with alfredos suggestion and it´s sending notification mail .

On my pbs I followed seeds guide because I don´t find any settings in the gui.

I keep getting mail with error:
"Undelivered mail returned to sender"
User (from mail) not authorized to send on behalf of (root@hostname).

Any suggestions?
 
alfredo.pironti said:
Hope this helps!
Click to expand...
It helped a lot! I was about to configure postfix manually, lucky for me I read your reply on the last page :)

I've sent a notification test and it worked via gmail smtp since I installed proxmox at home and I've got a residential IP address blocked by default.

This is how my setup looks like:
(for password, create a new app password here https://myaccount.google.com/u/0/apppasswords)

1709759444442.png
 
  • Like
Reactions: Vox, lukej0 and DavidBoo
Don't forget to change the "Targets-to-notify" to your new SMTP mail address. By default mail-to-root (sendmail) is enabled and this will only work with a subscription. You can find this under Datacenter-Notifications-Notification Matchers, there modify the default-matcher and under the "Targets to notify" tab disable mail-to-root and enable your new mail address.
 
  • Like
Reactions: i_am_jam, Vox and SunnyCloudy
Hello everyone, I'm new.. I followed the guide in all respects but I don't receive mail what can it be ??
 
SunnyCloudy said:
It helped a lot! I was about to configure postfix manually, lucky for me I read your reply on the last page :)

I've sent a notification test and it worked via gmail smtp since I installed proxmox at home and I've got a residential IP address blocked by default.

This is how my setup looks like:
(for password, create a new app password here https://myaccount.google.com/u/0/apppasswords)

View attachment 64211
Click to expand...


Thanks for the screenshot. I could get it to work via the cli but not the gui. With the cli I used port 587 so naturally I tried the same port in the gui and I just couldn't figure out why it wouldn't work. Finally I noticed the different port number in your screenshot and BAM! it's working. Kudos.
 
  • Like
Reactions: SunnyCloudy
Hello,
I've come to relaunch the subject because a few months ago I managed to configure notifications by gmail via SSL in SMTP on my proxmox 8.2.2 server.

Today I'm redoing a server with the same method but I don't receive any messages even though I'm using the same process.

1 - nano /etc/mailname
addressmail@gmail.com

2- Creating an application password on Google

3-
nano /etc/postfix/sasl_passwd
smtp.gmail.com addressmail@gmail.com:lemotdepassedegoogle

4- postmap hash:/etc/postfix/sasl_passwd && chmod 600 /etc/postfix/sasl_passwd

5- cp /etc/postfix/main.cf /etc/postfix/save-main.cf

6-nano /etc/postfix/main.cf
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
myhostname=proxmox.local
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no
# appending .domain is the MUA's job.
append_dot_mydomain = no
# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mydestination = $myhostname, localhost.$mydomain, localhost
#relayhost =
mynetworks = 127.0.0.0/8
inet_interfaces = loopback-only
recipient_delimiter = +

relayhost = smtp.gmail.com:465
smtp_use_tls = no
smtp_sasl_auth_enable = yes
smtp_sasl_security_options =
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/Entrust_Root_Certification_Authority.pem
smtp_tls_session_cache_database = btree:/var/lib/postfix/smtp_tls_session_cache
smtp_tls_session_cache_timeout = 3600s
inet_protocols = ipv4
smtp_tls_wrappermode = yes
smtp_tls_security_level = encrypt

7- service postfix reload

8 - echo “Proxmox” | mail -s “proxmox” addressmail@gmail.com

9 - tail /var/log/mail.info
cat /var/log/mail.log

When I go to place an order, I receive nothing, and nothing appears in the logs.

I'm putting the logs here because I'm having a lot of trouble understanding them

Jun 30 10:31:16 proxmox postfix/pickup[166399]: 82E7A18036F: uid=0 from=<root>
Jun 30 10:31:16 proxmox postfix/cleanup[181358]: 82E7A18036F: message-id=<20240630083116.82E7A18036F@proxmox.local>
Jun 30 10:31:16 proxmox postfix/qmgr[166400]: 82E7A18036F: from=<root@proxmox.local>, size=411, nrcpt=1 (queue active)
Jun 30 10:31:16 proxmox postfix/smtp[181360]: warning: database /etc/postfix/sasl_passwd.db is older than source file /etc/postfix/sasl_passwd
Jun 30 10:31:18 proxmox systemd[1]: session-33.scope: Deactivated successfully.
Jun 30 10:31:18 proxmox systemd-logind[875]: Session 33 logged out. Waiting for processes to exit.
Jun 30 10:31:18 proxmox systemd-logind[875]: Removed session 33.
Jun 30 10:31:18 proxmox pvedaemon[1240]: <GB_Informatics@pve> end task UPID:proxmox:0002C16D:006137D4:668116BC:vncshell::GB_Informatics@pve: OK
Jun 30 10:31:26 proxmox postfix/smtp[181360]: 82E7A18036F: to=<gmailuser.alarmes@gmail.com>, relay=none, delay=10, delays=0.02/0.01/10/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=smtp.gmail.com type=MX: Host not found, try again)
Jun 30 10:31:28 proxmox systemd[1]: Stopping user@0.service - User Manager for UID 0...
Jun 30 10:31:28 proxmox systemd[180598]: Activating special unit exit.target...
Jun 30 10:31:28 proxmox systemd[180598]: Stopped target default.target - Main User Target.
Jun 30 10:31:28 proxmox systemd[180598]: Stopped target basic.target - Basic System.
Jun 30 10:31:28 proxmox systemd[180598]: Stopped target paths.target - Paths.
Jun 30 10:31:28 proxmox systemd[180598]: Stopped target sockets.target - Sockets.
Jun 30 10:31:28 proxmox systemd[180598]: Stopped target timers.target - Timers.
Jun 30 10:31:28 proxmox systemd[180598]: Closed dirmngr.socket - GnuPG network certificate management daemon.
Jun 30 10:31:28 proxmox systemd[180598]: Closed gpg-agent-browser.socket - GnuPG cryptographic agent and passphrase cache (access for web browsers).
Jun 30 10:31:28 proxmox systemd[180598]: Closed gpg-agent-extra.socket - GnuPG cryptographic agent and passphrase cache (restricted).
Jun 30 10:31:28 proxmox systemd[180598]: Closed gpg-agent-ssh.socket - GnuPG cryptographic agent (ssh-agent emulation).
Jun 30 10:31:28 proxmox systemd[180598]: Closed gpg-agent.socket - GnuPG cryptographic agent and passphrase cache.
Jun 30 10:31:28 proxmox systemd[180598]: Removed slice app.slice - User Application Slice.
Jun 30 10:31:28 proxmox systemd[180598]: Reached target shutdown.target - Shutdown.
Jun 30 10:31:28 proxmox systemd[180598]: Finished systemd-exit.service - Exit the Session.
Jun 30 10:31:28 proxmox systemd[180598]: Reached target exit.target - Exit the Session.
Jun 30 10:31:28 proxmox systemd[1]: user@0.service: Deactivated successfully.
Jun 30 10:31:28 proxmox systemd[1]: Stopped user@0.service - User Manager for UID 0.
Jun 30 10:31:28 proxmox systemd[1]: Stopping user-runtime-dir@0.service - User Runtime Directory /run/user/0...
Jun 30 10:31:28 proxmox systemd[1]: run-user-0.mount: Deactivated successfully.
Jun 30 10:31:28 proxmox systemd[1]: user-runtime-dir@0.service: Deactivated successfully.
Jun 30 10:31:28 proxmox systemd[1]: Stopped user-runtime-dir@0.service - User Runtime Directory /run/user/0.
Jun 30 10:31:28 proxmox systemd[1]: Removed slice user-0.slice - User Slice of UID 0.

Am I doing anything wrong?
 
GB_Informatics said:
Jun 30 10:31:26 proxmox postfix/smtp[181360]: 82E7A18036F: to=<gmailuser.alarmes@gmail.com>, relay=none, delay=10, delays=0.02/0.01/10/0, dsn=4.4.3, status=deferred (Host or domain name not found. Name service error for name=smtp.gmail.com type=MX: Host not found, try again)
Click to expand...

Your host isn't resolving smtp.google.com

Please post the output of dig smtp.google.com
Same for cat /etc/resolv.conf
 
Seed said:
I'm not sure I did this in the proxmox way but I couldn't get email to relay to me and some posts were dated or didn't work for me, so I did the following:

Gmail for example:

Change /etc/postfix/main.cf to include/change these lines:
Code: 
relayhost = [smtp.gmail.com]:587
smtp_use_tls = yes
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_tls_CAfile = /etc/ssl/certs/ca-certificates.crt

#mydestination = $myhostname, localhost.$mydomain, localhost

Be sure there are no dupes as the main.cf may have smtp_sasl_security_options = {} , and relayhost = {}. Just delete or comment those lines.

Create an /etc/postfix/sasl_passwd file with:
Code: 
[smtp.gmail.com]:587    testmehere@gmail.com:PASSWD

run
Code: 
chmod 600 /etc/postfix/sasl_passwd
postmap /etc/postfix/sasl_passwd

install for passwd support:
Code: 
apt-get install libsasl2-modules

Restart service:
Code: 
systemctl restart postfix.service

Test:
Code: 
echo "Test mail from postfix" | mail -s "Test Postfix" test@test.com

Test from PVE:
Code: 
echo "test" | /usr/bin/pvemailforward


Logs:​
Code: 
/var/log/mail.warn
is helpful as well as
Code: 
/var/log/mail.info



Customize From:
This is nice so it's not from "root"​

Create smtp_header_checks file, this changes all outgoing mail:
Code: 
/^From:.*/ REPLACE From: HOSTNAME-alert <HOSTNAME-alert@something.com>

Add to main.cf:
Code: 
smtp_header_checks = pcre:/etc/postfix/smtp_header_checks

Don't forget to run postmap on the header file

#note. For pcre support you'll need to install apt install postfix-pcre and restart postfix service
Click to expand...

I did all those things and it still didn't work. I had to do these additional steps...

apt update
apt install rsyslog

After installing, start the service:
systemctl start rsyslog

Enable the service to start on boot:
systemctl enable rsyslog

Verify the Service Status:
systemctl status rsyslog

Restart Postfix:
systemctl restart postfix

After these steps, check if the /var/log/maillog file.

Also Check the following:
vi /etc/postfix/main.cf

Ensure the following line is present and uncommented:
maillog_file = /var/log/maillog

Check master.cf: Open the master.cf file:
vi /etc/postfix/master.cf

Ensure the following line is present and uncommented:
-o syslog_name=postfix

Restart Postfix: After making any changes, restart Postfix:
systemctl restart postfix

Check Permissions: Ensure the permissions on /var/log/maillog are correct:
touch /var/log/maillog
chown root:postfix /var/log/maillog
chmod 640 /var/log/maillog

Test Logging: Send a test email and check the logs again:
echo "Test mail from postfix" | mail -s "Test Postfix" test@test.com

tail -f /var/log/maillog

All this to find in the log file my password was wrong. :)
 
Last edited:
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back