According to RFC 2298, the envelope sender address (SMTP MAIL FROM) of the
Message Disposition Notification (MDN) must be null (<>). This
specification indicates that no Delivery Status Notification (DSN) messages
or other notifications about successful or unsuccessful delivery should be
sent in response to an MDN.
In the context of SMTP, there are two important aspects to consider
regarding the From and To entries:
- SMTP Commands: When issuing SMTP commands, it's possible to use "<>" to
represent the mail server sending the response. According to the RFC 2298,
this usage of "<>" is not intended to be blocked.
- Email Body Fields: Within the email body itself, the To, CC (Carbon
Copy), BCC (Blind Carbon Copy), and From fields can be left blank if they
are not relevant to the SMTP server's operation. These fields primarily
serve the client's use. It's important to note that the "MAIL FROM:"
command in SMTP and the "From:" field in the email message do not
necessarily need to match, nor do the "RCPT TO:" command and the To field
in the email message. This flexibility allows for different handling of
sender and recipient information between the SMTP protocol and email
content.
There might be some Spam/Phishing emails with null sender so spamassassin
will help you block it if you configured them correctly..
On Mon, Apr 8, 2024 at 5:38 PM Benny Pedersen <m...@junc.eu> wrote:
> natan skrev den 2024-04-08 12:31:
>
> >>>
> >>> Apr 6 01:15:09 amavis3 amavis[3887068]: (3887068-17) Passed
> >>> BAD-HEADER-7 {RelayedInbound}, [34.23.17.0]:38582 [34.23.17.0] <>
> >>> -> <i...@xxxx.ltd>, Queue-ID: 4VBDq04Bn7z1Q9qQ, mail_id:
> >>> 6LRhEwtUmP7u, Hits: -, size: 10888, queued_as: 4VBDq06n69z1Q9q1,
> >>> 358 ms
> >>>
> >>> I check and I not found any <> in whitelist
> > I check and nothging check whitelist in sql and nothing abou
> > whitelisted sender <>
> >
> >> check amavis config.
>
> read books :)
>
> <> is bounce addresse with must not be rejected
>
> hence its whitelisted
>
>
