As your rule does not have a final action (Quarantine, Accept, Block) they are not set to one of those states - and these states are what cause the different highlighting - see:
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#pmg_tracking_center
The modify field actions are also not...
The tracking center takes it's data from /var/log/syslog and the rotated variant (/var/log/syslog.1, /var/log/syslog.2.gz,....)
you can delete the data there - or wait until it is rotated out (usually 4 weeks)
This is the option to translate certain attachments (e.g. docx, odt, jpg, pdf) to plain-text and scan those for Spam...
It was added with SpamAssassin 4.0.0 (available since PMG 7.3) - see the roadmap:
https://pmg.proxmox.com/wiki/index.php/Roadmap#Proxmox_Mail_Gateway_7.3
I hope this helps!
This is most likely due to a missing reverse (or forward) DNS entry for myhostname.my-domain.com pointing to your PMG's IP address - in your internal DNS
Either add those entries, or add your PMG's IP-Address to the trusted relays of your downstream server (10.31.1.10)
I hope this helps!
else...
hm - Since the question does not come up the first time - I would suggest you open an enhancement request over at our bugzilla:
https://bugzilla.proxmox.com - That way all users who want this functionality can subscribe and say so there - which helps us in our planning on if and when we might...
hm - I think from your description that you don't see anything in the logs for mails to your domain1.pl from booking would agree with their statement - and booking.com would most likely not say that they are having problems with some emails, if it was not the case (they need that for their...
Ich würde empfehlen Bayes zu deaktivieren (ist seit 8.0 auch der default-wert) - bei dieser mail wurden 5 punkte abgezogen wegen dem (nicht trainierten Bayes filter) - dann sollten die mails auch als spam erkannt werden.
Ich hoffe das hilft!
postfix replied with a permanent error-code to the mailserver sending the mail (mail.....google.com) - that mailserver is responsible for notifying the sender, that the mail could not be delivered (and I'm very sure google does that)
The mail itself is not stored on PMG.
I hope this helps!
The issue seems to be that your router does rewrite the source-ip of the smtp-server sending to your PMG
This says that the connection is made from your router - whitelisting this ip would result in basically allowing every IP on the internet to send you mail - not a good idea.
I'd check the...
This is not easily possible - blacklisting automatically causes the mail to be marked as deleted in the Database - and there is no easy way to restore that...
You can copy that file with scp and send it to the user as eml - would this work?
Then I guess that the issue is with domain1.pl (and booking not sending the mails there) - I'd contact booking and ask them why this does not work...
I hope this helps!
this could very well be - looking into this (along with ARC) is on our roadmap - although I cannot promise a date when it will be available...
related issues :
https://bugzilla.proxmox.com/show_bug.cgi?id=4658
https://bugzilla.proxmox.com/show_bug.cgi?id=3423
this was addressed (for the largest...
I have not experience with Microsoft Business Central - probably best to ask Microsoft support how to configure mail-relaying with one of their products. (Maybe someone from the community has experience with this and chimes in)
In general you should be able to configure PMG as outbound relaying...
yes currently there is no signing for mails originating directly from the PMG
(For mails with empty envelope/bounces, you now can chose to sign based on the From-header domain instead of the envelope sender domain - this was added in PMG 8.1, but this is not applied to mails originating directly...
Sorry our forum is public - Only the Enterprise support portal (available with Subscription of level Basic or higher) has the option of sharing data privately in general.
maybe you can anonymize them - or reduce them to the attempts from booking.com?
You need to have a destination for that e-mail - what exactly is your plan and what are you trying to set up?
(you want the MX record of the domains you want to handle to point to the external IP where your PMG is reachable - then the question remains where PMG should send the mail further (it...
We'd need the logs for that - maybe it got rejected for some other reasons.
If there is no track of booking contacting your mailgateway for the mail to mydomain.pl - make sure the MX record of your domain is setup correctly - and contact booking.com otherwise.
PMG does not use the spamassassin.service - SpamAssassin is integrated into pmg-smtp-filter
EDIT: and this service does not exist on a PMG installation - make sure you have the correct packages installed (pmgversion -v)
I hope this explains it!
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.