FAQ.OnlineUI.txt 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300
  1. #!/bin/cat
  2. $Id: FAQ.OnlineUI.txt,v 1.36 2022/09/14 11:18:05 gilles Exp gilles $
  3. This document is also available online at
  4. https://imapsync.lamiral.info/FAQ.d/
  5. https://imapsync.lamiral.info/FAQ.d/FAQ.OnlineUI.txt
  6. =====================================================================
  7. Imapsync tips about the online visual user interfaces
  8. https://imapsync.lamiral.info/X/
  9. =====================================================================
  10. Questions answered in this FAQ are:
  11. Q. Can I launch several imap synchronizations on the visual
  12. user interface /X?
  13. Q. How secure is the online visual user interface /X?
  14. Q. Does the online service store any sensitive information
  15. like my passwords?
  16. Q. I want to switch from the visual interface /X to the
  17. imapsync command line or to the script examples
  18. https://imapsync.lamiral.info/#DOC_BASIC
  19. What should I know?
  20. Q. Shall I have issues when the browser times out?
  21. What happens if the browser connection is closed for whatever reason?
  22. Q. Shall I have issues when the webserver times out? What happens
  23. if the web server closes the connection for whatever reason?
  24. Q. The sync stalls at the beginning, just after a line like:
  25. "Host1: xxx says it has CAPABILITY for AUTHENTICATE LOGIN"
  26. What is the problem?
  27. Q. The synchronization fails with the error message like:
  28. Err 1/1: Host1 failure: Error login on [10.1.161.155] with user [webmaster@truc.com] auth [LOGIN]: 2 NO [ALERT] LOGIN DENIED -- COUNTRY IS BLACKLISTED
  29. Now the questions again with their answers.
  30. =====================================================================
  31. Q. Can I launch several imap synchronizations on the visual
  32. user interface /X?
  33. A. Yes. Open several tabs/windows on your browser and fill each one
  34. with different credentials.
  35. =====================================================================
  36. Q. How secure is the online visual user interface /X?
  37. A0. Well, I don't know if asking the provider whether his online
  38. service is secure or not would be of any interest.
  39. Let's do it anyway, you'll be the judge.
  40. A1. Some figures
  41. Date of this report: 24 December 2021. Happy Christmas!
  42. The online imapsync service /X started 9 January 2017,
  43. 5 years ago (1810 days of service).
  44. On average, /X has 51 users per day, each user lunches on average
  45. 6 account migrations, from just 1 launch to many (hundreds).
  46. The total volume /X transferred so far is around 240 TiB coming
  47. from nearly 520 000 imap account migrations and 810 million email messages.
  48. A2. Pros & Cons
  49. The online imapsync service /X runs on HTTPS only, with a letsencrypt
  50. certificate, an up to date certificate overall rated "A+" at
  51. https://www.ssllabs.com/ssltest/analyze.html?d=imapsync.lamiral.info
  52. Because of the HTTPS usage, what the users enter in their browser, the
  53. imap logins and passwords, can't be eavesdropped on the network.
  54. Imapsync itself takes care of encryption for the imap sessions, if
  55. possible. First, imapsync tries to use SSL on port 993, then TLS on
  56. port 143 if the servers announce TLS, then no encryption at all.
  57. Concerning encryption, what is done with the source imap server host1
  58. is independent of what is done with the destination imap server host2.
  59. On the date of 24 December 2021, there is no security problem detected
  60. or reported to me (Gilles LAMIRAL), so far.
  61. Concerning the Log4j threats, the imapsync server doesn't use Log4j at
  62. all, so it should be safe about this issue.
  63. Feel free to attack the service and feel free to report any hole
  64. encountered. Have in mind that I can watch what you do from the
  65. server-side, and then take measures if the service suffers from your
  66. acts. Drop me a note before will be fair play and I will let you act
  67. as harsh as you can.
  68. As the owner of the service, it could have been 520 000 pairs of
  69. credentials collected and nearly 240 terabytes of email messages.
  70. That's massive. I haven't kept them but I can't prove I haven't. It's
  71. just trust, like nearly every online service in the universe.
  72. Concerning imapsync transfers, the imap server certificates are not
  73. checked for authenticity by default because too many imap servers are
  74. crappy configured regarding their certified certificates.
  75. This default behavior is chosen like this because users of /X
  76. want their emails transferred, instead of being not transferred
  77. because of an incompetent imap server sysadmin.
  78. I admit that this part, checking imap ssl/tls certificates,
  79. could be improved from my side by including well known
  80. certificates directly in imapsync.
  81. If an imap server doesn't honor ssl nor tls, then logins, passwords
  82. and everything will go clear text during the imap transfers. That's
  83. not good at all! But what "comforts" me is that if an imap server does
  84. only clear text transfers, then it's also true for all the imap
  85. sessions the account owner encounters, imapsync is just one of them;
  86. the imap servers are then always unsecured for any imap software
  87. client.
  88. Last point, who could be sure that no cracker cracked the online hosts
  89. and that he isn't currently sniffing the credentials?
  90. No one! I'm not sure myself, even if I do take care of that
  91. possibility. So changing the imap accounts passwords after
  92. the sync is a safe and recommended practice! You can even
  93. change the password just after imapsync has started its job,
  94. just after a successful login. This way you know the previously
  95. given password is no longer working just after imapsync has
  96. started its job.
  97. =====================================================================
  98. Q. Does the online service store any sensitive information
  99. like my passwords?
  100. No.
  101. The online passwords are kept by your browser. The goal is that the
  102. next time you run a sync from your browser, all the parameters are
  103. already there without having to re-enter them. The save is done when
  104. you click on the "Sync or resync" green button. So, if you don't want
  105. your browser to keep your password, enter a wrong one or empty the
  106. password field and click on the "Sync or resync" green button, the
  107. wrong password will be saved in your browser and no sync will be done,
  108. since a correct login is mandatory to do anything on your mailboxes.
  109. =====================================================================
  110. Q. I want to switch from the visual interface /X to the
  111. imapsync command line or to the script examples
  112. https://imapsync.lamiral.info/#DOC_BASIC
  113. What should I know?
  114. A. Let's do some ascii art.
  115. The visual interface looks roughly like this, for the textfields input part:
  116. +------------------------------------------+------------------------------------------+
  117. | IMAP source Mailbox | IMAP destination Mailbox |
  118. | | |
  119. | Login (usually an email address) | Login (usually an email address) |
  120. | | |
  121. | test1 | test2 |
  122. | | |
  123. | Password | Password |
  124. | | |
  125. | secret1 | secret2 |
  126. | | |
  127. | IMAP Server hostname (or its IP address) | IMAP Server hostname (or its IP address) |
  128. | | |
  129. | test1.lamiral.info | test2.lamiral.info |
  130. | | |
  131. +------------------------------------------+------------------------------------------+
  132. Notice the 6 examples values I put in the previous "picture":
  133. * test1
  134. * secret1
  135. * test1.lamiral.info
  136. * test2
  137. * secret2
  138. * test2.lamiral.info
  139. The corresponding imapsync command line on Windows is:
  140. imapsync.exe --host1 "test1.lamiral.info" --user1 "test1" --password1 "secret1" ^
  141. --host2 "test2.lamiral.info" --user2 "test2" --password2 "secret2"
  142. The order of the parameters is whatever you want as long as you respect each pair
  143. like: --optionname "value"
  144. There is no need to type this in a command prompt window, just use the example script
  145. https://imapsync.lamiral.info/examples/imapsync_example.bat
  146. The corresponding imapsync command line on Linux is:
  147. imapsync --host1 "test1.lamiral.info" --user1 "test1" --password1 "secret1" \
  148. --host2 "test2.lamiral.info" --user2 "test2" --password2 "secret2"
  149. There is no need to type this in a command prompt window, just use the example script
  150. https://imapsync.lamiral.info/examples/imapsync_example.sh
  151. =====================================================================
  152. Q. Shall I have issues with the browser timing out?
  153. What happens if the browser connection is closed for whatever reason?
  154. A. A browser connection closed closes also the imapsync process,
  155. ie, the sync is ended right away.
  156. Further comments on this behavior.
  157. When using the /X interface there are three connections.
  158. One connection is the Browser/WebServer connection,
  159. the two other connections are the WebServer/ImapServers
  160. connections (imapsync stuff).
  161. If the Browser/WebServer connection timeouts or ends,
  162. the imapsync sync is also ended immediately by the remote
  163. Apache HTTPS server. Technically, Apache sends a TERM signal
  164. to the imapsync process, then wait some seconds before
  165. sending a KILL signal if the imapsync process is still alive.
  166. You can relaunch the sync with the "Sync!" button, at any time.
  167. If the "Sync!" button is gray/inactive then just reload
  168. the page (F5 or similar), and reenter the credentials.
  169. If the interface tells you that the sync is already going on,
  170. it may be that the sync is running from another browser or place.
  171. You can stop this sync with the "Abort!" button from any /X
  172. tab/window, even from another browser or place. To be able
  173. to abort with success, you have to give the same account
  174. parameters, same credentials, or imapsync will ignore the demand.
  175. In other words, you can try safely to launch several parallel
  176. runs between the same mailboxes. Open a new tab/windows with /X,
  177. and start the same sync. It's safe, the /X page will say that
  178. there is already one sync running and it will present
  179. the logfile running the sync like a "tail -f" command (isn't that magic?).
  180. =====================================================================
  181. Q. Shall I have issues when the webserver times out? What happens
  182. if the web server closes the connection for whatever reason?
  183. A. If the webserver closes the connection then usually it also
  184. kills the imapsync process and the imap connections as well.
  185. The current webserver timeout at
  186. https://imapsync.lamiral.info/X/
  187. is 3600 secondes, one hour.
  188. =====================================================================
  189. Q. The sync stalls at the beginning, just after a line like:
  190. "Host1: xxx says it has CAPABILITY for AUTHENTICATE LOGIN"
  191. What is the problem?
  192. A. I've seen this issue on /X with the imap server
  193. CommuniGate Pro IMAP Server 6.0.11
  194. The issue looks related to special characters in the password.
  195. Solution for now: change the password, keep only standard (ASCII)
  196. alphanumeric characters ABC-YZ abc-yz 012-89.
  197. =====================================================================
  198. Q. The synchronization fails with the error message like:
  199. Err 1/1: Host1 failure: Error login on [10.1.161.155] with user [webmaster@truc.com] auth [LOGIN]: 2 NO [ALERT] LOGIN DENIED -- COUNTRY IS BLACKLISTED
  200. A. The message "[ALERT] LOGIN DENIED -- COUNTRY IS BLACKLISTED" comes directly
  201. from the IMAP server at 10.1.161.155
  202. It looks like that the 10.1.161.155 imap server filters incoming
  203. connexions based on their IPS. In that case, here are the current
  204. IPs of the imapsync online service (September 2022):
  205. ks5.lamiral.info has address 91.121.221.224
  206. ks5ipv6.lamiral.info has IPv6 address 2001:41d0:2:84e0::1
  207. ks6.lamiral.info has address 5.39.87.81
  208. ks6ipv6.lamiral.info has IPv6 address 2001:41d0:8:9951::1
  209. ks7.lamiral.info has address 5.135.177.225
  210. ks7ipv6.lamiral.info has IPv6 address 2001:41d0:8:b8e1::1
  211. i050.lamiral.info has address 213.32.72.139
  212. i050ipv6.lamiral.info has IPv6 address 2001:41d0:302:1000::155d
  213. vp3.lamiral.info has address 51.178.81.27
  214. vp3ipv6.lamiral.info has IPv6 address 2001:41d0:404:200::4d81
  215. vp4.lamiral.info has address 51.38.34.201
  216. vp4ipv6.lamiral.info has IPv6 address 2001:41d0:305:2100::4c46
  217. The imapsync online service may contact your imap server with one
  218. or more of those IP addresses.
  219. CPhulk of Cpannel has a buildin country block that can cause this behavior.
  220. Later on you may encountered issues with maximum sessions per ip.
  221. You can change that within cPannel.
  222. https://support.cpanel.net/hc/en-us/articles/4406663082519-What-is-cPHulk-
  223. https://docs.cpanel.net/whm/security-center/cphulk-brute-force-protection/
  224. =====================================================================
  225. =====================================================================