-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
SOGo calendar email notification #4754
Comments
I think there is somewhere an issue with sending, same as here: |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Problem still exists. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
And again, problem still exists. |
@Schnuecks could you please share the config at |
Hi, @marrobHD here it is.
|
See steps to reproduce |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still not resolved. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not solved until disable SOGo Authentication |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still not resolved. |
Issue happening on my end too with a almost completely default install. logs:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Still a problem. |
Do not close. |
On another note: it would be nice if there was any feedback in that matter: Is there insufficient information? Does it work for anyone else? Even a simple wontfix comment would be greatly appreciated. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not State |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
Not stale |
I'm running into the same issue. I've observed a secondary bug as well. When enforced TLS authentication is enabled for the mailbox postfix doesn't even log an error/connection when sending an email. And when someone disables forced TLS authentication it does log an error and says SASL PLAIN authentication failed (reason unavailable). I may end up buying a support package just to get this issue resolved (it is that important for me). |
What did you want to achieve? It works for me. Do you want to change a shared calendars appointment and then there is no mail send? Because if so, you need to allow the mail account you modify the shared calendar with to send as the calendar owner: Example: You have |
Hello, Relevant setup attached. Basically, I want the calendar to send email alerts to my email address when appointments are 2 hours from start. When TLS is not force-enabled I also get the following error in the mailcow postfix logs:
When TLS is not enabled there are no errors, but also no emails. |
Ah ok, now i get it. Yes i need to analyse this and see if we can fix it. |
Will be fixed just in time next week :) |
It occurred to me that if the calendar didn’t send emails the mail filters in sogo reject response might not as well. I’ll test that later today or tomorrow but if that doesn’t work does this pull request fix that? |
That's what it's made for |
Will be fixed in 2024-11 |
Contribution guidelines
I've found a bug and checked that ...
Description
If an event happens in SOGo calendar an email notification isn't sent. the problem seems to be the authentication.
If authentication in SOGo is disabled the notification is send as unknown user. If reactivated nothing happens and a postfix error occurs.
Logs
Steps to reproduce
/opt/mailcow-dockerized/data/conf/sogo/sogo.conf
// SOGoSMTPAuthenticationType = plain;
restart sogo
send works but with unknown user
/opt/mailcow-dockerized/data/conf/sogo/sogo.conf
SOGoSMTPAuthenticationType = plain;
restart sogo
send doesn't work
System information
docker version
)docker-compose version
)git describe --tags `git rev-list --tags --max-count=1`
)All third-party firewalls and custom iptables rules are unsupported. Please check the Docker docs about how to use Docker with your own ruleset. Nevertheless, iptabels output can help us to help you:
iptables -L -vn:
ip6tables -L -vn:
iptables -L -vn -t nat:
ip6tables -L -vn -t nat:
The text was updated successfully, but these errors were encountered: