You can use forwardings in the form of
$MAILBOX@$USER.uber.space. If you have set up additional domains,
$MAILBOX@$DOMAIN will also work.
We do not forward mails with a spam score >= 10. This is crucial due to policy reasons at nearly any mail provider and makes sure the reputation of our servers stays fine.
Add forwards for a mailbox¶
You can configure forwardings with the
uberspace mail user forward set <mailbox> <mail address> command. This will effectively create an alias for the specified address. There is no way to convert a regular mailbox (without forwarding) to an alias.
To forward all mails from
email@example.com run the following command:
[isabell@stardust ~]$ uberspace mail user forward set forwardme firstname.lastname@example.org Mail to forwardme will be forwarded to email@example.com. [isabell@stardust ~]$
uberspace mail user forward set overwrites existing configurations.
List existing forwards for a mailbox¶
You can list your existing forwardings using the
uberspace mail user forward list command, e.g. if you have setup fowardings for
[isabell@stardust ~]$ uberspace mail user forward list forwardme firstname.lastname@example.org [isabell@stardust ~]$
Delete forwards for a mailbox¶
You can delete forwardings using the
uberspace mail user forward del <mailbox> command. This will delete the specified alias, so mails sent to it will no longer be delivered (exept if you set up a catchall address). To delete forwarding for
forwardme, run the following command:
[isabell@stardust ~]$ uberspace mail user forward del forwardme Mail to forwardme will no longer be forwarded. [isabell@stardust ~]$
With enabled spam filtering we do not forward mails with a spam score greater than 5. These mails get sorted into
In the past on the outdated product version Uberspace 6 we encouraged users to manipulate
.qmail files for forwarding and controlling the email flow. This is technically still possible on U7 but will strongly interfere with our standard email setup that should be configured by using the
uberspace mail commands. Because of this, we no longer provide support for problems originating from customly changed
.qmail files. Please also be aware, that our setup might change in the future and break your now working custom configurations.