Closed omexlu closed 2 years ago
@DerLinkman
I have just tested it again but it does not work.
Postfix log (Note here perhaps that from=<>
remains empty here, and no email is sent.):
12.09.2022, 14:28:40 info D263C3F940: from=<>, size=6254, nrcpt=1 (queue active)
12.09.2022, 14:28:39 info D263C3F940: message-id=<dovecot-1662985719-777011-0@cd822d26d8e4>
12.09.2022, 14:28:39 info D263C3F940: replace: header Received: from cd822d26d8e4 (mailcowdockerized-dovecot-mailcow-1.mailcowdockerized_mailcow-network [172.22.1.250])??by mx.s3cured.pw (Postcow) with ESMTP id D263C3F940??for <tgl@hushmail.me>; Mon, 12 from mailcowdockerized-dovecot-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.250]; from=<> to=<tgl@hushmail.me> proto=ESMTP helo=<cd822d26d8e4>: Received: from sieve (sieve [172.22.1.250]) by mx.s3cured.pw (Postcow) with ESMTP id D263C3F940??for <tgl@hushmail.me>; Mon, 12 Sep 2022 14:28:39 +0200 (CEST)
12.09.2022, 14:28:39 info D263C3F940: client=mailcowdockerized-dovecot-mailcow-1.mailcowdockerized_mailcow-network[172.22.1.250]
Dovecot log:
12.09.2022, 14:28:39 warning lmtp(noreply@the-greenleaf.in)<256097><+JMZLfclH2Nh6AMAe7znIg>: Warning: smtp-client: conn postfix:588 (172.22.1.253:588) [1]: Received invalid EHLO response line: Unexpected character in EHLO keyword
Somehow the email is queued but not sent.
Thanks in advance.
Can you try something for me? Downgrade your sogo version to 1.109 in docker-compose.yml and restart your stack with docker-compose up -d again to see if this error persists or not.
Hello,
I'm not that professional to dare to mess in there now, sorry.
But I'm sure it's either sogo itself or some connection, because it has always worked in the past (a few updates before).
I'd rather leave the troubleshooting here to the devs or users who have more idea than me :)
I'm sure you will find the problem.
Thanks in advance.
@DerLinkman Something new in this case?
Not really it hasn't been reported anymore since your report. And I didn't had time to investigate. But in the issue #4743 we came across the idea of a MySQL connector issue. Maybe it's also related to that.
@DerLinkman
Ok thanks. I will wait until your team has time to investigate more.
I could be related to this. Maybe you could test on your test-machine soon 💪👍
Can you try something for me?
Disable the Sieve Protocol for the User in the mailcow UI and re-enable it.
Then try to save/use the filter.
@DerLinkman
Still not working, the email is rejected but the email is not sent out.
I have done the following:
Did I do this correctly?
PS. So unfortunately still does not work.
Thanks in advance.
Cannot reproduce it sorry.
On all mailcows on three different maschines i cannot reproduce your error.
But i´ve noticed something. You are using ufw. According to our docs: There are several problems with running mailcow on a firewalld/ufw enabled system.
Maybe this is one of those.
All maschines i´ve used used IPTables instead of ufw.
@DerLinkman
First of all, thank you for testing.
So I don't really have an error message but the mail is just not sent which is set in Sieve.
Furthermore, I had never had problems with UFW and MailCow before, everything works without problems except for the Sieve and the sending.
Is only since a few updates that it no longer works.
I could try to disable UFW completely.
Is there perhaps an extra port that I still have to release?
My configuration has not changed since the beginning, so it is a bit suspicious that it suddenly no longer works since a few updates.
Is the reply mail sent with your 3 machines?
The communication seems to work with me, otherwise the mail would not be correctly rejected.
Thanks in advance.
Yes it works just fine without any issue on my tested maschines
Hm okay, thanks, I must look but is very strange.
@DerLinkman
I have now tried from another sender and there it works 🙈
It seems that hushmail cannot receive rejected mails, from any other email account it works without problems.
What I noticed is that the sender of the rejected mails is "postmaster@domain.tld".
Would be better if the sender here is also the recipient of the actual mail.
Maybe this is possible somehow?
Sorry for the extra work I have done, but now everything works as intended again :)
Thanks again.
Contribution guidelines
I've found a bug and checked that ...
Description
Sogo filters (sending) no longer work, since when I unfortunately do not know but have seen that there were problems with Sogo and have tested.
Has always worked in the past, problem only hits since the last updates. Everything goes without problems except that.
SEE SCREENSHOT FROM SOGO FILTER-SETTING: https://imgur.com/a/0ZJLm7B
Logs
Steps to reproduce
(See screenshot above for the setting that worked in the past without any problem).
System information
docker version
)docker-compose version
)git describe --tags `git rev-list --tags --max-count=1`
)Output of
git diff origin/master
, any other changes to the code? If so, please post them: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:
DNS problems? Please run
docker exec -it $(docker ps -qf name=acme-mailcow) dig +short stackoverflow.com @172.22.1.254
(set the IP accordingly, if you changed the internal mailcow network) and post the output: