Mail classé en SPAM

damdams
Messages : 3
Enregistré le : mar. 6 nov. 2018 12:16

Mail classé en SPAM

Messagepar damdams » mar. 6 nov. 2018 12:47

Bonjour,

Utilisateur de récent de la messagerie Zaclys, je remarque depuis un moins d'une semaine tout les mails que je peux envoyer depuis mon adresse mail Zaclys sont systématiquement détectés comme spam chez mes destinataires, aussi bien via le webmail, K9Mail ou Thunderbird. Alors que mes destinataires recevaient correctement mes mails auparavant

Pourtant j'ai bien suivis les procédures ci-dessous et mes destinataire recevait bien mes mails auparavant.
https://wiki.zaclys.com/index.php/Confi ... _des_alias
https://wiki.zaclys.com/index.php/Confi ... %A9ception)

Suite à ce sujet sur votre forum : viewtopic.php?t=3128

Voici le résultat d'un envoi de mail à check-auth@verifier.port25.com

Code : Tout sélectionner

This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com.  The service allows email senders to perform
a simple check of various sender authentication mechanisms.  It is provided
free of charge, in the hope that it is useful to the email community.  While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check:          pass
"iprev" check:      pass
DKIM check:         pass
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname:  mail.zaclys.net
Source IP:      178.33.93.72
mail-from:      damien.caroff@zaclys.net

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=damien.caroff@zaclys.net

DNS record(s):
    zaclys.net. 60 IN TXT "v=spf1 a mx ip4:5.196.114.145 ip4:188.165.53.39 ip4:178.33.93.72 ip4:5.196.58.138 ip4:178.33.225.24  ~all"
    zaclys.net. 60 IN A 178.33.93.72


----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result:         pass (matches mail.zaclys.net)
ID(s) verified: policy.iprev=178.33.93.72

DNS record(s):
    72.93.33.178.in-addr.arpa. 60 IN PTR mail.zaclys.net.
    mail.zaclys.net. 60 IN A 178.33.93.72


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: damien.caroff@zaclys.net)
ID(s) verified: header.d=zaclys.net

Canonicalized Headers:
    date:Tue,'20'06'20'Nov'20'2018'20'12:23:09'20'+0100'0D''0A'
    from:Damien'20'CAROFF'20'<damien.caroff@zaclys.net>'0D''0A'
    to:check-auth@verifier.port25.com'0D''0A'
    subject:test'0D''0A'
    reply-to:damien.caroff@zaclys.net'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/relaxed;'20'd=zaclys.net;'20's=default;'20't=1541503389;'20'bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=;'20'h=Date:From:To:Subject:Reply-To:From;'20'b=

Canonicalized Body:

DNS record(s):
    default._domainkey.zaclys.net. 60 IN TXT "k=rsa; s=email; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC1fnkjRGPdultocbqJxEVNOq0Z4I42WLvjNHmyxb3Jw1E1Yf/9O4RcDGXysOOCnXg+3vRiz5cyh14/zBXxSD+96hDEwSLV7L06tFjT35w2g+v9mJ7Wb6zSFf34L7vTM77gzOHc3fVszNYUwejrqPiHZZruzj3H1XSM9GLPCRLUfQIDAQAB"

Public key used for verification: default._domainkey.zaclys.net (1024 bits)

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.4.0 (2014-02-07)

Result:         ham (-2.0 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0002]
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
                            trust
                            [178.33.93.72 listed in list.dnswl.org]
-0.0 SPF_PASS               SPF: sender matches SPF record
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
                            domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
 0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid



==============================================================
Explanation of the possible results (based on RFCs 7601, 7208)
==============================================================


DKIM Results
============

none:  The message was not signed.

pass:  The message was signed, the signature or signatures were
    acceptable to the ADMD, and the signature(s) passed verification
    tests.

fail:  The message was signed and the signature or signatures were
    acceptable to the ADMD, but they failed the verification test(s).

policy:  The message was signed, but some aspect of the signature or
    signatures was not acceptable to the ADMD.

neutral:  The message was signed, but the signature or signatures
    contained syntax errors or were not otherwise able to be
    processed.  This result is also used for other failures not
    covered elsewhere in this list.

temperror:  The message could not be verified due to some error that
    is likely transient in nature, such as a temporary inability to
    retrieve a public key.  A later attempt may produce a final
    result.

permerror:  The message could not be verified due to some error that
    is unrecoverable, such as a required header field being absent.  A
    later attempt is unlikely to produce a final result.


SPF Results
===========

none:  Either (a) no syntactically valid DNS domain name was extracted from
    the SMTP session that could be used as the one to be authorized, or
    (b) no SPF records were retrieved from the DNS.

neutral:  The ADMD has explicitly stated that it is not asserting whether
    the IP address is authorized.

pass:  An explicit statement that the client is authorized to inject mail
    with the given identity.

fail:  An explicit statement that the client is not authorized to use the
    domain in the given identity.

softfail:  A weak statement by the publishing ADMD that the host is probably
    not authorized.  It has not published a stronger, more definitive policy
    that results in a "fail".

temperror:  The SPF verifier encountered a transient (generally DNS) error
    while performing the check.  A later retry may succeed without further
    DNS operator action.

permerror: The domain's published records could not be correctly interpreted.
    This signals an error condition that definitely requires DNS operator
    intervention to be resolved.


"iprev" Results
===============

pass:  The DNS evaluation succeeded, i.e., the "reverse" and
    "forward" lookup results were returned and were in agreement.

fail:  The DNS evaluation failed.  In particular, the "reverse" and
    "forward" lookups each produced results, but they were not in
    agreement, or the "forward" query completed but produced no
    result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an
    RCODE of 0 (NOERROR) in a reply containing no answers, was
    returned.

temperror:  The DNS evaluation could not be completed due to some
    error that is likely transient in nature, such as a temporary DNS
    error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or
    other error condition resulted.  A later attempt may produce a
    final result.

permerror:  The DNS evaluation could not be completed because no PTR
    data are published for the connecting IP address, e.g., a DNS
    RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR)
    in a reply containing no answers, was returned.  This prevented
    completion of the evaluation.  A later attempt is unlikely to
    produce a final result.




==========================================================
Original Email
==========================================================

Return-Path: <damien.caroff@zaclys.net>
Received: from mail.zaclys.net (178.33.93.72) by verifier.port25.com id hs5sq02e8s4i for <check-auth@verifier.port25.com>; Tue, 6 Nov 2018 11:23:12 +0000 (envelope-from <damien.caroff@zaclys.net>)
Authentication-Results: verifier.port25.com; spf=pass  smtp.mailfrom=damien.caroff@zaclys.net;
 iprev=pass (matches mail.zaclys.net)  policy.iprev=178.33.93.72;
 dkim=pass (matches From: damien.caroff@zaclys.net)  header.d=zaclys.net
Received: from webmail.zaclys.net (webmail.zaclys.net [5.196.58.138])
    (authenticated bits=0)
    by mail.zaclys.net (8.14.7/8.14.7) with ESMTP id wA6BN9Yg048547
    for <check-auth@verifier.port25.com>; Tue, 6 Nov 2018 12:23:09 +0100
DMARC-Filter: OpenDMARC Filter v1.3.2 mail.zaclys.net wA6BN9Yg048547
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zaclys.net;
    s=default; t=1541503389;
    bh=47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=;
    h=Date:From:To:Subject:Reply-To:From;
    b=mE2JpLwubxEimyYuby8sOKZ9RHklwLXVMe0m0uDGDz9lbQ9w83j+sNZby+iZxsmxL
     4zChJuzbeMQQNd3PVgnZqaPY8p5y1IifwJiixwz01GBT5fECVMbNxhoKNwCBRv+CGu
     5x6fRt4UoZOuYAUV4bat4ds0OI5WHvKdMzMC+K0k=
MIME-Version: 1.0
Date: Tue, 06 Nov 2018 12:23:09 +0100
From: Damien CAROFF <damien.caroff@zaclys.net>
To: check-auth@verifier.port25.com
Subject: test
Reply-To: damien.caroff@zaclys.net
Mail-Reply-To: damien.caroff@zaclys.net
Message-ID: <132798a87cb30cb839bddc89bc8902ac@zaclys.net>
X-Sender: damien.caroff@zaclys.net
User-Agent: Roundcube Webmail/1.3.6


Pouvez-vous m'aider svp ?

damdams
Messages : 3
Enregistré le : mar. 6 nov. 2018 12:16

Re: Mail classé en SPAM

Messagepar damdams » jeu. 8 nov. 2018 23:51

Bonsoir,

Le problème est toujours persistant. Quelqu'un a t-il le même problème que moi ?

Aurai-je loupé une configuration ?

Merci d'avance pour votre aide.

MatthieuBarbu
L'équipe Zaclys
Messages : 70
Enregistré le : mar. 13 juin 2017 11:06

Re: Mail classé en SPAM

Messagepar MatthieuBarbu » ven. 9 nov. 2018 13:48

Bonjour,

le problème ne vient pas de votre config...

Il y a eu récemment le piratage d'une vielle boite mail de test qui a servit à envoyer plus 1 million de mails frauduleux.

La boite mail a été supprimée ainsi que les mails frauduleux qui étaient encore en cours d'envoi mais la réputation de notre serveur en a pris un sacré coup :(

Nous nous efforçons actuellement de réglé ce problème, les choses devraient rentrer dans l'ordre dans peu de temps...

Pourriez-vous nous indiquer, svp, la liste des serveurs mails (serveurs uniquement pas vos contacts, gmail.com ou yahoo.fr par exemple) classant automatiquement nos mails comme spam, cela pourrait nous aider à la résolution du problème?

Désolé pour le désagrément mais ce n'est pas toujours facile de convaincre google ou autres que nous sommes de bonne foi, que nous ne sommes pas un serveur de spammeur et que nous chassons sérieusement ce genre de pratique.
Membre de l’Équipe Zaclys
https://www.zaclys.com

Sur https://mastodon.zaclys.com
@MatthieuBarbu

damdams
Messages : 3
Enregistré le : mar. 6 nov. 2018 12:16

Re: Mail classé en SPAM

Messagepar damdams » mar. 13 nov. 2018 08:19

Bonjour,

Désolé pour le temps de réponse..

Concernant les serveurs mails, il s'agit principale de gmail.com et orange.fr. Mais cela semble être maintenant rétabli pour gmail.

Merci encore pour votre aide ;)


Retourner vers « Utilisation »

Qui est en ligne

Utilisateurs parcourant ce forum : Aucun utilisateur enregistré et 0 invité