With the Default address In cPanel, you define what happens to emails sent to a non-existent address on your domain.
For example, if a message is sent to verkuaft@deine-domain.ch sent, although this address does not exist, the default address configuration determines how the mail server handles this message.
In this guide, we will show you how to configure the default address in your CURIAWEB cPanel, what options are available, and why a classic Catch-All is not the best choice for many domains.
Briefly explained: The default address is not a normal email address. It defines how the mail server handles messages for which there is no matching recipient within your domain.
What is a default address? #
Various regular email accounts and forwarders can be set up for a domain.
For example:
info@deine-domain.ch
verkauf@deine-domain.ch
rechnung@deine-domain.ch
What happens to a message to:
irgendetwas@deine-domain.ch
if this address has not been set up?
That is exactly what the default address is for.
What does catch-all mean? #
In a so-called Catch-All are messages to non-existent recipients of a domain forwarded to a designated email address.
Assuming that as a catch-all destination:
info@deine-domain.ch
determined.
Then messages to unconfigured addresses like:
asdf@deine-domain.ch
or:
falscher-name@deine-domain.ch
end up in the defined target mailbox.
That sounds convenient at first, but it has significant disadvantages.
Why a catch-all can be problematic #
With a catch-all domain, spammers do not need to know an actually existing email address.
You can send messages to randomly generated recipient names, and depending on the rest of the mail and spam configuration, they will still be processed by the catch-all.
As a result, a catch-all can generate an unnecessarily large number of unwanted messages or forward them to the target mailbox.
Recommendation: For business-related addresses, prefer using specifically created email accounts or forwards. A catch-all should only be activated if you have a specific reason for it and understand the consequences.
1. Open default address in cPanel #
Log in to your CURIAWEB cPanel.
Scroll to the section on the homepage Email and click on Default address.
Here you can configure how messages to invalid or non-existent recipients of your domain are handled.
2. Choose the correct domain #
If multiple domains are set up in your hosting account, first select the domain whose default address you want to configure.
The setting for:
your-domain.ch
is not automatically the same as for:
zweite-domain.ch
Attention: Check the selected domain before each change. The catch-all address can affect the handling of all non-existent recipient addresses for this domain.
3. Decide how to handle unknown recipients #
cPanel offers various options for the default address. Which exact labels and advanced options are displayed may depend on the server configuration.
For most applications, two basic variants are particularly important:
- Reject messages to non-existent recipients with an error message
- Forward messages to another email address
The correct setting depends on whether you intentionally want to use a catch-all.
Option 1: Reject unknown recipients #
If you don't need a catch-all, it usually makes sense not to simply redirect messages to non-existent recipients into another mailbox.
cPanel offers an option for this, where the sender receives an error message or the message is rejected accordingly.
This sends a message, for example, to:
inof@deine-domain.ch
not easy on info@deine-domain.ch delivered, if enough is not even set up as an address.
Instead, the message is treated as addressed to an invalid recipient.
Advantage: Randomly invented recipient addresses are not automatically collected in a central mailbox. This reduces, in particular, the unwanted mail traffic that can be caused by a catch-all.
4. Set error message for unknown recipients #
When you use the error message return option, cPanel can provide a field for the corresponding error text, depending on the interface.
For normal applications, no complicated custom text is required.
The crucial point is that the sender or their mail server can recognize that the specified recipient does not exist.
Change such technical messages only if you have a specific reason to do so.
5. Save setting #
Double-check the selected domain and the desired handling of unknown recipients.
Then save the setting using the corresponding button.
The new default address or treatment of unknown recipients is subsequently configured for the domain in question.
6. Test rejection with a non-existent address #
If you want to check whether unknown recipients are actually rejected, you can send a message from an external email address to an intentionally non-existent address.
For example:
test-adresse-die-nicht-existiert@deine-domain.ch
Use a name for which you are certain that neither an email account nor a forwarding address or other matching configuration exists.
Depending on the mail servers involved, the external sender may subsequently receive a non-delivery report.
Important: Do not use an address for such a test that may have been set up as a forward or through another email rule. Otherwise, you are not exclusively testing the behavior of the default address.
Option 2: Forward catch-all to an email address #
If you want to consciously forward all messages to non-existent recipients of a domain to a specific address, you can use the corresponding forwarding option of the default address.
For example, the objective could be:
info@deine-domain.ch
This makes this mailbox the destination for messages for which there is no specific recipient.
7. Enter catch-all destination address #
Select the option to forward to an email address and enter the complete destination address.
For example:
info@deine-domain.ch
Check the destination address carefully and then save the setting.
Attention: With a catch-all, the destination mailbox can receive significantly more messages. This can include spam, messages to invented addresses, and emails to misspelled recipients.
8. Catch-All testing #
Send a test message from an external address to an address on your domain that definitely does not exist as a regular email account or forwarder.
For example:
catchall-test-8472@deine-domain.ch
Then check whether the message arrives at the defined catch-all destination.
This allows you to check whether the default address is working as intended.
A catch-all is not the same as a normal forwarding address #
A standard email forwarding rule applies to a specifically defined address.
For example:
verkauf@deine-domain.ch → info@deine-domain.ch
This rule specifically concerns verkauf@deine-domain.ch.
A catch-all, on the other hand, handles messages sent to recipients for whom no specific address or corresponding rule exists.
We show you how to set up targeted redirects at Set up email forwarding in cPanel.
Why targeted redirections are usually better #
If you know which additional addresses are needed, you can configure them specifically.
Do you need, for example:
bewerbung@deine-domain.ch
and want all incoming messages there at:
info@deine-domain.ch
received, can you set up a forwarding exactly for this address.
This does not simultaneously accept messages to arbitrary invented addresses either.
Catch-All does not reliably protect against typos #
A common argument in favor of catch-all is that messages are not lost despite misspelled recipient addresses.
This is generally true for certain typos within the local part of a domain. Nevertheless, a catch-all is not always the best solution for this.
On the one hand, the volume of spam is increasing. On the other hand, typos can also occur elsewhere, for example in the domain itself.
From:
info@deine-domain.ch
could, for example, accidentally:
info@deine-doman.ch
become.
A catch-all for your-domain.ch cannot catch an error in a completely different domain.
Catch-all can even let errors go unnoticed for longer #
If any address is accepted, a sender may not notice a typo.
A misspelled address like:
rechnug@deine-domain.ch
can still end up at the catch-all destination.
The sender may continue to use the same incorrect address in the future because they have never received an error message.
With a clean rejection, on the other hand, the sender recognizes that the recipient address used is not valid.
Catch-all and spam #
Spammers often use automatically generated recipient names.
With a domain without catch-all, messages to non-existent addresses can be rejected accordingly.
When catch-all is enabled, on the other hand, significantly more of these messages can make it through to further email and spam processing.
This can place an unnecessary load on the destination mailbox.
We show how to configure the cPanel spam filters under Configure spam filter in cPanel.
Practical Tip: If a catch-all mailbox suddenly starts receiving a lot of spam, you shouldn't just try to filter it increasingly aggressively. First, check whether you actually need the catch-all at all.
Catch-All and Storage Space #
If the default address forwards messages to a regular mailbox and a very large amount of unwanted email arrives there, this can also increase storage consumption.
Especially in mailboxes that are not checked for a long time, large amounts of unwanted messages can accumulate.
You can check the storage usage of your email accounts using the corresponding cPanel features. We show you how to do this under Check and clean up email storage in cPanel.
Forward Catch-All to an external address #
Technically, an external email address can also be used as the destination for a redirection under certain circumstances.
This should be considered with particular care.
A catch-all can already accept large volumes of unwanted messages. If these are additionally forwarded to an external provider, a more complex delivery path is created.
External mail providers perform their own spam and authentication checks. Forwarded messages may therefore be treated differently than directly delivered emails.
Recommendation: A catch-all with subsequent forwarding to an external mail provider should not be the standard solution for a business domain. Use clearly defined mailboxes and targeted mail routes wherever possible.
What does „discard“ mean? #
Depending on the cPanel configuration, additional options for handling unknown recipients may be offered under the advanced options.
This may also include a variant in which messages are discarded.
You should distinguish between an explicit rejection and a silent dismissal.
In the event of a rejection, the sending mail server learns that the message was not accepted. With silent dropping, on the other hand, the message can be removed without the sender being informed of the non-delivery in the same way.
Attention: Silent dropping can be problematic for legitimate messages because the sender may assume that their message was successfully delivered.
Why a rejection is often cleaner than quietly discarding #
If an address does not exist, a clear technical rejection is often more transparent.
The sender or their mail server then receives the information that the message could not be delivered to the specified recipient.
With a legitimate sender, this at least provides the opportunity to recognize the mistake and use the correct address.
Default address and existing email accounts #
The standard address is not intended to replace existing regular mailboxes.
For example, does exist:
info@deine-domain.ch
As a properly configured email account, a message sent to this address will be processed according to the normal mail configuration.
The default address becomes relevant for messages for which there is no matching recipient.
Default address and email filter #
Email filters and the default address serve different purposes.
The default address handles non-existent recipients. Filters, on the other hand, process messages based on specific conditions.
With a filter, for example, you can process messages based on sender, subject, or other criteria.
We show how to set up such rules at Create and manage email filters in cPanel.
Test standard address after changes #
After every change, you should test the configuration with an external email address.
In the event of a rejection, you send a message to a guaranteed non-existent recipient and check the expected error behavior.
With a catch-all, you also send to a non-existent address and check whether the message arrives at the intended destination.
Also test an actually existing address on your domain. This ensures that normal email traffic continues to work.
Unknown recipients are still accepted #
Wenn eine Nachricht an eine vermeintlich nicht vorhandene Adresse trotzdem zugestellt wird, prüfe zuerst, ob für diese Adresse möglicherweise bereits eine Weiterleitung oder andere passende E-Mail-Konfiguration existiert.
Kontrolliere außerdem die aktuelle Standardadresse der richtigen Domain.
Bei unklarem Verhalten kannst du mit der cPanel-Funktion Zustellung nachverfolgen untersuchen, wie eine konkrete Nachricht verarbeitet wurde.
We explain the procedure under Track email delivery in cPanel.
Nachricht an gültige Adresse wird abgewiesen #
Wenn eine tatsächlich vorhandene E-Mail-Adresse keine Nachrichten empfängt, solltest du nicht vorschnell die Standardadresse ändern.
Die Standardadresse ist primär für nicht vorhandene Empfänger relevant.
Prüfe bei einem bestehenden Postfach stattdessen, ob das Konto korrekt eingerichtet ist, ausreichend Speicher besitzt und ob die Nachricht im Zustellungsprotokoll erscheint.
Wie du bestehende Konten verwaltest, zeigen wir unter Manage or delete email account in cPanel.
Wann ist ein Catch-All trotzdem sinnvoll? #
Es gibt Situationen, in denen ein Catch-All bewusst eingesetzt werden kann.
Das kann beispielsweise bei einer speziell geplanten E-Mail-Struktur der Fall sein, bei der variable Empfängeradressen gezielt verwendet und anschließend durch andere Systeme verarbeitet werden.
In solchen Fällen sollte der Betreiber jedoch wissen, warum das Catch-All benötigt wird und wie Spam, Speicherung und weitere Verarbeitung kontrolliert werden.
Für eine normale Unternehmensdomain mit einigen klar definierten Adressen ist ein Catch-All dagegen meist nicht erforderlich.
Empfohlene Struktur für normale Unternehmensdomains #
Für die meisten kleineren und mittleren Websites ist eine übersichtliche Struktur sinnvoller als ein globales Catch-All.
Erstelle echte Postfächer für Personen oder Funktionen, die ein eigenes Postfach benötigen.
Verwende gezielte Weiterleitungen für zusätzliche Adressen, die bei einem bestehenden Postfach ankommen sollen.
Adressen, die nicht existieren, können anschließend sauber als unbekannte Empfänger behandelt werden.
Damit bleibt nachvollziehbar, welche E-Mail-Adressen tatsächlich verwendet werden.
Basic rule: Nur die Adressen annehmen, die du tatsächlich verwenden möchtest, ist meist sauberer als jede beliebige Adresse deiner Domain über ein Catch-All einzusammeln.
Typische Fehler bei der Standardadresse #
Ein häufiger Fehler besteht darin, Catch-All vorsorglich zu aktivieren, obwohl es überhaupt nicht benötigt wird. Das Ergebnis zeigt sich später oft durch unnötig viel Spam.
Ebenso problematisch ist eine falsch geschriebene Catch-All-Zieladresse oder eine Änderung an der falschen Domain.
Auch die Annahme, eine Standardadresse sei dasselbe wie ein normales E-Mail-Konto, führt zu Missverständnissen.
Schließlich sollte eine Nachricht nicht ohne guten Grund still verworfen werden, wenn eine klare Ablehnung für legitime Absender hilfreicher wäre.
Summary #
Die Standardadresse findest du in deinem CURIAWEB-cPanel unter E-Mail → Standardadresse.
Sie bestimmt, wie der Mailserver Nachrichten an nicht vorhandene Empfänger einer Domain behandelt.
Für die meisten normalen Unternehmensdomains ist es sinnvoll, gültige E-Mail-Adressen gezielt als Postfach oder Weiterleitung einzurichten und Nachrichten an unbekannte Empfänger entsprechend abzulehnen.
Ein Catch-All kann zwar Tippfehler im Empfängernamen auffangen, nimmt aber potenziell auch Nachrichten an beliebige erfundene Adressen an. Dadurch kann das Spamaufkommen erheblich steigen.
Wenn du die Standardadresse änderst, kontrolliere deshalb zuerst die richtige Domain und teste anschließend sowohl eine absichtlich nicht vorhandene als auch eine tatsächlich vorhandene E-Mail-Adresse.
