If you want to view the log files of your mail server, you can export them via the SpaceNet Mail web interface. To do this, enter mail.yourdomain in your browser and log in with your <postmaster> account in the mail administration area.

You can download the archived files in the "Server/Logfiles" menu. The files can be viewed from the day before retrieval up to a maximum of 6 months before retrieval.

80% of your spam volume is blocked in advance before it reaches your network and burdens your mail server. We achieve this by using integrated mail and web reputation filters from IronPort. The basis for the evaluation of reputation is the IronPort SenderBase TM database - the world's largest network for monitoring global mail volumes.

IronPort is one of the world's leading providers of anti-spam business solutions. Eight of the ten largest Internet service providers in the world rely on the IronPort solution.

You can access your mails from anywhere via the SpaceNet Mail web interface. You can access your mailbox via your webmail account and your host name for SpaceNet Mail (mail.yourdomain). You will need your e-mail address and password to log in.

In order to offer you and us the best possible protection against misuse of the SpaceNet Mail mail server for spam purposes, you must have activated the "SMTP authentication" function in your e-mail programme when sending e-mails.

The reason for this is simple: Some Telekom routers (e.g. the Speedport W 724V) block the sending of e-mails by default if an e-mail provider is not on a list stored in the router.

This so-called "list of secure mail servers" is a list of authorised Telekom mail servers. If a server is not listed, this does not mean that the server is insecure.

You can solve your problem by expanding the list of "secure servers" and adding your server:

Step 1: Log in to your Speedport. To do this, enter speedport.ip in your browser.

Step 2: Now enter the password. This can be found on the back of the device. If you have assigned a different one, this will of course apply. Then click on Login.

Step 3: In the user interface, click on the "Internet" button to access the "List of secure e-mail servers" menu item.

Step 4: Click on "Enter another e-mail server" and enter your mail server (host name or IP address). Alternatively, you can also deactivate this list. To do this, simply uncheck the box "Use list of secure e-mail servers".

Step 5: You should now be able to send emails via your mail server again.

You can choose between two different incoming mail server types: POP3 or IMAP. If you access your emails on the move, IMAP has the advantage that the emails remain on the mail server and can be accessed from anywhere. With POP3, the data is retrieved from the mail server.

Switching to the SpaceNet Mail mail server is very straightforward: you simply set up your existing mailboxes with the same access data using a simple administration interface on SpaceMail and then only have to adjust the settings for the incoming and outgoing mail server. Our hotline will be happy to help you with this.

SpaceNet Mail has integrated virus protection from Sophos, which is always up to date. With the spam filter, SpaceNet Mail can filter out unwanted advertising messages. The spam filter works with state-of-the-art methods such as SenderBase

There is no limit to the number of mailboxes in SpaceNet Mail, the only limit is the size of your disc space. If the mails are not deleted and the disc space is exceeded as a result, further costs may be incurred.

In the mail administration area, you as the person responsible for mail in your company can view the individual mailboxes with the Postmaster account, as well as statistics on the individual mailboxes.

You can set up mailboxes, forwarding, autoresponders, autosignatures etc. yourself via your web interface without much effort. You can access this at: mail.yourdomain.com You can find a detailed explanation in the manual in your SpaceNet Mail under Help.

SMTP servers often return short numerical codes instead of long, detailed error messages. These are intended for system administrators and technicians and are deliberately kept short and unambiguous. This information is not always useful for end users.

These numerical codes are universal codes that are used by every mail server (Linux, Exchange, etc.). This means that there can be no misunderstandings regarding communication between the various mail servers.

Each digit of the SMTP code has a different function and meaning.

Error numbers of 4xx indicate temporary errors, for example due to maintenance work.

Error numbers of 5xx are permanent errors that can be caused by misconfiguration or a lack of action. In these cases, you should notify the responsible system administrator.

Here you will find an overview of codes, the corresponding problem and the solution

• Code 421

  Problem: Mail server is not available - delivery cancelled.
  Solution: Try again later. Alternatively: Notify the responsible system administrator.

• Code 450
  Problem: User's mailbox is not available.
  Solution: Try again later. Alternative: Use a different e-mail address for the mailbox as the recipient.
• Code 451
  Problem: Cancellation due to a server error
  Solution: Try again later. Alternative: Notify the responsible system administrator.
• Code 451 4.1.8
  Problem: Domain of the sender address cannot be resolved
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 451 5.1.8
  Problem: Domain of the sender address does not exist
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 451 5.5.4
  Problem: Sender address requires a domain
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 452
  Problem: The server does not have enough memory to perform the task
  Solution: Notify the responsible system administrator
• Code 452 4.1.8
  Problem: Domain of the sender address cannot be resolved
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 452 5.1.8
  Problem: Domain of the sender address does not exist
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 452 5.5.4
  Problem: Sender address requires a domain
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 452 5.7.1
  Problem: DMARC verification not possible
  Solution: The mailbox of the user you are trying to write to rejects unauthenticated emails.
• Code 500
  Problem: Syntax error in the command
  Solution: Try a different e-mail programme. Alternatively: Inform the responsible system administrator.
• Code 501
  Problem: Syntax error in the command argument
  Solution: Try a different e-mail programme. Alternative: Notify the responsible system administrator.
• Code 502
  Problem: Command is not implemented
  Solution: Notify the responsible system administrator.
• Code 503
  Problem: Error in the command sequence
  Solution: Try a different e-mail programme.
• Code 504
  Problem: Command parameter is not implemented
  Solution: Notify the responsible system administrator.
• Code 550
  Problem: User mailbox not available
  Solution: The mailbox of the user you are trying to write to either does not exist or your message has been rejected.
• Code 550 4.7.1
  Problem: Non DMARC authenticated mails are forbidden
  Solution: The mailbox of the user you want to write to rejects unauthenticated emails.
• Code 550 5.7.1
  Problem: Access to send messages to this email system has been denied
  Solution: The mailbox of the user you are trying to write to is rejecting your emails. Your server may be on a blacklist.
• Code 551
  Problem: Recipient is not on this server. Your message must be forwarded.
  Solution: Try a different e-mail programme or check your mail settings.
• Code 552
  Problem: The recipient's mailbox is full.
  Solution: Inform the recipient in another way or try at a later time.
• Code 553
  Problem: Mailbox name is invalid
  Solution: Check that the recipient's address is correct
• Code 553 4.1.8
  Problem: Domain of the sender address cannot be resolved
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 553 5.1.8
  Problem: Domain of the sender address does not exist
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 553 5.5.4
  Problem: Sender address requires a domain
  Solution: Check whether the SMTP server has a valid "A" "MX" and "Reverse" record.
• Code 554
  Problem: Transmission failed
  Solution: Check your details and settings. Alternatively: Contact your system administrator
• Code 554
  Problem: Your access to this mail system has been rejected due to the sendig MTA's poor reputation.
  Solution: The sending server is on the blacklist of www.senderbase.org. It must be ensured that no spam was/is sent from there so that the reputation is normalised again.

No, no emails can be deleted. Long-term archiving is audit-proof, so it is not possible to manipulate or delete emails at a later date.

The SpaceNet mail archive stores all e-mails that are sent via the SpaceNet mail server.

Yes, if you use the SpaceNet Mail Server as your outgoing mail server and have logged in to SpaceNet Mail using SMTP authentication.

The user data is the same as for your SpaceNet Mail account. The only difference is the incoming mail server - this is: mailvault.yourdomain.com. You must set up your own separate IMAP mailbox to use it.

They can either be retrieved via IMAP or you can search for specific criteria via the mail administration, which can be accessed at mail.yourhostname.com, under the menu item "Archive".