-
Notifications
You must be signed in to change notification settings - Fork 63
Support for Custom Ports #120
Comments
Pinging @axelvnk - Hey! I saw that you made a pull request on the main Nylas Mail repository (nylas/nylas-mail#3640). It doesn't appear that there is any real activity there, though. Figured I'd see if you would like to make that pull request here before I go ahead and make my own. |
@54 I'll do it tonight :) |
@axelvnk did you do it? |
@dweremeichik would you want this to remove the dropdown in place of a text field for port number? Or would we rather have the dropdown with "Custom..." which shows the input field and allows for input? The latter I think is better, but will require some extra work |
I'm behind the latter. The other option allows for too much error. It's hard enough for most to set up email as it is. |
agreed; therefore i dont think the PR at nylas/nylas-mail#3640 is sufficient. i've got some time tonight to work this. still need my 4 PRs for the month >.> that is if @axelvnk doesnt want to work it |
i went ahead and started this |
Well done! I'm 👍 on this. |
Hey!
It would be great if someone could add support for non-standard ports when configuring an email account. In my particular case, it makes it mildly annoying to use ProtonMail as their bridge software defaults to 1143 and 1025 for the incoming/outgoing ports.
Also, this affects signifcantly more people than simply ProtonMail users. Many organizations change their mail server ports—which makes Nylas unusable without using inspect element or something. See: nylas/nylas-mail#3424
The text was updated successfully, but these errors were encountered: