What can you do to prevent other people from sending spam e-mails using your e-mail address as sender address?
The answer is: Nothing, regrettably. In the same way as you cannot prevent other people writing your address onto a paper envelope and post the letter.
But: You can do something in order to help recipients to reject mails, which were not really sent by you! One useful method if SPF (Sender policy framework). Summarized SPF works like this: You add some information to your domain defining which mail servers you want to authorize as legal sources for your e-mails. The recipient can evaluate this information and reject e-mails or mark them as spam, which have your sender address but were not sent from mail servers authorized by you.
Well, the recipient may use this information, he is not obliged to do so. But an increasing number of recipients use this method and reject e-mails, which were sent from other mail servers than those authorized by you.
How to enter SPF information for your domain? Very simple:
- Log in at www.delink.biz using your customer login data
- Go to DOMAINS -> Manage and click the DNS button next to your domain
- Enter the following data at Add new subdomain/service
Subdomain/Service: – leave this field empty –
Type: Select TXT
TTL: – leave this field empty –
Target: v=spf1 include:spf.delink.de -all
To finish click Add and then Save changes. Approximately 10 minutes later the SPF record for your domain will become public, and the method starts to work.
The above entry is correct in case you are sending e-mails with your domain as sender address solely via the deLink mail system. If you are sending e-mails via other systems as well (e.g. a local mail server, via a newsletter provider) you have to add these mail servers to the SPF record.
Currently many domain owners are receiving faked e-mails informing about an alleged suspension of their domain. These mails are looking authentic, because
- as sender deLink or another, really existing registrars is indicated
- the e-mail adress of the recipient is correct
- the personal name is correct
- the domain really belongs to the recipient
Obviously the data was grabbed from the public domain whois. The content of the e-mail is similar to this:
Dear John Doe,
The Domain Name yourdomain.com have been suspended for violation of the deLink GmbH Abuse Policy.
Multiple warnings were sent by deLink GmbH Spam and Abuse Department to give you an opportunity to address the complaints we have received.
We did not receive a reply from you to these email warnings so we then attempted to contact you via telephone.
We had no choice but to suspend your domain name when you did not respond to our attempts to contact you.
Click here and download a copy of complaints we have received.
These e-mails are FAKED.
If you click the proposed link, you will very probably get a trojan onto your device. In case of doubt please forward the e-mail to us, we will analyze it and give you a feedback.
Since many months the value of the EURO has been losing against the US Dollar, dramatically in the last few weeks. Most domain registries charge their fees in US Dollar. We did not forward the recent price increases by VeriSign and other registries to our customers.
But now the exchange rates are forcing us to increase the prices for several TLDs which are charged in US Dollar or GBP, coming into effect at the 1st of February 2015. The increase applies mostly to the higher discount rates and is kept at the possible minimum. Each customer will receive an individual e-mail with an exact listing of all changes concerning him.
The good news: The prices for several TLDs (where registries charge in EURO) will be reduced at the same time!
Everyone is talking about it: Who can read which of all the data transmitted via internet?
If you manage your e-mails via deLink you can make it a lot more difficult for unwanted eavesdroppers to read your e-mails: Use encrypted transmission from and to the deLink mail system!
The mail servers at deLink allow encrypted transmission from today. You have the choice – if you want to apply enhanced security, you only have to tell your e-mail client (OutLook, Thunderbird, MacMail … whatever you use) to do so: Replace the names of your incoming e-mail servers (POP3, IMAP) and outgoing e-mail server (SMTP) as follows:
– until now mail.<mydomain> (<mydomain> to be replaced by your individual domain name)
– new mail.delink-ssl.net
and activate encryption in your e-mail client. Please refer to the e-mail clients documentation to find out how to do this.
Webmail and e-mail administration can be processed encrypted as well. Just use
http://admin.delink.email for e-mail administration
http://delink.email for webmail
You will be forwarded to a secure connection. Your login data for e-mail client, mail administration and webmail remain unchanged.
The September patchday updates by Microsoft have changed the behaviour of several e-mail clients: OutLook Express, OutLook, Live Mail, MailDroid and perhaps others. The result: Retrieving and sending e-mail via the deLink mail system is possibly no longer working. Unfortunately in some cases not even an error message appears, e.g. with Live Mail in Windows 8.
During connection the client checks whether a certificate is installed for the domain which is used to address the mail server. If there is no certificate, e-mail will not be retreived or sent.
In the settings of your e-mail client replace the name of the mail server, which is mail.<mydomain> following our recommendation (<mydomain> stands for your individual domain name), by
as well for the incoming mail server (POP3 und IMAP) and for the outgoing mail server (SMTP). You may activate SSL encryption at the same time using the follwing settings
Outgoing mail server (SMTP) mail.delink-ssl.net Port 465
Incoming mail server (POP3) mail.delink-ssl.net Port 995
Incoming mail server(IMAP) mail.delink-ssl.net Port 993
With these values set e-mail will function as usual again.