Est-ce que tu peux détailler ta remarque / question ?
J’ai cette impression aussi. Si oui ce serait vraiment top pour améliorer la robustesse de Yunohost en ce qui concerne le taux de réception des emails. J’attends la sortie officielle de 4.1 pour tester sur mon serveur de prod !
La question, si j’ai bien compris, c’est : si j’utilise mailjet (ou Google) comme relais email, est-ce que mes correspondants verront mon email comme venant de :
- monadresse@monserveuryunohost ? (complètement transparent)
- monadresse@monserveuryunohost via mailjet (ou via Google) ?
- uneadresse@mailjet
Les cas 1 et 2 sont viables car c’est transparent ou à peu près pour le récipiendaire, le cas 3 ne fonctionne pas en usage courant.
Je parle bien ici de ce qui est visible pour l’utilisateur final, pas de ce qui se passe entre les serveurs (dans l’absolu peu importe)
Logiquement les relais mail sont transparent, mais je n’ai aucune idées précises concernant mailjet et google. Faut tester.
Le mail serait donc expédié avec mon adresse mail (mon domaine) et non pas le domaine du relai?
Logiquement le relais ne modifie pas l’entête “From” mais il est possible que certains relais ait des restrictions. Comme dit il faut faire un test pour en être sûr.
We had decided to rollback to may, see: [fix] Accept all kind of relay even the unencrypted · YunoHost/yunohost@11fe9d7 · GitHub
1 Like
I don’t understand this issue … Imho it’s expected that old backups are kept as .tar.gz (considering they were .tar.gz and Yunohost won’t “dezip” old backups, it’s just that new backups will be not compressed)
On my side I’m able to download the .tar.gz and open it with a graphical tool … The fact that file reports “POSIX tar archive” doesn’t mean it’s really-a-.tar. Actual .tar.gz are also displayed as “POSIX tar archive” by file.
Thanks for update ! There are great improvements in 4.1.1 
Now, Bitwarden works, I can use it again !
Collabora works great now too 
Still have the issue for the logs : it works great under CLI, but not on the webadmin, I receive this message :
Action
GET /logs/display
{"path":"20201219-095752-app_upgrade streama","filter_irrelevant":"","number":"25","with_suboperations":""}
Trace
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/moulinette/interfaces/api.py", line 482, in process
ret = self.actionsmap.process(arguments, timeout=30, route=_route)
File "/usr/lib/python2.7/dist-packages/moulinette/actionsmap.py", line 587, in process
return func(**arguments)
File "/usr/lib/moulinette/yunohost/log.py", line 267, in log_display
metadata["suboperations"] = list(suboperations())
File "/usr/lib/moulinette/yunohost/log.py", line 260, in suboperations
if submetadata.get("parent") == base_filename:
AttributeError: 'NoneType' object has no attribute 'get'
In short, thank you for this update which brings lots of fixes
2 Likes
Hello,
Since ssowat 4.1.1 update (I guess), plenty of error message in nginx log files for Nextcloud domain, with
2020/12/21 13:51:01 [error] 28696#28696: *38 [lua] helpers.lua:396: authenticate(): Connection failed for: nextclouduser, client: 192.168.1.254, server: my.domain, request: "GET /remote.php/dav/avatars/nextclouduser/128.png HTTP/1.1", host: "my.domain"
with corresponding fail2ban (huge) error messages:
2020-12-21 13:51:02,390 fail2ban.actions [4635]: ERROR Failed to execute ban jail 'yunohost' action 'iptables-multiport' info 'ActionInfo({'ip': '192.168.1.254', 'family': 'inet4', 'ip-rev': '254.1.168.192.', 'ip-host': None, 'fid': '192.168.1.254', 'failures': 10, 'time': 1608555062.0, 'matches': '2020/12/21 13:50:55 [error] 28696#28696: *36 [lua] helpers.lua:396: authenticate(): Connection failed for: nextclouduser, client: 192.168.1.254, server: my.domain, request: "PROPFIND /remote.php/dav/files/nextclouduser/ HTTP/1.1", host: "my.domain"\n2020/12/21 13:50:59 [error] 28696#28696: *38 [lua] helpers.lua:396: authenticate(): Connection failed for: nextclouduser, client: 192.168.1.254, server: my.domain, request: "GET /status.php HTTP/1.1", host: "my.domain"\n...etc.
With 4.1.1 i have been banned on my home ip (with a server on a vps):
2020-12-21 13:21:51,138 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:51
2020-12-21 13:21:51,214 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:51
2020-12-21 13:21:51,684 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:51
2020-12-21 13:21:51,748 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:51
2020-12-21 13:21:51,975 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:51
2020-12-21 13:21:52,112 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:52
2020-12-21 13:21:52,351 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:52
2020-12-21 13:21:52,369 fail2ban.filter [7270]: INFO [yunohost] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:52
2020-12-21 13:21:52,752 fail2ban.actions [7270]: NOTICE [yunohost] Ban 92.xxx.yyy.zzz
2020-12-21 13:21:52,754 fail2ban.filter [7270]: INFO [recidive] Found 92.xxx.yyy.zzz - 2020-12-21 13:21:52
It may appears when i run nexctloud client (or not, i am not sure of this)
The fix from Kayou was merged and released in ssowat 4.1.1.1, that should fix the issue
3 Likes
Just did the beta update on my server.
Everything is working fine, Nextcloud, Wekan, Rainloop, Wallabag2 running great as far as I could test.
However I wasn’t able to find where the email relay can be configured in the admin panel ?
Thanks for your help 
Unfortunately it’s not configurable from the webadmin at this point … You need to check the yunohost settings commands 
Hi Aleks that’s fine of course, I managed very easily to configure my SMTP relay. Everything seems to work perfectly with the free mailjet smtp relay. I have a big hope that this will finally solve my issues with hotmail users…
Do you want me to document the feature on Yunohost website ? These are the kind of things where I can help.
3 Likes
Yup if you feel like writing a small piece of doc for it that would be super appreciated ! 
3 Likes
“Extend permission features” failing on a test server; logs: https://paste.yunohost.org/raw/dehumeqewi
Relevant log extract:
020-12-28 12:48:32,481: ERROR - La migration 0019_extend_permissions_features a échoué avec l’exception Domaine '^\' inconnu : annulation
Traceback (most recent call last):
File "/usr/lib/moulinette/yunohost/tools.py", line 897, in tools_migrations_migrate
migration.run()
File "/usr/lib/moulinette/yunohost/data_migrations/0019_extend_permissions_features.py", line 99, in run
migrate_legacy_permission_settings()
File "/usr/lib/moulinette/yunohost/utils/legacy.py", line 188, in migrate_legacy_permission_settings
show_tile=False, allowed='visitors', protected=True, sync_perm=False)
File "/usr/lib/moulinette/yunohost/log.py", line 358, in func_wrapper
result = func(*args, **kwargs)
File "/usr/lib/moulinette/yunohost/permission.py", line 354, in permission_create
sync_perm=False)
File "/usr/lib/moulinette/yunohost/log.py", line 358, in func_wrapper
result = func(*args, **kwargs)
File "/usr/lib/moulinette/yunohost/permission.py", line 420, in permission_url
ur = _validate_and_sanitize_permission_url(ur, app_main_path, app)
File "/usr/lib/moulinette/yunohost/permission.py", line 708, in _validate_and_sanitize_permission_url
raise YunohostError('domain_name_unknown', domain=domain)
YunohostError: Domaine '^\' inconnu
@JimboJoe : eh, that’s an interesting one 
Can you share the output of
grep "unprotected" /etc/yunohost/apps/freshrss/settings.yml
?
root:~# grep "unprotected" /etc/yunohost/apps/freshrss/settings.yml
unprotected_regex: ^\/api\/.*|\/scripts\/api.js$