Admin Email PMG 7

Loni78

Active Member
Dec 7, 2019
40
13
28
49
Hallo zusammen,

ich habe mir zu Testzwecken PMG 7 in einer Proxmox VM installiert. Soweit läuft alles. Ich habe das Problem, dass ich keine tägliche. Admin Emails erhalte, obwohl ich meine Email Adresse eigetragen habe. Was muß ich tun, damit ich die Emails erhalte?

Grüsse
Rafael
 
ist unter configuration -> options 'send daily report' aktiviert?
wenn ja was sagt
Code:
systemctl status pmgreport.service
systemctl list-timers pmgreport.timer
 
systemctl list-timers pmgreport.timer

NEXT LEFT LAST PASSED UNIT ACTIVATES
Wed 2021-07-28 00:01:00 CEST 30min left Tue 2021-07-27 00:01:26 CEST 23h ago pmgreport.timer pmgreport.service

1 timers listed.
Pass --all to see loaded but inactive timers, too.


systemctl status pmgreport.service

root@mg:~# systemctl status pmgreport.service
● pmgreport.service - Send Daily System Report Mail
Loaded: loaded (/lib/systemd/system/pmgreport.service; static)
Active: inactive (dead) since Tue 2021-07-27 00:01:27 CEST; 23h ago
TriggeredBy: ● pmgreport.timer
Process: 24557 ExecStart=/usr/bin/pmgreport --timespan yesterday --auto (code=exited, status=0/SUCCESS)
Main PID: 24557 (code=exited, status=0/SUCCESS)
CPU: 742ms

Jul 27 00:01:26 mg systemd[1]: Starting Send Daily System Report Mail...
Jul 27 00:01:27 mg systemd[1]: pmgreport.service: Succeeded.
Jul 27 00:01:27 mg systemd[1]: Finished Send Daily System Report Mail.
root@mg:~#
 
ok was sagt das /var/log/mail.log aus der zeit in der es gesendet wurde? (zwischen 00:00:00 und 00:05:00) ?
 
Hier mal ein Beispiel:

Jul 26 00:00:10 mg pmgpolicy[784]: Received a SIG HUP
Jul 26 00:00:10 mg pmgpolicy[784]: 2021/07/26-00:00:10 Server closing!
Jul 26 00:00:10 mg pmgpolicy[784]: 2021/07/26-00:00:10 Re-exec server during HUP
Jul 26 00:00:11 mg pmgpolicy[784]: WARNING: Pid_file created by this same process. Doing nothing.
Jul 26 00:00:11 mg pmgpolicy[784]: WARNING: Pid_file created by this same process. Doing nothing.
Jul 26 00:00:11 mg pmgpolicy[784]: 2021/07/26-00:00:11 main (type Net::Server::preForkSimple) starting! pid(784)
Jul 26 00:00:11 mg pmgpolicy[784]: Binding open file descriptors
Jul 26 00:00:11 mg pmgpolicy[784]: Binding to TCP port 10022 on host 127.0.0.1 with IPv4
Jul 26 00:00:11 mg pmgpolicy[784]: Reassociating file descriptor 8 with TCP on [127.0.0.1]:10022, using IPv4
Jul 26 00:00:11 mg pmgpolicy[784]: Group Not Defined. Defaulting to EGID '0'
Jul 26 00:00:11 mg pmgpolicy[784]: User Not Defined. Defaulting to EUID '0'
Jul 26 00:00:11 mg pmgpolicy[784]: Setting up serialization via flock
Jul 26 00:00:11 mg pmgpolicy[784]: Policy daemon (re)started
Jul 26 00:00:11 mg pmgpolicy[784]: Beginning prefork (5 processes)
Jul 26 00:00:11 mg pmgpolicy[784]: Starting "5" children
Jul 26 00:00:12 mg pmg-smtp-filter[8515]: starting database maintenance
Jul 26 00:00:12 mg pmg-smtp-filter[8515]: end database maintenance (5 ms)
Jul 26 00:01:10 mg postfix/smtpd[15427]: connect from localhost.localdomain[127.0.0.1]
Jul 26 00:01:10 mg postfix/smtpd[15427]: 7D2BE81323: client=localhost.localdomain[127.0.0.1]
Jul 26 00:01:10 mg postfix/cleanup[15429]: 7D2BE81323: message-id=<20210725220110.7D2BE81323@mg.xx-xxx.de>
Jul 26 00:01:10 mg postfix/qmgr[7396]: 7D2BE81323: from=<>, size=3753, nrcpt=1 (queue active)
Jul 26 00:01:10 mg postfix/smtpd[15427]: disconnect from localhost.localdomain[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 commands=4
Jul 26 00:01:14 mg postfix/smtp[15430]: Trusted TLS connection established to xx.xxx.176.66[xx.xxx.176.66]:25: TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA>
Jul 26 00:01:14 mg postfix/smtp[15430]: 7D2BE81323: to=<admin@xx-xxx.de>, relay=xx.xxx.176.66[xx.xxx.176.66]:25, delay=4.2, delays=0.06/0.02/3.5/0.61, dsn=5.7.1, status=bounced (host xx.xxx.176.66[xx.xxx.176.6>
Jul 26 00:01:14 mg postfix/qmgr[7396]: 7D2BE81323: removed
Jul 26 00:02:12 mg pmg-smtp-filter[8515]: starting database maintenance
Jul 26 00:02:12 mg pmg-smtp-filter[8515]: end database maintenance (5 ms)
Jul 26 00:02:21 mg pmgpolicy[784]: starting policy database maintenance (greylist, rbl)
Jul 26 00:02:21 mg pmgpolicy[784]: end policy database maintenance (8 ms, 1 ms)
Jul 26 00:04:13 mg pmg-smtp-filter[8515]: starting database maintenance
Jul 26 00:04:13 mg pmg-smtp-filter[8515]: end database maintenance (5 ms)
Jul 26 00:04:31 mg pmgpolicy[784]: starting policy database maintenance (greylist, rbl)
Jul 26 00:04:31 mg pmgpolicy[784]: end policy database maintenance (7 ms, 1 ms)
Jul 26 00:05:27 mg postfix/smtpd[15479]: connect from localhost.localdomain[127.0.0.1]
Jul 26 00:05:27 mg postfix/smtpd[15479]: 5BA3A8183E: client=localhost.localdomain[127.0.0.1]
Jul 26 00:05:27 mg postfix/cleanup[15481]: 5BA3A8183E: message-id=<20210725220527.5BA3A8183E@mg.xx-xxx.de>


Das kommt mir ein bischen komisch vor mg.xx-xxx.de ist der MX Eintrag bzw. die FQDN vom Proxmox Mail Gateway. Eine Email Domain mit mg.xx-xxx.de gibt es nicht.

Grüße
Rafael
 
Jul 26 00:01:14 mg postfix/smtp[15430]: 7D2BE81323: to=<admin@xx-xxx.de>, relay=xx.xxx.176.66[xx.xxx.176.66]:25, delay=4.2, delays=0.06/0.02/3.5/0.61, dsn=5.7.1, status=bounced (host xx.xxx.176.66[xx.xxx.176.6>
das hier ist AFAICS die relevante zeile, das ziel relay 'xx.xxx.176.66' nimmt die mail nicht an ?
 
  • Like
Reactions: Stoiko Ivanov

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!

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!