Skip to content
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

"Aliases" table has "BCC destination" column, while such field cannot be defined? #6135

Open
5 tasks done
ralfbergs opened this issue Nov 2, 2024 · 0 comments
Open
5 tasks done
Labels

Comments

@ralfbergs
Copy link

Contribution guidelines

I've found a bug and checked that ...

  • ... 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 noticed that the "Aliases" table has a column labelled "BCC destination," so I would expect that you can define such a property when you create an alias. Strangely, there is no such field when setting up an alias, so is this something that existed in the past and has been abandoned since?

Logs:

Won't help.

Steps to reproduce:

1. Follow clickpath "E-Mail" -> "Configuration" -> "Aliases"
2. Note that in the table of all existing aliases, a column "BCC destination" is displayed.
3. Click "Add alias" button and note that in the dialog that pops up there is no field named "BCC destination" or similar.

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:

No relevant changes.

Logs of iptables -L -vn:

Won't help.

Logs of ip6tables -L -vn:

Won't help.

Logs of iptables -L -vn -t nat:

Won't help.

Logs of ip6tables -L -vn -t nat:

Won't help.

DNS check:

Not relevant.
@ralfbergs ralfbergs added the bug label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant