-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provisioning does not replace %USERID% in mail host #2698
Comments
Can be fixed at mail/lib/Service/Provisioning/Config.php Line 55 in 11a5d64
|
This is a serious bug... cmon. Did you ever get the provisioning working with the And when I go to the Mail tab it just stays loading for a very long time and ends up in this: My Dovecot says Nextcloud is trying to login with the placeholder lol
It says that “* %USERID% and %EMAIL% will be replaced with the user’s UID and email” but apparently it doesn’t replace the %EMAIL% placeholder with the login email as we can see on the log. Note: my users will login with 2 different domains using their full e-mail address. The IMAP and SMTP require login with the full e-mail as well. |
Lines 155 to 157 in 3d118f2
|
How come? They login to Nextcloud with their e-mail. In my setup Nextcloud is configured to authenticate users against an IMAP server , unless I'm missing something there's no reason why the email would be missing... |
Sounds like you are using the email as login name and should rather map %USERID% to the imap username. |
Hm, I'll give it a try! |
Expected behavior
%USERID% (and %EMAIL%) can be used in IMAP/SMTP host and will be replaced by the values for each user.
Actual behavior
the host in the preview and in the db table oc_mail_accounts is literally "%USERID%"
Mail app
Mail app version: 1.1.2
Mailserver or service: Postfix / Dovecot
Server configuration
Operating system: Debian 9
Web server: Apache2
Database: MariaDB
PHP version: 7.4
Nextcloud Version: 18.0.1
Client configuration
Browser: Chrome
Operating system: Windows 10
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: