would it not be more appropriate to address your email sending? You'll never be able to list all the mail systems that *might* not work so it's probably not worth trying. It's also not easy to accommodate all the ways email goes wrong but it's easy to guess at some of them like the user entering the wrong email address or just being the sort of person who doesn't read email or won't read between you sending it and them arriving. Email will fail silently, it's a collision between some design features and the implementation some providers took.
For those reasons, you might insist leave a contact telephone number as a more pragmatic solution to listing all the email servers that your email server might not work with. You might also assume that email won't work and instead of giving warning messages which will only confuse, just put a message that the guest should print the details on the screen which *should* arrive by email later. You'll notice that this is way major brands deal with this problem - no one is going to take on the task of supporting other people's email systems or mailboxes, it's just not a good use of time.
pasochicogay wrote: ↑Fri Sep 29, 2017 6:51 pm
As soon we send an email it will not arrive in the postbox and we did not get any delivery status
That's certainly fixable, send your email through a transactional service like mailgun.
pasochicogay wrote: ↑Fri Sep 29, 2017 6:51 pm
In the moment we have a lot of trouble with ALL Microsoft Emails like hotmail, msn, live, outlook etc.
They work fine for us. The only email service I have problems with currently is yahoo and btinternet on a different system I run. The problem is with bt & yahoo, I'm not going to waste my time on it
markkinchin wrote: ↑Sat Sep 16, 2017 8:58 am
It is an interesting idea and we have added it to our list for a future update.
It would be more interesting to support the API to a service like mailgun I'd suggest.