You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
... I have understood that answers are voluntary and community-driven, and not commercial support.
... I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description
I enabled "Domain wide footer" for my test domain. When I send a plain-text-only message, there's now suddenly an extra blank line at the *beginning* of the message body.
It seems that when "mangling" the message to add the footer, this extra line is introduced into the message body.
Logs:
Not helpful.
Steps to reproduce:
1. Enable "Domain wide footer" for a domain.
2. Use a single line as the "plain" footer for testing. I did not use a trailing line break, dunno if it matters.
3. (MUA doesn't matter) Send plain-text email from one mailbox in that domain, containing just a single word "Test", with no blank line before it.
4. (On the receiving end:) Note that there is now a single blank line on top of the line "Test".
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Debian 12.7
Server/VM specifications:
AWS m5.large: 8 GB RAM, 2 vcores
Is Apparmor, SELinux or similar active?
no
Virtualization technology:
AWS EC2
Docker version:
27.3.1
docker-compose version or docker compose version:
v2.29.7
mailcow version:
2024-08a
Reverse proxy:
none
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: