changing Port in AdvancedSetup has no effect (on Android/iOS)

[nayooti]

I was implementing a custom Port field in the AdvancedAccount Setup. Changing the port in IMAP to random number still allowed me to receive messages. Login was via oAUTH2.

Same happened on Android.

• Delta Chat Core Version:
• Expected behavior:
• Actual behavior:
• Steps to reproduce the problem:
• Screenshots:
• Logs:

[hpk42]

On Wed, May 22, 2019 at 14:51 +0000, nayooti wrote: I was implementing a custom Port field in the AdvancedAccount Setup. Changing the port in IMAP to random number still allowed me to receive messages. Login was via oAUTH2.

i think core uses the configured port but then falls back to the standard ones. I'd prefer if core only uses the specified one, as this makes debugging probably faster and easier.

[r10s]

@nayooti thanks for filing the issue. sorry that i could not answer this question in the a/v directly.

just had a look. @hpk42 is right. if you define a port that does not work, dc_configure() checks some different known ports.

this is also logged, if such a fallback happens, some Trying: ... lines are added to the log.

same happens also for the username that is tested with and without the domain-part and for starttls vs. ssl.

in general, i think this is okay. i think the most important thing is to get a connection - wrong parameters may come from autoconfigure/autodiscover for $reasons (outdated, http-subdomain-config does not match mail-config etc.) EDIT: this is not true, if we get an autoconfig, we do not probe at all.

sure, the drawback is that it is harder to debug. but if we stop the probing (which is done only after failures), things may get harder for the user.