No Permissions to Foreward Mail

vandewater

I've just ran an update of my grommunio host, and it appears I've lost the ability to forward existing mail in another user's mailbox that I have full access to. To be clear, I can still create new mail and send as this user. I've narrowed it down to the gromox package. Has something changed recently? I've been unable to find anything related in documentation or forum (though my search foo could be lacking). Any help is appreciated.

gromox-2.16.41.9bb3a2f-lp154.15.1 -> 2.20.6.g19e4a21-lp154.18.1

crpb

vandewater gromox-2.16.41.9bb3a2f-lp154.15.1 -> 2.20.6.g19e4a21-lp154.18.1

You are still on OpenSuse Leap 15.4. Is that on purpose?
It could be that there is already a fix in 2.22 but i guess that will not be build anymore for Leap 15.4.

vandewater

I went to 15.5, which is when I noticed the issue, so I restored to where I was and slowly updated each package until I determined the change was with gromox,

crpb

Well, with the information you have given there isn't much i can say.
Did you try it in the Webapp or via Outlook? Outlook-Versions could also matter. Have you tried removing the Permissions and recreating them? Maybe take a screenshot of the Admin-GUI where it is configured.

And 'Full-Access' doesn't mean you are allowed to send in their name. So maybe it is just 'Sent-As' or 'Delegates' which got lost somehow?

vandewater

Just did another update to 15.5 and gromox-2.23.26.ga69b508-lp155.21.1. Same issue:

vandewater

This is for the shared mailbox:

Same behavior for mailboxes in Normal mode.

vandewater

Removing permissions and re-adding have no effect.

crpb

In my experience you should either set Delegate or Send As, not both. Disregard it if that was just because of the blurry text.
Have you looked into the log-files for some error/warning? find /var/log/grom* /var/log/nginx/ /var/log/php* -type f -iname "*log" -exec tail -f "{}" + or something alike.

vandewater

Yeah, sorry I obfuscated the email address with permissions. Each permissions had the same user. I removed all except Full permission users but no change.

I'm seeing this in logs:
==> /var/log/php-fpm.log <== [11-Feb-2024 07:39:04] WARNING: [pool grommunio-web-pool] child 19630 said into stderr: "NOTICE: PHP message: Unable to submit message for REDACTED@REDACTED, MAPI error: MAPI_E_NO_ACCESS. SMTP server may be down or it refused the message or the message is too large to submit or user does not have the permission ..."

==> /var/log/nginx/nginx-web-error.log <== 2024/02/11 07:44:36 [error] 7198#7198: *1166 FastCGI sent in stderr: "PHP message: Unable to submit message for REDACTED@REDACTED, MAPI error: MAPI_E_NO_ACCESS. SMTP server may be down or it refused the message or the message is too large to submit or user does not have the permission" while reading response header from upstream, client: REDACTED, server: _, request: "POST /web/grommunio.php?subsystem=webapp_1707626762548 HTTP/2.0", upstream: "fastcgi://unix:/run/php-fpm/php-grommunio-web-fpm.sock:", host: "REDACTED"

crpb

vandewater removed all except Full permission users

You probably want 'Full permission' as this is just for the access of the mailbox and has nothing to do with the 'sending of mails'. So enable either one of Send-As or Delegate aswell if you haven't tried that yet.

hmm.. what does systemctl --failed say?
You could also look into journalctl -u 'grom*' -f --since -1h

You can send normal mails right? 😛

vandewater

You probably want 'Full permission' as this is just for the access of the mailbox and has nothing to do with the 'sending of mails'. So enable either one of Send-As or Delegate aswell if you haven't tried that yet.

Tried only 'Full permission, only Send as, and only Delegates. No change.

hmm.. what does systemctl --failed say?

# systemctl --failed UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed.

You can send normal mails right?

Yup. From my mailbox, I can send new mail and forward existing mail. From other users I have access to, I can send new mail, but can't forward existing mail.

vandewater

Interesting. Noticed gromox-2.24.2.g6bf4f42-lp155.4.1.x86_64 was released. Installed, and issue is gone.

crpb

I guess mwilliams could recreate and fix it.
https://github.com/grommunio/gromox/commit/6bf4f4249f33f8c1fe3a91fe4b51870537c501e9

mwilliams

crpb

https://github.com/grommunio/grommunio-web/commit/4bc05c51b3feaf6b7c2b0b4a109ab5502be33089

vandewater

Well thank you both for the attention.