public inbox for [email protected]
 help / color / mirror / Atom feed
From: Julien Ducarroz<[email protected]>
To: [email protected]
Subject: Purchase Order - New Customer
Date: 13 Jan 2025 09:04:17 +0100	[thread overview]
Message-ID: <[email protected]> (raw)

[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]

Spam detection software, running on the system "server-vie001.gnuweeb.org",
has identified this incoming email as possible 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
@@CONTACT_ADDRESS@@ for details.

Content preview:  Dear Supplier, Happy new year. I am interested in your product.
   We have gone through your site/catalog samples. However here is more detailed
   information which includes order quantity, packing requirement, and clea
  [...] 

Content analysis details:   (7.9 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 RCVD_IN_DNSWL_BLOCKED  RBL: ADMINISTRATOR NOTICE: The query to
                            DNSWL was blocked.  See
                            http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
                             for more information.
                            [23.94.82.43 listed in list.dnswl.org]
 1.0 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
 0.1 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts
 0.0 HTML_MESSAGE           BODY: HTML included in message
 3.6 RCVD_IN_SBL_CSS        RBL: Received via a relay in Spamhaus SBL-CSS
                            [23.94.82.43 listed in zen.spamhaus.org]
 0.0 URIBL_ZEN_BLOCKED_OPENDNS ADMINISTRATOR NOTICE: The query to
                            zen.spamhaus.org was blocked due to usage
                            of an open resolver. See
                            https://www.spamhaus.org/returnc/pub/
                            [URIs: pages.dev]
 1.3 RDNS_NONE              Delivered to internal network by a host with no rDNS
 1.0 TO_NO_BRKTS_FROM_MSSP  Multiple header formatting problems
 1.0 TO_NO_BRKTS_NORDNS_HTML To: lacks brackets and no rDNS and HTML
                            only

The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam.  If you wish to view
it, it may be safer to save it to a file and open it with an editor.


[-- Attachment #2: original message before SpamAssassin --]
[-- Type: message/rfc822, Size: 12891 bytes --]

[-- Attachment #2.1: Type: text/html, Size: 11823 bytes --]

From: Julien Ducarroz<[email protected]>
To: [email protected]
Subject: Purchase Order - New Customer
Date: 13 Jan 2025 09:04:17 +0100
Message-ID: <[email protected]>

                 reply	other threads:[~2025-01-13  8:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    [email protected] \
    [email protected] \
    [email protected] \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox