dismail.de is a platform providing free online services based on principles of privacy, security, decentralization and freedom. All services are hosted in Germany.
- XMPP - Decentralized instant messaging
- Email - Free email accounts for your IMAP/SMTP clients or via Webinterface.
- PrivateBin - Minimalist, open source, encrypted online pastebin/discussion board
- CryptPad - End-to-end encrypte collaborative office suite
- NTP - dismail.de servers are part of the NTP Pool project
- DNS - Free DNS resolver (with ad, malware and tracking filter)
- Tor - Some of our servers are part of the Tor privacy network
- yadim - Yet another disposable mailbox
- ESEL - Email server security list
No advertising, no tracking, no profiling, no data mining, no fancy website.
2022-08-30: ntp1 - IP address has changedThe IP address of the time server at ntp1.dismail.de has changed. If you have IP addresses in your configuration (18.104.22.168; 2a02:c207:3000:6091::1), you should update them.
The new IP addresses:
The old addresses will be accessible until 2022-09-22.
2022-06-11: CryptPad - End-to-end encrypte collaborative office suite
If you do not know CryptPad, this is what the project home page says:
CryptPad is a collaborative office suite that is end-to-end encrypted. CryptPad includes all the tools needed for productive collaboration: spreadsheet, text, presentation, form, kanban, whiteboard, and more...
All data on CryptPad is encrypted in the browser. This means no readable data leaves the user's device. Even the service administrators cannot see the content of documents or user data.
Database problems, I'm working on it ... fixed.
2021-05-28: Too much, too many people, too much ... so I have decided to stop registration of new users
- Oh no, why?
It's no secret that providing dismail services is very time consuming. This is 3 hours every day for the last 6 years. Sometimes less, sometimes much more. With family, job and other commitments, this means very long days. Unfortunately, the day has a limited number of hours and so it comes (among other importent things) that I have hundreds of unanswered requests and questions in my inbox, I just don't have enough time to answer them all in a reasonable amount of time. This is frustrating for you and for me.
- When will you reopen the registration?
If I won the lottery, maybe.
- What does this mean for existing users?
Nicer services, faster response times and a better looking admin ;)
Database problems, I'm working on it ... fixed.
2020-04-28: Conversations A/V callsConversations with audio and video calls has been released. In restricted networks conversations will use dismails server to proxy the encrypted traffic. Please report any issues.
Thank you Daniel, thank you Holger and everyone involved!
2020-04-14: Scheduled maintenance on Wednesday, April 15th 5:00-7:00 UTC.Due to urgent network maintenance, the following services will not be available on Wednesday, 15th between 5:00 and 7:00 UTC
- Webservices (webmail, webchat, pastebin, trashmail)
2020-02-06: XMPP: ejabberd has been updated to 20.01
ejabberd has been updated to 20.01, please report any issues.
2020-01-25: Email aliases
In response to user requests, dismail.de now offers email aliases (up to five). To activate a new alias you have to send a request to support.
2020-01-14: The second DNS resolver is online
The second Ad-, Tracker- and Malwaredomains filtering DNS resolver is online. Please have a look for the details at the info page.
2020-01-13: XMPP message archive (MAM) policy changed
Archived XMPP messages now expire after 7 days, it was 21 days before.
2019-11-13: Some people have asked why the XMPP server was migrated to ejabberd, ...
Some people have asked why the XMPP server was migrated to ejabberd, what I liked about Prosody, why I have chosen Prosody in the first place and what I recommend for beginners - prosody or ejabberd
- Why did you choose Prosody?
For me, ejabberd had a completely confusing configuration syntax, and I felt like I was send back in time directly into sendmails m4 mess. In previous ejabberd version the configuration file was written in Erlang terms, newer versions uses Yaml configuration file format. I don't like that either, but it's not that ugly. Prosodys configuration is written in Lua, also not the kind of configuration that I like, but bearable.
So, the only reason why I had choosen Prosody, instead of ejabberd, was the less weird configuration file :)
- What do you liked about Prosody?
Prosody has reliably served dismails users for over 4 years, the developers and the community are awesome and very helpful. Prosody is written mainly in Lua. Although Lua is a great language, I am not quite sure if it is really well suited for writing a network service. But, the simplicity of Lua and the good structure of Prosodys source code helped me a lot and I will miss that.
- What do you recommend for beginners, Prosody or ejabberd?
Go with Prosody, learn some Lua, read the source code and write some usefull modules (There are too few. Not) or go with ejabberd, learn some erlang (haha), read the source code and write some usefull modules (There are too few)
Actually, I don't think it makes much of a difference. Try both, join the community conference rooms, ask some related questions and see how they react. Then choose the one that suits you best.
- Then why was the server migrated to ejabberd?
Most of dismails infrastructure is redundant, so I also want redundancy for XMPP to reduce (maintenance) downtimes. With Prosody you can do some cold standby thingy, but I don't like that and I don't like to pay for a server doing nothing most of the time. So yes, that's the main reason, and because of an annoying memory leak in Prosody, that seems to affect only a few servers.
Thank you Prosody and a big thank you to the Prosody developers.
We'll see how it goes with ejabberd ...
2019-11-04: XMPP migration is almost finished.The new nodes are up and running.
Somehow the ejabberd importer didn't imported the MUCs properly. If you are a dismail MUC Admin and don't want to wait until I have found a solution, you can "fix" it by yourself by deleting and recreating your MUC. If you need any assistance please contact me. Sorry for the inconvenience.
2019-10-28: Scheduled XMPP downtime on Sunday, November 3th 05:00-08:00 UTCThe XMPP service will be migrated from Prosody to ejabberd. During the migration XMPP and the account registration will not be available. The estimated downtime is 3 hours.
2019-10-10: Scheduled maintenance on Friday, October 11th 4:00-5:00 UTC.Due to maintenance work, the following webservices will not be available on Friday, 11th between 4:00 and 5:00 UTC
2019-08-11: Switched to a new database backendToday, the database servers has been migrated from a master-slave to a multi-master architecture (2 DB nodes + 1 quorum). Everything is working as expected, but maybe some adjustments have to be made in the next days. This shouldn't cause any issues, but who knows.
2019-07-31: XMPP - Prosody to ejabberd migrationAs first part of the long planned Prosody migration I have finally started with the evaluation and testing of ejabberd. This will take some time, as there are some dismail specific things to take into account. If I do not come across any showstoppers, Prosody will be migrated to ejabberd in a few weeks.
2019-07-24: fdns1 - some head scratchingWith the last maintenance two small nasty bugs slipped in, which made some DNS clients to fail sometimes, under some conditions.
It took me quite some time, but everything should work fine again - if not, please let me know.
2019-07-18: fdns1 - Scheduled maintenance on Friday, Jul 19th 6:30-8:30 UTC.Due to maintenance work, the DNS resolver fdns1 will not be available on Friday, 19th between 06:30 and 08:30 UTC
2019-04-25: Second MX Server is up and running
The second MX Server is up and running. With that, the whole restructuring and upgrading is mostly finished. As always, please report any issues.
2019-03-31: Scheduled XMPP downtime on Sunday, April 7th 8:00-10:00 UTC
Server migration - Part III: The XMPP service will be moved to a new server on April 7th 8:00-10:00 UTC. XMPP will not be available during the migration.
2019-03-29: Server migration - Part II
dismail's website has been moved to the new webserver (This also affects some XMPP clients which do not use XMPP SRV Records. Appropriate network rules are in place, so everything should work as usual). Additionally the xmpps address has been changed. Please report any issues.
2019-03-24: Server migration - Part I
The XMPP service will be moved to a new server. As a first step, the Webchat and the XMPP filestore has been moved to the new webserver, please report any issues.
2019-03-03: Support for TLS v1.0 and TLS v1.1 has been dropped
As announced TLS v1.0 and TLS v1.1 are no longer supported (IMAP and SMTP). If you receive errors such as "Unknown SSL protocol error in connection", please update your client.
2019-02-25: Webchat updated to converse.js v4.1.2Some Highlights - You can find more at convers.js changelog
- XEP-0384: OMEMO encrypted messaging. Please be aware that your OMEMO key is stored and generated by your webbrowser (Security considerations for browser-based crypto)
- XEP-0363: HTTP File Upload (no OMEMO)
- XEP-0308: Last Message Correction
- Support for OTR (off-the-record) encryption has been dropped, but you can use the legacy version.
2019-02-06: Support for TLS 1.0 and 1.1 is being discontinued in March 2019
dismail.de is going to drop support for TLS 1.0 and TLS 1.1 in March 2019 (IMAP and SMTP).
If you use outdated email clients or devices, please upgrade. If you are already using up-to-date email clients, you are most probably already using TLS 1.2.
2018-12-06: Prosody 0.11.1
Prosody 0.11.0 has been released on 2018-11-21 and a few days later Prosody 0.11.1
So why haven't I updated yet?
- The upgrade and migration of the mailsystem was and is very time consuming, but it's worth it.
What we have now: load-balanced, georedundent systems which I could swear are also somehow hyperconverged ;)
- I am not an early adopter. The new software release needs testing even if there are no significant changes. The running Prosody version is at a local stable maximum with some known minor issues. The new release don't has any killer feature forcing me to upgrade in a hurry.
- The upgrade will be combined with a new server and a lot of testing and this needs time.
2018-12-06: Provider maintenance work - Thursday Dec 13th 3:00-5:00 UTCXMPP: Due to maintenance in the providers Data Center there will be a short network interruption between 3:00-5:00 UTC
2018-11-25: New SMTP ServersThe new SMTP Servers are now up and running, please report any issues.
Currently you might experience connection problems to the SMTP Gateway. This could be related to the preparation of new SMTP-Servers. I'm working on it. Sorry for any inconvenience.
SMTP issue (fixed)
2018-10-23: New IMAP and DB ServersIn then next few days I will start integrating new IMAP and DB Servers. Actually they are already in sync, but there are some subsequent works to be done. Most can be done without interruption, some not (most likely you will not notice it)
2018-10-10: Scheduled maintenance on Friday, Oct 12th 6:30-8:00 UTC.Webmail will not be reachable during the maintenance.
2018-10-02: Scheduled maintenance on Thursday, Oct 4th 7:00-8:00 UTC.fdns1, privatebin and yadim will not be reachable during the maintenance.
2018-09-11: dismail.de has been added to the STARTTLS Everywhere Policy List"STARTTLS Everywhere is a project by EFF to improve the security of the email ecosystem. We want to increase and improve STARTTLS adoption and improve solutions for downgrade attacks on secure email communications."
Please report any issues.
2018-07-24: STARTTLS Everywhere Policy List enforcementOn Saturday, 28th dismail.de will start using the STARTTLS Everywhere Policy List to enforce TLS connections to all listed domains. Please report any issues.
2018-06-09: Scheduled maintenance on Wednesday, 13th 07:00 - 07:30 UTC.The XMPP service will not be available on Wednesday, 13th between 07:00 and 07:30 UTC.
2018-05-22: Die Datenschutzrichtlinie wurde aktualisiertDie Datenschutzrichtline wurde nach Vorgaben durch die EU-Datenschutz-Grundverordnung (DSGVO) aktualisiert.
2018-05-03: Webmail - Scheduled maintenance on Sunday 6th 8:00-9:00 UTCThe webmailer will be updated and will not be available on Sunday 6th 8:00-9:00 UTC.
2018-05-01: XMPP Certificate will be updated on Friday, May 4thSHA1 Fingerprint:
2018-03-19: The webmailer has been moved to a new serverThe webmailer has been moved to a new host. Please report any issues you might experience.
2018-02-15: Webchat updatedThe webchat has been updated. In addition, there is now a full screen version.
2018-02-12: Third-party request on the registration pageThere was an unnecessary third-party request for bootstrap on the registration page.
Many thanks to Mike from Kuketz IT-Security for reporting it.
2018-02-04: XMPP Certificate will be updated on Wednesday, February 7thSHA1 Fingerprint:
2017-12-26: Email provider list
- Sometimes I get asked which other mail provider I recommend. I don't want to recommend any. But here is a serverlist, please decide for yourself.
2017-12-18: OMEMO now without mutual presence subscription.
- Daniel Gultsch has developed a Prosody module that makes OMEMO available without the need of mutual presence subscription (at least with conversations).
2017-12-06: Scheduled maintenance on Sunday, December 17th 5:00-7:00 UTC.
- Mail server and XMPP server will not be available.
2017-11-12: Certificate will be updated on Wednesday, November 15thSHA1 Fingerprint:
2017-10-21: Webchat moved to subpageThe webchat has been moved to a subpage to reduce size and load time of the main page.
2017-10-11: Planned network interruption on Wednesday, October 18th between 03:00 - 05:00 UTCDue to maintenance work there will be a short (a few minutes) network interruption on Wednesday, October 18th between 03:00 - 05:00 UTC.
2017-08-25: Dear ChatSecure user ...Some ChatSecure users seem to have connectivity issues after the certificate change. Please open your account details and then "Edit Account". A popup should appear where you are asked to accept the new certificate. See also: ChatSecure issue 777
After that your ChatSecure should work as usual.