[zaza24]

re
encore merci pour la précision de la réponse et le nombre de solutions posssibles même si elles ne m'agréent pas
à quoi correspond la solution google apps ?
Enfin pour ce qui concerne un serveur dédié, est ce que un KIMSUFFI peut remplacer un 90 PLAN car les tarifs des autres serveurs dédiés m'ennuient un peu car cela fait cher pour juste contrer ce problème
Enfin, connaitriez vous un prestataire (free lance ou auto entreprenneur par ex. ) pouvant assurer la migration (le site est un site Joomla) puis éventuellement l'entretien
Merci encore

[fritz2cat]

Les comptes Exchange OVH ne sont pas une solution. En effet les mails entrants arrivent toujours par les mêmes serveurs mx0, mx1, mx2, mx3, mxb.ovh.net.

Il n'y a pas d'autre solution que d'employer un autre service de mail à l'envoi ou bien à la réception.

Tu peux ouvrir un compte Gmail qui retransfère tout vers une de tes adresses hébergées chez OVH et dire à tes américains d'envoyer les mails vers Gmail. C'est sûr que ça fonctionnera.

Si ça ne te convient pas, et que tes correspondants américains ne veulent pas changer de prestataire, alors c'est toi qui dois chercher une autre crèmerie ou bien t'asseoir et pleurer.

Une solution serait un serveur dédié mais ça demande la compétence d'administrer un serveur Linux.

Une solution serait d'utiliser Google Apps au lieu du mutualisé OVH.

Une solution serait de passer par un prestataire qui filtre les spams et renvoie tout le reste vers ton compte OVH.

Bref, c'est toi qui vois.

Frédéric

[zaza24]

Bonjour Mr FREDERIC
mais je n'ais toujours pas de solution et cela fait plusieurs mois que cela dure
un technicien de OVH m'avait parlé d'un compte microsoft exchange qui pourrait résoudre le problème
Sinon, OVH m'avait fait changer de serveurs (mxo oumxb etc...) mais cela n'avait rien changé...
Enfin changer d'offre chez OVH ne changerait rien
Merci

[fritz2cat]

Securence a l'air de travailler correctement au niveau de ses DNS: le reverse correspond au forward.

# host 216.17.63.160
160.63.17.216.in-addr.arpa domain name pointer mail026.160.63.A.static.mtka.securence.com.

# host mail026.160.63.A.static.mtka.securence.com
mail026.160.63.A.static.mtka.securence.com has address 216.17.63.160

Maintenant je dois admettre que c'est une *Mauvaise Idée* ™ de donner un nom pareil à un mailhost avec 6 niveaux de sous-domaines en-dessous de securence.com.
Il n'y a rien de tel que ça pour faire croire que la connexion émane du pc-de-la-mémé-à-la-maison.
Qu'il y ait static, dynamic, dsl, xdsl, cable ou mobile dans le nom n'a pas grande importance. Ils auraient mieux fait de l'appeler mail-out-26.securence.com.


Frédéric

[zaza24]

Bonjour frédéric et merci de vous intéresser à mon cas !
Effectivement, pour ce qui concerne le protocole SMTP c'est exactement ce que m'a répondu le support OVH en deùandant à ce que les américains augmentent leur SMTP à au moins deux minutes et que cela résoudrait le problème.
malheureusement il semble que notre fournisseur n'ait pas réussi à faire changer cette régle...

Pour info voilà ce que répond dernièrement le provider de mon fournisseur :
"Your domain has a static IP can they just allow connections from 216.17.54.139 without doing this spam check that is causing the problem? Blocking because the word static wouldn’t be recommended"

En effet car OVH m'a expliqué que le serveur d'ou provenait les mails contenait le mot STATIC et que ce mot était banni car de nombreux envoyeurs de SPAM utilisait des serveurs avec le mot STATIC d'ou ces règles de filtrations.

voici une autre réponse signifiant que c'est pas de leur faute

Hello Tom,
You should have received an email stating that This is not an issue with any of the timeouts. The customers mail server is using a throttling filter that is stating that we are connecting to their server to deliver mail to frequently. They will need to adjust this threshold to prevent false positives from occurring. Our servers will automatically retry delivery several more times before failing to deliver the message. Please let us know if you have any further questions.

Thank you

Edward

US Internet Corp

Enfin la copie d'un email avec des logs...

Our connection timeout is two minutes. Our read banner timeout is 30 seconds.

There are some read banner timeouts, but this isn't the problem. When we do get a response from the server it says "453 no more connections allowed from this ip at this time, please try again later"

The receiving server is throttling the incoming mail from Securence.

Here is an adjusted log trace the shows just a single thread more clearly:
2012-03-13 07:51:07 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:51:07 connection opened
2012-03-13 07:51:37 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:51:37 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:51:37 >> QUIT
2012-03-13 07:51:37 got end of stream...
2012-03-13 07:51:37 closing connection...
2012-03-13 07:51:37 ...connection closed



We can internally throttle the delivery, but it's better if we know more accurately how they are throttling. Unfortunately, this solution will delay delivery of messages whatever their throttling limit is. They appear to have a very aggressive limit so we may never be able to work through the entire queue or mail.

The best solution is for the receiving server to disable throttling. As you can see below, we tried many times to deliver the message and got the "...no more connections..." response 10 times. Can the people at epanalyse.com adjust their settings?


This appears to be a recurring issue with the mail provider at ovh.net:
http://forum.ovh.com/showthread.php?t=58194
http://forum.kimsufi.com/showthread.php?t=7133


Below is our delivery attempts and rejections from the receiving server for this message:

2012-03-13 07:51:06 attempt lateral from sniper #20 to 192.168.227.26:25
2012-03-13 07:51:06 << 220 mta26.mtka.securence.com ESMTP ready
2012-03-13 07:51:06 >> xlat 20 1331643063161-020-00480636
2012-03-13 07:51:06 << 250 OK for XLAT 20
2012-03-13 07:51:06 >> data
2012-03-13 07:51:06 << 354 End data with .
2012-03-13 07:51:06 sending data...
2012-03-13 07:51:06 ...data sent
2012-03-13 07:51:06 >> .
2012-03-13 07:51:06 << 250 OK, queued as EB21B2D0F30501408A72A2A0815669980AC0...usinternet.com
2012-03-13 07:51:06 >> quit
2012-03-13 07:51:06 << 221 Bye
2012-03-13 07:51:06 lateral OK to ServerNumber:26 Bound IP:216.17.63.160 Outside IP:216.17.63.160 RBL weight:0 rblDestDomains:[]
2012-03-13 07:51:07 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 07:51:07 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:51:07 connection opened
2012-03-13 07:51:37 closing connection...
2012-03-13 07:51:37 ...connection closed
2012-03-13 07:51:37 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 07:51:37 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:51:37 connection opened
2012-03-13 07:51:37 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:51:37 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:51:37 >> QUIT
2012-03-13 07:51:37 got end of stream...
2012-03-13 07:51:37 closing connection...
2012-03-13 07:51:37 ...connection closed
2012-03-13 07:53:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 07:53:09 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:53:09 connection opened
2012-03-13 07:53:39 closing connection...
2012-03-13 07:53:39 ...connection closed
2012-03-13 07:53:39 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 07:53:39 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:53:40 connection opened
2012-03-13 07:53:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:53:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:53:40 >> QUIT
2012-03-13 07:53:40 got end of stream...
2012-03-13 07:53:40 closing connection...
2012-03-13 07:53:40 ...connection closed
2012-03-13 07:56:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 07:56:09 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:56:09 connection opened
2012-03-13 07:56:39 closing connection...
2012-03-13 07:56:39 ...connection closed
2012-03-13 07:56:39 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 07:56:39 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 07:56:39 connection opened
2012-03-13 07:56:39 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:56:39 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 07:56:39 >> QUIT
2012-03-13 07:56:39 got end of stream...
2012-03-13 07:56:39 closing connection...
2012-03-13 07:56:39 ...connection closed
2012-03-13 08:01:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 08:01:09 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:01:10 connection opened
2012-03-13 08:01:40 closing connection...
2012-03-13 08:01:40 ...connection closed
2012-03-13 08:01:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 08:01:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:01:40 connection opened
2012-03-13 08:01:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:01:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:01:40 >> QUIT
2012-03-13 08:01:40 got end of stream...
2012-03-13 08:01:40 closing connection...
2012-03-13 08:01:40 ...connection closed
2012-03-13 08:09:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 08:09:09 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:09:10 connection opened
2012-03-13 08:09:40 closing connection...
2012-03-13 08:09:40 ...connection closed
2012-03-13 08:09:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 08:09:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:09:40 connection opened
2012-03-13 08:09:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:09:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:09:40 >> QUIT
2012-03-13 08:09:40 got end of stream...
2012-03-13 08:09:40 closing connection...
2012-03-13 08:09:40 ...connection closed
2012-03-13 08:23:10 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 08:23:10 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:23:10 connection opened
2012-03-13 08:23:40 closing connection...
2012-03-13 08:23:40 ...connection closed
2012-03-13 08:23:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 08:23:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:23:40 connection opened
2012-03-13 08:23:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:23:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 08:23:40 >> QUIT
2012-03-13 08:23:40 got end of stream...
2012-03-13 08:23:40 closing connection...
2012-03-13 08:23:40 ...connection closed
2012-03-13 08:49:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 08:49:10 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:49:10 connection opened
2012-03-13 08:49:40 closing connection...
2012-03-13 08:49:40 ...connection closed
2012-03-13 08:49:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 08:49:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 08:50:01 closing connection...
2012-03-13 08:50:01 ...connection closed
2012-03-13 08:50:01 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: Connection refused to mxb.ovh.net:25 from 216.17.63.160. Connection timed out
2012-03-13 09:37:10 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 09:37:10 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 09:37:10 connection opened
2012-03-13 09:37:40 closing connection...
2012-03-13 09:37:40 ...connection closed
2012-03-13 09:37:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 09:37:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 09:37:40 connection opened
2012-03-13 09:37:41 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 09:37:41 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 09:37:41 >> QUIT
2012-03-13 09:37:41 got end of stream...
2012-03-13 09:37:41 closing connection...
2012-03-13 09:37:41 ...connection closed
2012-03-13 11:07:10 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 11:07:10 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 11:07:10 connection opened
2012-03-13 11:07:40 closing connection...
2012-03-13 11:07:40 ...connection closed
2012-03-13 11:07:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 11:07:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 11:07:40 connection opened
2012-03-13 11:07:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 11:07:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 11:07:40 >> QUIT
2012-03-13 11:07:40 got end of stream...
2012-03-13 11:07:40 closing connection...
2012-03-13 11:07:40 ...connection closed
2012-03-13 13:58:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 13:58:10 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 13:58:10 connection opened
2012-03-13 13:58:40 closing connection...
2012-03-13 13:58:40 ...connection closed
2012-03-13 13:58:40 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 13:58:40 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 13:59:01 closing connection...
2012-03-13 13:59:01 ...connection closed
2012-03-13 13:59:01 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: Connection refused to mxb.ovh.net:25 from 216.17.63.160. Connection timed out
2012-03-13 19:22:09 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-13 19:22:09 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 19:22:09 connection opened
2012-03-13 19:22:39 closing connection...
2012-03-13 19:22:39 ...connection closed
2012-03-13 19:22:39 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-13 19:22:39 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-13 19:22:39 connection opened
2012-03-13 19:22:40 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 19:22:40 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-13 19:22:40 >> QUIT
2012-03-13 19:22:40 got end of stream...
2012-03-13 19:22:40 closing connection...
2012-03-13 19:22:40 ...connection closed
2012-03-14 05:36:33 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-14 05:36:33 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-14 05:36:33 connection opened
2012-03-14 05:37:03 closing connection...
2012-03-14 05:37:03 ...connection closed
2012-03-14 05:37:03 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-14 05:37:03 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-14 05:37:24 closing connection...
2012-03-14 05:37:24 ...connection closed
2012-03-14 05:37:24 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: Connection refused to mxb.ovh.net:25 from 216.17.63.160. Connection timed out
2012-03-15 01:02:34 ## DELIVERY ATTEMPT FROM SERVER 26
2012-03-15 01:02:34 opening connection to mx0.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-15 01:02:34 connection opened
2012-03-15 01:03:04 closing connection...
2012-03-15 01:03:04 ...connection closed
2012-03-15 01:03:04 failed delivery to mx0.ovh.net:25 from 216.17.63.160, reason: Timed out while connecting to mx0.ovh.net:25 from 216.17.63.160
2012-03-15 01:03:04 opening connection to mxb.ovh.net:25 from local IP 216.17.63.160 (0)
2012-03-15 01:03:04 connection opened
2012-03-15 01:03:05 << 453 no more connections allowed from this ip at this time, please try again later
2012-03-15 01:03:05 failed delivery to mxb.ovh.net:25 from 216.17.63.160, reason: bad banner from server: 453 no more connections allowed from this ip at this time, please try again later
2012-03-15 01:03:05 >> QUIT
2012-03-15 01:03:05 got end of stream...
2012-03-15 01:03:05 closing connection...
2012-03-15 01:03:05 ...connection closed

Merci pour votre aide & votre patience
Zaza

[fritz2cat]

houlà c'est un très vieux problème qui refait surface.
Quand OVH reçoit un mail depuis un serveur mal configuré au niveau DNS (reverse inexistent ou incorrect), OVH freine la conversation.

Ceci est un acte délibéré pour limiter le flot de messages quand la provenance est suspecte.

D'un autre côté le fournisseur US devrait respecter les recommandations du protocole SMTP et notamment des timeouts de l'ordre de 5 minutes.

Dans ce combat, tu es le pot de terre face à deux pots de fer.

L'un comme l'autre vont te dire qu'ils ont raison parce qu'ils peuvent parler avec le reste du monde ...

Peux-tu poster (par exemple sur pastebin.com) les en-têtes d'un message que tu as reçu de ce contact américain ? Tu peux gommer (mais pas trop) les informations sensibles (juste les e-mails)

Frédéric

[zaza24]

Bonjour
Notre site est hébergé en mutualisé chez OVH depuis plusieurs années et tout se passe bien.
un fournisseur US à changé début 2012 de "mail provider" et depuis je ne reçois plus leurs emails...(j'utilise outlook 2010)
J'ai contacté le support d'OVH qui m'indique que c'est parce que ce fameux mail provider (je résume) utilise un TIME OUT trop court (30 sec ou 1 minute) et qu'en le mettant à 2 minutes, cela résoudrait le prob...
Mon fournisseur ne semble pas être en mesure de pouvoir faire changer son fournisseur (hébergeur) aussi je souhaiterais savoir s'il y avait une autre possibilité pour moi de modifier (via notre site par ex. ou en changeant de serveur ou type d'hébergement )
Merci de votre aide et pardon peut être du manque de détails mais je peux fournir tout renseignement pouvant vous éclairer.
Merci par avance
Zaza