https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7805
--- Comment #9 from hnsupport <[email protected]> --- (In reply to hnsupport from comment #6) > (In reply to Giovanni Bechis from comment #3) > > Created attachment 5692 [details] > > fix unparseable relay > > > > I cannot reproduce the spf error, anyway the attached diff fixes the > > unparseable relay for me. > > I'll apply this patch and test, thanks. Spam detection software, running on the system "spamd-node0.wehostwebsites.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see [email protected] for details. Content preview: [email protected] te ha enviado archivos 1 elemento, 40 MB en total ・ Se eliminará el 9 de Abril de 2020 Enlace de descarga: https://wetransfer.com/downloads/058fc95d58f0d9a427265377a121cc5820200402172453/c6947aad5fc592c6b7b95bcfba3d17f220200402172455/943a2f Content analysis details: (6.3 points, 10.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: zendesk.com] -0.5 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 6.0 SPF_FAIL SPF: sender does not match SPF record (fail) [SPF failed: Please see http://www.openspf.org/Why?s=mfrom;id=noreply%40wetransfer.com;ip=10.30.65.95;r=spamd-node0.wehostwebsites.com] 0.0 SPF_HELO_FAIL SPF: HELO does not match SPF record (fail) [SPF failed: Please see http://www.openspf.org/Why?s=helo;id=wetransfer.com;ip=10.30.65.95;r=spamd-node0.wehostwebsites.com] 0.1 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 0.5 RDNS_NONE Delivered to internal network by a host with no rDNS 1.0 DMARC_QUAR No description available. -6.0 TRUSTED_BUT_SPAMMY_DOMAINS No description available. 2.0 DKIM_INVALID DKIM or DK signature exists, but is not valid 3.3 TXREP TXREP: Score normalizing based on sender's reputation Confirmed resolution of unparseable relay on my end. SPF issue still persists. Since none of you can reproduce it in your respective environments with the redacted test case, I've included both an unredacted test case (the message, post-delivery) and my own debug output with that test case for further reference. I provided my version of Mail::SPF and Mail::SpamAssassin, and confirmed both are the latest stable versions, already, so it's nothing immediately obvious to me. If anyone else can't reproduce the issue, I'd appreciate if you could include your full debug output for my reference. If it's an environmental difference, that will quantify it well. -- You are receiving this mail because: You are the assignee for the bug.
