These directories are created in /tmp ... because they are temporary files.
They contain the mail when a user looks at it in their quarantine.
Why do you want to not have them?
This sounds odd - it can happen that a google IP gets listed here and there - but that's quite the exception...
in my experience it usually is...
which makes me think - maybe it's your DNS-Setup (e.g. we had reports here in the forum, that some firewalls/routers (in that case it was pfsense...
The issue is more that PMG itself is sending the mails (unless the IP is not the one from your PMG!)
PMG itself adds it's local network to the trusted networks - thus the mail is accepted.
as said if it is indeed PMG sending the mails - then check the system for signs of a break in - I would...
please make sure that this is indeed the local ip configured on your PMG (saying this since I have spent quite a lot of time hunting ghosts, because I misread one of the octets)
If this is the case - I'd suggest you inspect your PMG thoroughly - maybe somebody has broken into the system, and is...
sehe jetzt auch nix auffälliges (bin aber auch kein unbound experte... und es scheinen keine debug-logs von unbound aufgedreht zu sein - die würden wohl mehr verraten).
potentielle ideen für weiteres debugging:
* einfach einen anderen DNS-Server verwenden (der vom ISP, oder jener, der sonst so...
If you want to adapt the postfix config in PMG you need to use the templateting system:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine
I hope this helps!
Out of curiosity: what kind of additional checks do you run there?
der konfigurierte DNS-server scheint auf localhost zu laufen - mit `ss -ulnp` herausfinden welcher prozess auf udp port 53 lauscht - und dessen logs ansehen.... z.b. im fall von unbound: `journalctl -u unbound`
In the rule-system - there even is a rule in the default ruleset called Blacklist - just add a regular expression '.*\.ru' to the corresponding Who Object.
This message tells you that the mail was rejected because the sending IP is listed on zen.spamhaus.com.
The IP belongs to Google according to whois information - so it probably is a legitimate mail.
The IP is currently not listed at spamhaus - so the next report should be accepted (or at least...
as said PMG automatically adds it's local network - you need to adapt the main.cf.in template and not use the variable for this:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine
you also did not post the relvant logs where the messages first came in (mostly only...
This describes an oubound message (postfix/smtp is the smtp client) - here your PMG successfully sent an email to mail.your-server.be
I would suggest to clear the queue with all the deferred mail (make sure you only remove the spam-messages) - then maybe you see better where the mails...
is your PMG our-mail.server.name? - else I don't understand local-ip-of-proxmox in this context.
Also it's odd for the system to log mails originating from it with it's public ip-address..
The logs simply say, that PMG cannot connect to port 25 on both protonmail server and gmail servers.
As it's really unlikely that both are down - my guess is that your ISP simply does not allow connections on port 25 from your IP
(This is not uncommon, as it is quite an effective way to prevent...
What do you mean with "initialized"?
* PMG ships the config-files in `proxmox-spamassassin`
* The relevant config that PMG does happens through the templateing system:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_template_engine
- so if you need to adapt the config - use...
The screenshots you shared do not show where the emails from info@your-server.be came from - so it's not possible to see where the issue is.
Please post the logs of the initial submission of such a mail - as plaintext and not as screenshot
Ahh - I see - yes - quarantined mails that are released are not signed (I did not think about that, as those mails are delivered to the downstream server and in most deployments it makes sense to have the downstream server simply accept mails from PMG).
In general logs can be found:
* in the...
This is explained in our reference documentation:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmgconfig_whitelist_overview
I hope this helps!
then please share the logs - or describe what kind of mail is rejected by which provider for which reason.
In general we cannot guarantee a ETA for a particular feature/change - getting mails sent by PMG directly signed is on our roadmap though
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.