Bonjour,
Je viens d’installer em-client sur un smartphone Android. Toutes les boîtes, (sauf une) se sont facilement installées avec le QR code qui est top !
Le nom de domaine de celle-ci est
pro1.mail.ovh.net
Pourriez-vous voir si il vous es possible de faire quelque-chose pour ce nom de domaine car je voudrais pouvoir utiliser em-client sur Android comme je le fais sur mon pc.
Bien cordialement,
Éric GIRONNAY
Bonjour Breizhspirit
Est-ce que les autres nom de domain sont de forme abc.def.xxx (3 parties et no 4?)
So the issue is for em client to handle domain names with 4 parts, “pro1.mail.ovh.net” (with 3 periods as separators), instead of the more usual 3 parts like “imap.gmail.com” (with 2 periods as separators)?
Bonjour Tony,
Je vous es envoyé un mail mais c’est peut-être ici que je devais faire ma réponse.
C’est exactement ce que vous expliquez.
La boite mail avec 3 points ne fonctionne pas alors que les boites mail avec 2 points fonctionnent très bien.
Pouvez-vous résoudre ce problème, merci.
Bien cordialement,
Éric
I just installed em-client on an Android smartphone. All the boxes (except one) were easily installed with the QR code which is great!
The domain name of this one is
pro1.mail.ovh.net
Could you see if you can do something for this domain name because I would like to be able to use em-client on Android as I do on my PC.
eM Client mobile app accounts can be setup exactly the same as the desktop. I’m not aware of any known issues with the mobile apps with 4 part mail server names compared to 3 part.
Click “Menu / Settings”. Then open your mail account and press on “Services” at the bottom. Then enter the same Server address, Port & Security policy as eM Client for desktop and enter any username and password if you require that too (if it’s not an OAuth type account).
Ps I can definitely enter the server address pro1.mail.ovh.net with no errors in the eM Client Droid mobile app, so I can only presume that you might have an eg: incorrect Port or Security policy or maybe might need an App Password if the account doesn’t use an OAuth token login.
(Example IMAP account Server address)
When you go to check mail, what errors are you getting when you try to check mail ? If you don’t see an error, click “Menu / Settings / Show Operations” in the app and jot down any obvious errors in this thread. Blank out anything personal
Hi Cyberzork,
Firstly, many thanks for this all explanations.
I make the transfert by QR code from my pc the first time and he not run. I make in a second time manually with the same identification that my pc and he not run. But when I make a synchrone a have the error auth noauth but I don’t know what is the signification.
You can see in attached file.
Many thanks for your help.
Regards,
Éric
when I make a synchrone a have the error auth noauth but I don’t know what is the signification.
Ok as you have tried the automatic QR setup and also tried the manual setup and getting that error “net_auth_noauth”, could be it wants maybe an eg: app password instead of your normal email password.
Did you have to use an app password for eM Client for desktop when you set that up before ?
Also do you have the same Port and Security Policy in your Droid mobile setup as in my example screenshot in my previous post ?
Encore une fois, un grand merci pour votre aide Cyberzork 
.
Et non je n’ai pas eu à entrer de mot de passe sur mes pc’s. Seulement le mot de passe de ma boîte mail.
Je suis allé voir les recommandations de OVH pour la configuration d’un smartphone Android et j’ai vu que pour la sécurité smtp je devais choisir startTls.
Or il n’y a pas d’option startTls dans em-client. Pensez-vous que cela soit un problème ? Encore merci pour toute votre aide.
Bien cordialement,
Éric
I went to see the OVH recommendations for configuring an Android smartphone and I saw that for smtp security I had to choose startTls.
However there is no startTls option in em-client. Do you think this is a problem?
No thats not the problem. eM Client already supports StartTls
Ok use the same IMAP and SMTP settings as eM Client for desktop, but you also need some “additional Text in the Diagnostics Tabs” in the mobile IMAP account for OVH accounts.
See @Gary post below in the following thread.
Also see @Phil_LP post also in the following thread,
So “try the following in the mobile app” and see if that then allows you to receive and send mail "with the same eM Client desktop IMAP and SMTP Tab server settings and same User / Pass.
Note:- We haven’t tested that previously with the mobile app & an OVH account (only with the desktop V10 client) so don’t know if that will work the same. Hopefully it does.
Go to the Mobile app “Menu / Settings / Accounts”
Then “Open your account” and press “Advanced” under “Preferences”
Then type in the “Advanced parameters” line at the bottom the following:-
Either
Or
Et bien je viens d’atterrir à l’instant et je vois beaucoup de réponses avec dont une qui est peu être la solution. Je vais donc tester cela et je reviendrai vers vous pour donner le résultat. Dans tous les les cas je m’attendais pas à avoir autant d’aide, alors je remercie encore tous ceux qui m’ont aidés.
Cordialement,
Éric
Bonjour à tous,
Me revoilà avec des nouvelles positives.
Après avoir entré:
–force-imap-auth PLAIN --force-smtp-auth PLAIN
J’ai maintenant je reçois maintenant mes e-mails. Merci beaucoup Cyberzork.
Maintenant il reste le smtp qui continu de se mettre en erreur.
Mais je dois dire que le plus important pour moi c’est la réception.
Donc, si vous avez encore une idée, je serais content de la tester mais je suis déjà très content de recevoir mes mails.
J’ai écrit mot pour mot ce que vous avez écris. Peut être que je dois écrire mon mot de passe à la place du mot LOGIN ?
J’ai essayé mais cela n’a rien changé.
Bien cordialement,
Éric
Hello everyone,
Here I am again with positive news.
After entering:
–force-imap-auth PLAIN --force-smtp-auth PLAIN
I now receive my emails. Thank you very much Cyberzork.
Now the smtp remains which continues to error.
Great you can now receive mail in the mob app.
In the “SMTP part of the parameter” try just changing the name PLAIN to LOGIN and see if that then sends.
Also set the SMTP server tab username and password to “use the same as the Incoming” rather than typing the username and password, (if it’s no set to that already) and see if that sends.
Failing that, try “removing the
-force-smtp-auth PLAIN” part in the advanced parameter, “as you may not need that at all to send mail”. Then see if it sends.
Now if none of the above makes no difference , update what your, SMTP server address, port and security policy is just incase there is a wrong SMTP tab setting in the mob app.
Rebonjour Cyberzork,
Malheureusement j’ai essayé tout ce que vous m’avez proposé de faire mais sans succès. Maintenant il y a des choses que je n’ai pas comprises, ce qui expliquerai que ça ne fonctionne pas.
Dans tous les cas je tiens OVH pour responsable car je pense qu’il pourrait proposer un nom de domaine en 3 parties et non en 4. Pour un néophyte comme moi, je n’arrive pas à comprendre toutes ces incompatibilités. Ainsi va l’informatique.
Je vous remercie encore une fois pour toute votre aide Cyberzork.
Bien cordialement,
Éric
Par exemple, je peux dire que je n’ai pas compris cette phrase:
Dans la « partie SMTP du paramètre », essayez simplement de changer le nom PLAIN en LOGIN et voyez si cela envoie.
Unfortunately I tried everything you suggested I do but without success.
In any case I hold OVH responsible because I think they could offer a domain name in 3 parts and not 4.
Yes it is an OVH server problem where “they need updating their end” to support new authentication methods so you don’t have to force plain text strings to get your login to work.
I don’t believe it’s anything to do with the domain name server being in 4 parts “as your incoming mail does work with the plain text string added”.
I can say that I didn’t understand this sentence:
In the “SMTP part of the parameter”, just try changing the name PLAIN to LOGIN and see if it sends.
I meant in the first screenshot example which had the word PLAIN “at the end for the SMTP part” , change that word to LOGIN to try instead as in the below example.
At a guess, the word LOGIN in the SMTP parameter could just mean to eg: use your username and password in the SMTP Tab.
I would have thought though that SMTP with the word PLAIN would have worked being that means “it sends your username and password in PLAIN text” which OVH servers normally want.
However if changing the SMTP parameter part at the end of the string to the word LOGIN also doesn’t work, then you will probably need to try the next mobile app update which hopefully won’t be far away from reading the forum threads.
In the meantime update what your mobile app SMTP Tab "Server address, Server port & Security policy is so we can also check those as well.