Recent content by Stoiko Ivanov

did this ever happen for you in practice? and - the IDs are local to the system - yes you see them in the sending server's logs, and when sending mails further in those servers logs as well... - but to get the complete picture you already need to look at all system's mail-ids... (even im PMG...

Why do you need to set enable_long_queue_ids? - without this setting the tracking center would work as intended.

Why do you think it is disabled in PMG? There is an option to disable it - if it causes problems with downstream servers - I assume that your problem might be related to this - but please share logs else it is not possible to tell for sure. See the postfix documentation for some background...

For PMG you get some information through /var/log/pmgproxy/pmgproxy.log - there you have the IP and a change to a who object would be a POST which entry was added/removed is not logged. I hope this helps!

There is currently no What Object that limits the number of mails outgoing?

The message comes from the _User_ welcome list - you can manage that for each e-mail address under GUI->Administration->User Whitelist/Welcomelist the envelope-from (RFC5321.From) is empty, but the mail has a from header (RFC5322.From) of: From: "sales@domain.com" <sales@domain.com> See also...

This is not supported by the log-tracker (and there are not current plans to change that): https://bugzilla.proxmox.com/show_bug.cgi?id=2091 I hope this helps!

Um herauszufinden wo der diskspace gebraucht wird kann ich `ncdu` empfehlen (siehe `man ncdu` für dokumentation). z.B. `ncdu -x /` Ich hoffe das hilft mal weiter.

please share the logs of such a mail so that we're sure that we're talking about the same thing. But the SPF handling in the mail-proxy (GUI->Configuration->Mail Proxy->Options->Use SPF) is quite rigid and not configurable - if the mail gets a hard-fail it is rejected. (you can disable that and...

to achieve your goal of letting anyone who has access to port 26 relay mails to anyone - this seems correct (did not test it explicitly) In context of having a separate firewall which restricts access to port 26 in your setup - this can work - Writing this here explicitly - lest someone reads...

Why not (asking mostly to not overlook something)? The only downside I currently see is that you'd need to create the DNS-entries for all domains (you can do so before switching and while keeping the record for the currently used selector in place)

see https://bugzilla.proxmox.com/show_bug.cgi?id=2742 - please record your interest there as this helps us prioritize which features to add in the future.

Not sure if I understand the question 100% correctly - but the scores depend on each mail: * PMG uses SpamAssassin as its Spamdetector * SpamAssassin gets updates to its rules quite often (they are stored in /var/lib/spamassassin/<spamassassinversion>) depending on which rules match for a mail...

might be an interaction of the user's welcome list and a rule where you remove an attachment (or put it in attachment quarantine)... could you share your ruleset and a mail which triggers the message (anonymize what you have to keep private - but please keep the information consistent (e.g...

Thanks - please also share `pmgversion -v` (and make sure you've upgraded to the latest available packages)