Uberspace
qmail-migration: Clarification on 'Workaround to keep “-” delimiter catchall'
I just received a mail regarding my qmail setup, that includes two different dash-delimited catchall mails. uberspace migration qmail check helpfully pointed me to those, and very soon I found https://manual.uberspace.de/migration/qmail/reports/config-is-catchall/#workaround-to-keep-delimiter-catchall, which was really nice.
I have several questions and remarks about the suggested workaround.
First, there seems to be an error in the suggested script, in that reject; is not valid (the webmailer raised the issue when i was copy-and-pasting it there). It looks like reject needs some argument detailing the rejection reason.
Second, say I have a .qmail-someaddress-default (containing only the line ./users/someaddress/), whouldn't the closer sieve script contain redirect "someaddress@whateverdomain"; when matching the catchall address? The way I understand it the current workaround sets up a new address that will have to be set up separately in the e-mail address.
This is the script I came up with (for two addresses):
# cat users/catchall-mailbox/sieve/forward-catchall.sieve
reject require ["fileinto", "reject"];
if address :matches "to" "address1-*@*" {
redirect "[email protected]";
stop;
}
if address :matches "to" "address2-*@*" {
redirect "[email protected]";
stop;
}
reject "User email address rejected";
Does that make sense? Should I open a PR to update the script (and description) accordingly?
