2024-07-30 14:07:55 1sYg1a-00000006UBE-1Zcn H=mail-qv1-f52.google.com
[209.85.219.52]:43452 Warning: "SpamAssassin as akasotech detected message as
NOT spam (1.3)"
2024-07-30 14:07:55 1sYg1a-00000006UBE-1Zcn <= sim...@growthmatessagency.com
H=mail-qv1-f52.google.com [209.85.219.52]:43452 P=esmtps
X=TLS1.3:TLS_AES_128_GCM_SHA256:128 CV=no S=17527
id=2c7b7f4d-42a7-441c-b5f9-cfd6f81bc...@growthmatessagency.com T="Re: Elevate
Your Marketing and Boost Revenue with Growth Mate" for c...@akasotech.com
2024-07-30 14:07:55 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc
1sYg1a-00000006UBE-1Zcn
2024-07-30 14:07:55 SMTP connection from mail-qv1-f52.google.com
[209.85.219.52]:43452 D=41s closed by QUIT
2024-07-30 14:07:55 1sYg1a-00000006UBE-1Zcn => cs <c...@akasotech.com>
R=virtual_user T=dovecot_virtual_delivery C="250 2.0.0 <c...@akasotech.com>
uDe1LTuDqGYKlxcAOtl5Ug Saved"
2024-07-30 14:07:56 1sYg1a-00000006UBE-1Zcn [54.157.237.25] SSL verify error:
certificate name mismatch: DN="/C=US/ST=California/O=Proofpoint,
Inc./CN=*.smtp.a.cloudfilter.net" H="email-smtp.us-east-1.amazonaws.com"
2024-07-30 14:08:00 1sYg1a-00000006UBE-1Zcn ** supp...@akasohelp.zendesk.com
(c...@akasotech.com) <c...@akasotech.com> R=send_via_ses T=ses_forwarded_smtp
H=email-smtp.us-east-1.amazonaws.com [54.157.237.25]
X=TLS1.2:ECDHE-RSA-AES256-GCM-SHA384:256 CV=no: SMTP error from remote mail
server after end of data: 550 Yg1csiqBIcYJ2Yg1cshbVu -
<srs0=6b8c=o6=growthmatessagency.com=sim...@akasotech.com> message rejected
AUP#SNDR
2024-07-30 14:08:00 cwd=/var/spool/exim 7 args: /usr/sbin/exim -t -oem -oi -f
<> -E1sYg1a-00000006UBE-1Zcn
2024-07-30 14:08:00 1sYg1g-00000006UBm-0tRI <= <> R=1sYg1a-00000006UBE-1Zcn
U=mailnull P=local S=18990 T="Mail delivery failed: returning message to
sender" for sim...@growthmatessagency.com
2024-07-30 14:08:00 cwd=/var/spool/exim 3 args: /usr/sbin/exim -Mc
1sYg1g-00000006UBm-0tRI
2024-07-30 14:08:00 1sYg1a-00000006UBE-1Zcn Completed
2024-07-30 14:08:01 1sYg1g-00000006UBm-0tRI ** sim...@growthmatessagency.com
R=send_via_ses T=ses_smtp H=email-smtp.us-east-1.amazonaws.com [3.224.1.122]
X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=yes: SMTP error from remote mail server
after MAIL FROM:<>: 501 Invalid MAIL FROM address provided
Original sender:sim...@growthmatessagency.com
Recipient's email address:c...@akasotech.com
Forwarded address:supp...@akasohelp.zendesk.com
SRS rewrite address:sim...@akasotech.com
In the above log, if the forwarding fails, the return failure report needs to
be sent to the original sender sim...@growthmatessagency.com, which prompts
SMTP error from remote mail server after MAIL FROM:<>: 501 Invalid MAIL FROM
address provided
xqm2...@gmail.com
From: Jeremy Harris via Exim-users
Date: 2024-07-30 17:07
To: exim-users
Subject: [exim] Re: error 501 Invalid MAIL FROM address provided is reported
On 30/07/2024 07:40, xqm2018--- via Exim-users wrote:
> In the exim advanced configuration manager
I've no idea what that is...
> SRS rewriting the sender has been enabled, but when the automatic forwarding
> of emails fails> and needs to be returned to the original sender,
Do you mean "a bounce mail is generated and needs to be sent to the original
sender"?
> an error 501 Invalid MAIL FROM address provided is reported.
I infer that such a bounce is being rejected by the destination for the bounce,
which should be an MX for the original sender domain. Bounces have a null
envelope
sender (required by standards, and needed to prevent loops). The envelope
sender
is notified as part of the SMTP transaction using the MAIL verb.
> LOG: MAIN
> ** marc.wres...@googlemail.com R=send_via_ses T=ses_smtp
> H=email-smtp.us-east-1.amazonaws.com [52.206.145.59]
> X=TLS1.3:TLS_AES_256_GCM_SHA384:256 CV=yes: SMTP error from remote mail
> server after MAIL FROM:<>: 501 Invalid MAIL FROM address provided
The recipient of a message with a null envelope sender (presumably, this bounce)
has rejected it because (it claims) it does not like the envelope sender.
That is its problem, not yours. It will ignore, presumably, all such automatic
notifications of message-handling issues ("MDN" is the general term, "bounce"
the most common type and colloquial term) - and its overall message reliability
and ease of maintenance will be impacted as a result.
SRS is not involved in it's rejection of this message.
--
Cheers,
Jeremy
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
--
## subscription configuration (requires account):
## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-users-unsubscr...@lists.exim.org
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
