Email configuration

Joined
Dec 14, 2018
Messages
7
Hi.
I'm trying to reconfigure email notifications on FreeNAS 11.2.
I'm moving from gmail to another provider (net-c). (works well with gmail)
I followed the guides etc, my configuration looks right.
ssl and authentication is enabled with the correct values.

However, I get error 334 each time. My provider only authorized AUTH LOGIN.
Apparently, it doesn't work with freenas.
I got it working in my nextcloud jail right away, but it provides configuration of the auth type in the interface.

Is there a way to force this auth type in config files or somewhere?
Thanks in advance.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Hi.
I'm trying to reconfigure email notifications on FreeNAS 11.2.
I'm moving from gmail to another provider (net-c). (works well with gmail)
I followed the guides etc, my configuration looks right.
ssl and authentication is enabled with the correct values.

However, I get error 334 each time. My provider only authorized AUTH LOGIN.
Apparently, it doesn't work with freenas.
I got it working in my nextcloud jail right away, but it provides configuration of the auth type in the interface.

Is there a way to force this auth type in config files or somewhere?
Thanks in advance.
This may require an additional field to be created in the email setup screen. It would be best to submit a feature request.
https://www.ixsystems.com/documentation/freenas/11.2/system.html#support
 
Joined
Dec 14, 2018
Messages
7
Agreed, it will probably require some development.
Is there a way to check that this auth method isn't supported? That would be the first step.
In the mean time, i'll look around in the issue tracker
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Agreed, it will probably require some development.
Is there a way to check that this auth method isn't supported? That would be the first step.
In the mean time, i'll look around in the issue tracker
FreeBSD must support it or you wouldn't have been able to do it from the jail. If they didn't implement a way to configure it in the GUI, FreeNAS doesn't support it, but that is only because it must be configured in the GUI. The settings you make in the GUI are recorded in a configuration database and the files you might edit to "configure it by hand" are rebuilt during boot based on the configuration database. It is down to how FreeNAS works. All the settings need to be made in the GUI, with very few exceptions, or those settings don't survive a reboot.
 
Top