Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions ispdb/nili.ca.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
<?xml version="1.0" encoding="UTF-8"?>
<clientConfig version="1.1">
<emailProvider id="nili.ca">
<domain>nili.ca</domain>
<displayName>Nili Mail</displayName>
<displayShortName>Nili</displayShortName>

<incomingServer type="imap">
<hostname>email.nili.email</hostname>
<port>993</port>
<socketType>SSL</socketType>
<username>%EMAILADDRESS%</username>
<authentication>password-cleartext</authentication>
</incomingServer>

<outgoingServer type="smtp">
<hostname>email.nili.email</hostname>
<port>587</port>
<socketType>STARTTLS</socketType>
<username>%EMAILADDRESS%</username>
<authentication>password-cleartext</authentication>
</outgoingServer>

<webMail>
<loginPage url="https://webmail.nili.ca/"/>
</webMail>
Comment on lines +24 to +26
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As mentioned in #96, we're looking into getting rid of the webMail section as it doesn't really bring much real-life value. I don't think we should include it in new configurations.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dear @babolivier, Thank you for looking to this.
Nili already hosts their own autoconfig file, but many of their customers face issues accessing it through certain ISPs, which has led to a noticeable number of support requests.

Originally, the Nili team explored creating a branded email app, and forking current apps seemed like the most natural choice; Thunderbird has long been their users’ top recommendation for the past 12 years. Instead, I suggested listing their autoconfig in the ISPDB and officially promoting Thunderbird as the recommended Nili email client for both desktop and mobile. This approach would save their team from maintaining a fork while strengthening Thunderbird’s presence among Nili users.

That said, I’m completely open to other approaches or ideas to share with their team if there’s a preferred path forward.
Sincerely,

Nick

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And webMail can be eliminated!

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Self-hosted autoconfig files should provide the same level of support for configuration auto-discovery as ISPDB - in fact, Thunderbird prioritises configurations hosted by service providers over those described in ISPDB.

I've looked a bit more into this, and it looks like there's a Cloudflare configuration issue here. https://autoconfig.nili.ca/mail/config-v1.1.xml (one of the URLs Thunderbird attempts to reach) redirects to https://jar.nili.ca/mail/config-v1.1.xml, but it looks like the whole jar.nili.ca domain is behind a Cloudflare frontend. As a result, Thunderbird is hit with a Cloudflare captcha that it cannot solve, and it's unable to retrieve the configuration.

Would the Nili team be open to disabling this protection specifically for the path /mail/config-v1.1.xml, so automated software such as Thunderbird's (and other supporting clients') auto-discovery feature can query it? Feel free to loop me (brendan [at] thunderbird.net) into any conversation I can help with 🙂

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @coldad, is there any news on this? Would you like me to reach out to Nili to get the ball rolling?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @babolivier ,
how do you check the error?
Would you please attempt again and see if tha resolved?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @coldad, I initially noticed it by going to https://autoconfig.nili.ca/mail/config-v1.1.xml, and noticing that I'm served by a Cloudflare captcha (which might not show for everyone). You can also verify this by running curl -L https://autoconfig.nili.ca/mail/config-v1.1.xml (-L tells cURL to follow redirects) and seeing that it serves Cloudflare's HTML, not the XML file that's hosted at that address.

I've just checked it now, it still seems to be happening.


<!-- Optional: document your help page(s) for maintainers -->
<documentation url="https://nili.ca/knowledge-base/how-to-connect-email-clients-to-servers/">
<descr lang="en">POP, IMAP, and SMTP settings for Nili</descr>
</documentation>
</emailProvider>
</clientConfig>