Solved Verzenden van het bericht is mislukt.

[Del S]

hallo

ik ben deze week van hostprovider verandert, dus het ip adres van de DA is veranderd, bijna alles werkt, ik kan mijn domeinnamen bereiken, ik ontvang mijn emails zowel pop3 als imap ik kan emails op mijn telefoon en thunderbird, ik kan emails versturen vanuit Roundcube, maar als ik via thunderbird of iphone mijn emails wil versturen lukt dit niet, bij thunderbird krijg ik de volgende foutcode:
Verzenden van het bericht is mislukt.
Het bericht kon niet worden verzonden, omdat het verbinden met uitgaande (SMTP-)server mail.mijn domain.be is mislukt. Mogelijk is de server niet beschikbaar of weigert SMTP-verbindingen. Controleer of de instellingen van uw uitgaande (SMTP-)server juist zijn en probeer het opnieuw.

Nu moet ik er wel bij vermelden dat de alias en het paswoord van de email hetzelfde was als bij de vorige instelling bij de andere hostprovider, of moet ik iets checken of instellingen veranderen in DA, heeft misschien iemand een oplossing? Alvast bedankt want ik zit er al 8 uren block op te werken

 

[Daniel_Dog]

Sorry but we cannot help you here.
This is a forum for hosting providers and license buyers of DirectAdmin.
If you need support then you will need to contact your hosting provider.

Dutch/Nederlands:
Sorry maar we kunnen je hier niet helpen.
Dit forum is alleen voor hosting providers/kopers van DirectAdmin licenties en niet voor klanten van hosting providers.
Als je ondersteuning nodig help moet je je hosting provider contacteren.

 

[Del S]

Sorry but we cannot help you here.
This is a forum for hosting providers and license buyers of DirectAdmin.
If you need support then you will need to contact your hosting provider.

Dutch/Nederlands:
Sorry maar we kunnen je hier niet helpen.
Dit forum is alleen voor hosting providers/kopers van DirectAdmin licenties en niet voor klanten van hosting providers.
Als je ondersteuning nodig help moet je je hosting provider contacteren.

Sorry verkeerd uitgedrukt ik ben van hostingsfirma veranderd van een VPS server naar een andere VPS server dus ik ben wel degene die DA licentie betaal en DA heb geinstaleerd op mijn VPS

 

[Richard G]

Denk er even aan dat dit een Engelstalig forum is dus a.u.b. alleen in Engels posten.

It's hard to do anything without the correct domain name.
If only SMTP is not working, then it looks like some local resolving issue.

Did you change all ip's to the new ip's on the server?
Are your running your own nameservers?
Does mail.mijndomein.be point to the correct ip address of the VPS?
Are the firewall ports open?

If you can't do English, contact me via pm.

 

[Del S]

Denk er even aan dat dit een Engelstalig forum is dus a.u.b. alleen in Engels posten.

It's hard to do anything without the correct domain name.
If only SMTP is not working, then it looks like some local resolving issue.

Did you change all ip's to the new ip's on the server?
Are your running your own nameservers?
Does mail.mijndomein.be point to the correct ip address of the VPS?
Are the firewall ports open?

If you can't do English, contact me via pm.

hello

i have my domain with versio.nl, i work with nameservers, like before, but i use the same own nameserver on my new vps server than i used with my old vps server, maybe thats mistake ?

Does mail.mijndomein.be point to the correct ip address of the VPS?

how i can check that?

Are the firewall ports open

on the vps are all the firewall ports open

 

[Richard G]

but i use the same own nameserver on my new vps server than i used with my old vps server, maybe thats mistake ?

No that is not per definition a mistake, but you do have to change the nameserver ip's to the new ip's if you have gotten new ip's.
In some cases you have to change those at your registrar (in your case Versio) too. Som registrars find them automatically, some you have to put the ip's for the nameservers in yourself.

how i can check that?

For example in a command prompt of your pc at home:
nslookup mail.mijndomein.be

then you should bet the correct ip as a result.

But if you can receive mail, visit your website etc. then it seems like everything is setup oke, except maybe the record for your smtp.

If you want, send me a pm with the real domain name and your vps hostname in Dutch (dus in Nederlands) and I will check for you if I can find other errors.

 

[Del S]

No that is not per definition a mistake, but you do have to change the nameserver ip's to the new ip's if you have gotten new ip's.
In some cases you have to change those at your registrar (in your case Versio) too. Som registrars find them automatically, some you have to put the ip's for the nameservers in yourself.


For example in a command prompt of your pc at home:
nslookup mail.mijndomein.be

then you should bet the correct ip as a result.

But if you can receive mail, visit your website etc. then it seems like everything is setup oke, except maybe the record for your smtp.

If you want, send me a pm with the real domain name and your vps hostname in Dutch (dus in Nederlands) and I will check for you if I can find other errors.

Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
Name: mail.domeinnaam.be thats correct
Address: and ip adress from my new also correct

but why i get on my 2 servers these notfication every day ?

This is e-mail notification to warn you that your hostname is setup improperly on your system.​

14-5-2023 00:10
strato-server.mijndomein.be, resolves to 127.0.0.1. Please make sure that your hostname resolves to your server ip or else your email may not work correctly.

but the other server no problems with send mail

and how can i solve these ?

 

[Richard G]

and how can i solve these ?

In the early days, DA created a hostname record for you. Maybe that is the reason.

But this is an easy fix. Be sure that your hostname strato-server.mijndomein.be is setup correctly in the adminstrator settings.
When that is done, go to DNS manager.

Check if there is a strato-server.mijndomein.be record. If that does not exist, create it. You can do that by creating a new DNS record in the DNS administration (so NOT in any domains dns manager but in the admin section DNS administration!!) and use there the hostname (I will use your example) strato-server.mijndomein.be and fill in the correct nameservers and the main ip of your server.
Add the record and you should be fine.

I always edit my /etc/hosts file to be sure and add my hostname like this (in your example):

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
185.xx.xx.xx strato-server.mijndomein.be strato-server

(I masked my ip etc. use your own credentials) and reboot the VPS.

Once your hostname resolves, create an SSL certificate for it.
Log in via SSH as root and do the following:

cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single strato-server.mijndomein.be 4096

In all examples mentiond here, replace ip and hostname with your own server's ip and hostname ofcourse.

 

[Del S]

In the early days, DA created a hostname record for you. Maybe that is the reason.

But this is an easy fix. Be sure that your hostname strato-server.mijndomein.be is setup correctly in the adminstrator settings.
When that is done, go to DNS manager.

Check if there is a strato-server.mijndomein.be record. If that does not exist, create it. You can do that by creating a new DNS record in the DNS administration (so NOT in any domains dns manager but in the admin section DNS administration!!) and use there the hostname (I will use your example) strato-server.mijndomein.be and fill in the correct nameservers and the main ip of your server.
Add the record and you should be fine.

I always edit my /etc/hosts file to be sure and add my hostname like this (in your example):

127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
185.xx.xx.xx strato-server.mijndomein.be strato-server

(I masked my ip etc. use your own credentials) and reboot the VPS.

Once your hostname resolves, create an SSL certificate for it.
Log in via SSH as root and do the following:

cd /usr/local/directadmin/scripts
./letsencrypt.sh request_single strato-server.mijndomein.be 4096

In all examples mentiond here, replace ip and hostname with your own server's ip and hostname ofcourse.

Yesterday i change by accident the country of my vpn connection, i see he send my emails, i try again and dont work agian, i change again my VPN country and than work again only once. these morning i disable my firewall in Direct Admin and now i can send my emails on my iphone again, thunderbird dont work yet, but thats maybe setting or re-install
But how i resolve that problem with my Firewall

 

[Richard G]

I don't know what is going on, got too little information. Maybe your ip got blocked in the firewall and then the VPN ip too?

You have to check your firewall and see if the necessery ports are open.
Check /etc/csf/csf.conf that this is set correctly:
SMTP_BLOCK = "1"
SMTP_ALLOWLOCAL = "1"
SMTP_PORTS = "25,465,587"
SMTP_ALLOWUSER = ""
SMTP_ALLOWGROUP = "mail,mailman"
SMTPAUTH_RESTRICT = "0"

Check that your ip address is in the /etc/csf/csf.ignore and /etc/csf/csf.allow files.
Or even better, set this setting like this:
IGNORE_ALLOW = "1"

Be sure the necessary ports are open, incoming and outgoing, so TCP ports 25, 110, 465,587,993 and 995.

Don't forget to restart firewall after making any changes.

Try to unblock your ip with the csf -tr and csf -dr command, just to be sure.

Check your /var/log/exim/mainlog and /var/log/exim/rejectlog files to see what is happening when you try to connect.

If you have other things running like Immunify, that can block traffic too.

 

[Del S]

Hi Richard

the problem I have and maybe stupid I don’t know where I can find these files for connecting for check an maybe resolve ! how I get acces on the ETC ? Mijn OS on the Sever is Amalux 8

 

[Richard G]

Hello Del.

I don’t know where I can find these files for connecting for check

Oke that is not stupid but probably only just lack of experience and knowledge. That can be a bit difficult when you encounter an issue.

You have to login via SSH on your server. But be *very* carefull as you can mess up things when you don't know what you're doing or how to work in console.
If you don't know how to work via console, better stay out of there and hire somebody who can. (Als je niet via console als root kunt werken, kun je er beter uit blijven en iemand huren die er wel verstand van heeft.

You have to know how to work with an editor like nano or vim in console too.

However I'm not a teacher, there are guides on the net on how to work with SSH and such things. But again... I would advise to have somebody with knowledge have a look at it.

 

[Del S]

Hello Del.

Oke that is not stupid but probably only just lack of experience and knowledge. That can be a bit difficult when you encounter an issue.

You have to login via SSH on your server. But be *very* carefull as you can mess up things when you don't know what you're doing or how to work in console.
If you don't know how to work via console, better stay out of there and hire somebody who can. (Als je niet via console als root kunt werken, kun je er beter uit blijven en iemand huren die er wel verstand van heeft.

You have to know how to work with an editor like nano or vim in console too.

However I'm not a teacher, there are guides on the net on how to work with SSH and such things. But again... I would advise to have somebody with knowledge have a look at it.

After long try and search: i find the solution Richard, first problem my firewall block my ip adress because of my thunderbird, with the latest version, i read on mozilla the new version only enable TLS or SSL connection and not STARTTLS anymore so i change all my SMTP port in thunderbird from 587 to 465 than i deleted all the blocking ip in my DA Firewall, now when i send mail under 465 port my firewall dont block my ip, or not yet, and i can send my mails again, very much thanks for the help and toughts for have any solution

 

[Richard G]

so i change all my SMTP port in thunderbird from 587 to 465

Oh why is that? Port 587 should be able to accept TLS connections.
There are providers which are all changing to TLS. I'm even wondering if Ziggo will be supporting SSL via port 465 by june 1st.

As for your ip. I would add it to the /etc/csf/csf.allow file and the /etc/csf/csf.ignore or even better, edit the csf.conf and use this setting:
IGNORE_ALLOW = "1"
and add your ip the the csf.allow anyway and also the /usr/local/directad/data//admin/ip_whitelist file. If that file is not present then create it.
At least this way you would never get blocked again.

I didn't expect the ip to get in the firewall at first because you could do lots of other things still. So good you found it.

As for the help, you're welcome.
You can find us now if you run into another issue (hopefully not) in the future.

 

[Del S]

Oh why is that? Port 587 should be able to accept TLS connections.
There are providers which are all changing to TLS. I'm even wondering if Ziggo will be supporting SSL via port 465 by june 1st.

As for your ip. I would add it to the /etc/csf/csf.allow file and the /etc/csf/csf.ignore or even better, edit the csf.conf and use this setting:
IGNORE_ALLOW = "1"
and add your ip the the csf.allow anyway and also the /usr/local/directad/data//admin/ip_whitelist file. If that file is not present then create it.
At least this way you would never get blocked again.

I didn't expect the ip to get in the firewall at first because you could do lots of other things still. So good you found it.

As for the help, you're welcome.
You can find us now if you run into another issue (hopefully not) in the future.

hello richard the problem is i dont have a static ip adres from my provider, but my VPS with Strato have these

 

[Del S]

what i also did is change te SSL certificaat from wildcard on my domein to normal SSL certificaat. dont know if that should be a reason or not

 

[Richard G]

i dont have a static ip adres from my provider,

Most of us don't, but with most providers the internet IP doesn't change often. I have Ziggo and it stays the same a long time, but official it's still a dynami address.
If you're changes more, you could make use of the no-ip.com services and then use the /etc/csf/csf.dyndns file to whitelist your ip.

As for the certificate, a wildcard certificate is better, because if you use normal now, you have to make a certicicate for www, mail, smtp etc. while when using a wildcard certificate that is done automatically and you don't need to worry about it.
However, the server needs to run own nameservers for that or LEGO needs to be installed and working.