Recent content by slava_ua

"data": [ { "receiver": "id": "C0R2159T133318405", "envelope_sender": "noreply@dhl.com", "from": "DHL EXPRESS <noreply@dhl.com>", "subject": "Re: DHL Notification / DHL_AWB_001179703/ETD", "bytes": 1819354...

Yes, indeed, there is a letter with a prohibited file type in the attachment quarantine, the content of the file may be bad

Yes, I delivered a log in the interval when there was a message

Good day! Recently, such zaps have begun to appear with a certain periodicity: Jun 04 09:54:41 pmg pmgproxy [489]: Deep recursion on subroutine "HTML :: Element :: delete" at /usr/share/perl5/HTML/Element.pm line 567. Do not mention it ? P.S. Mail Gateway version 6.4-4

Thanks, I also assumed that perhaps this is due to the cache, I will study in more detail on this topic to understand

Here is a quote from the Postfix instruction: "Recipient address verification is relatively straightforward and there are no surprises. If a recipient probe fails, then Postfix rejects mail for the recipient address. If a recipient probe succeeds, then Postfix accepts mail for the recipient...

No, in the settings YES I also noticed that the recipient check (NOQUEUE: reject: RCPT from) is processed correctly in the based one, but in isolated cases the smtp client connects to the mail server, even if the recipient check was successful Proxmox mail works for about a month

Thanks for the answer! If you look at the log, then: (More logs in the file) Oct 8 19:15:54 pmg pmgpolicy [32511]: SPF says pass recipient verification is turned on and should be like this (NOQUEUE: reject:): (this is an example from another check). (domain name is replaced with *) Oct...

Hello! I can't understand why, if recipient verification is enabled (code 550), first a message is sent on behalf of double-bounce and if the recipient does not exist, the response "status = undeliverable" is returned and then the message is discarded - NOQUEUE: reject: RCPT from *: 550 5.1 .1...