Message Body is empty - Githubissues

modoboa / modoboa-webmail

The webmail of Modoboa

MIT License

73 stars 48 forks source link

Message Body is empty #153

Closed danielsatanik closed 6 years ago

danielsatanik commented 6 years ago

Info:

Modoboa: 1.10.2
Webmail: 1.4.1
Installer: yes
Upgraded with pip to the current versions

my mail contents are empty and I don't see any errors in

/var/log/mail.log
/var/log/nginx/access.log
/var/log/nginx/error.log
/var/log/uwsgi/app/modoboa_instance.log
and on the website itself

screen shot 2018-02-12 at 13 43 37

Is there somewhere else to look? Something to enable? A similar issue I haven't found yet?

tonioo commented 6 years ago

@danielsatanik Does it happen with all messages?

danielsatanik commented 6 years ago

@tonioo yes it does and on all accounts

tonioo commented 6 years ago

@danielsatanik Have you tried with DEBUG set to True?

danielsatanik commented 6 years ago

Inside Modoboa instance/instance/settings.py? Yes

screen shot 2018-02-15 at 18 08 37

tonioo commented 6 years ago

Yes and do not forget to reload apache. Once done, please use a javascript debugger to inspect responses sent by the server.

danielsatanik commented 6 years ago

I get the following error in the JS console

Refused to display 'https://mail.example.com/webmail/getmailcontent?mbox=INBOX&mailid=271&links=1' in a frame because it set 'X-Frame-Options' to 'DENY'.

My nginx-conf doesn't use this option, but it is in settings.py enabled. I enabled it myself because the option python manage.py check --deploy suggested I should do it. Is there a different option I should choose instead of "DENY"?

I will try "SAMEORIGIN" for now and see if it fixes it.

danielsatanik commented 6 years ago

It worked setting it to SAMEORIGIN, thank you. I guess I can close it now, but maybe you should adapt the check option then