jimimaseye wrote: ↑2018-12-21 11:05Do this
run this run this and post the results: viewtopic.php?f=20&t=30914
.
.
.
And post the results in text form
Problem to setup
- jimimaseye
- Moderator
- Posts: 10060
- Joined: 2011-09-08 17:48
Re: Problem to setup
5.7 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829
Re: Problem to setup
Sorry, I do not see your screenshot.
Any example to have 2 ports together, for SMTP.
Any example to have 2 ports together, for SMTP.
Re: Problem to setup
In my previous post, there waa a screenshot, lookitup and take a look at it, it has redmarkings for SSL assignment but you can also see the Ports i had setup.
You need port
25 SMTP with STARTTLS optional
and
587 SMTP with STRTTLS required
I dont know howto explain it simpler to you, because i mentioned it repeatedly in other posts but your doesnt understand it or refuse to do it.
You need port
25 SMTP with STARTTLS optional
and
587 SMTP with STRTTLS required
I dont know howto explain it simpler to you, because i mentioned it repeatedly in other posts but your doesnt understand it or refuse to do it.
Re: Problem to setup
Can you show your entire hosts file
To be honest, I don't think that you meet the technical knowledge component required to run a mail server, and that you should uninstall hmailserver before some spammer takes control of it
See the bottom of this page >> https://www.hmailserver.com/documentati ... quirements
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation
https://www.hmailserver.com/documentation
Re: Problem to setup
Hi,
There is only one line like
There is only one line like
I tried to stop the action of spammers and how to identify reason of issue below?127.0.0.1 smtp.SearchHouseLive.com
Re: Problem to setup
It is now fine to send out messages. Before this, it was also fine to send out messages.
Re: Problem to setup
/Case closed
We solved the Problem in a Teamviewer session.
Main Problem was
The User is running Active Directory on the same Computer as hMailServer, which has setup a Primary Domain Forrest with its own
Microsoft DNS-Server. The Installation Assistant of Active Directory added Microsrofts DNS-Server as primary DNS-Server but the User
purchased a external Webhostingpackage which had exactly the same DNS name as the Active Directoy Domain
For example:
Instead of using the Broadband DSL/Cable-Routers DNS-Server or Googles public DNS-Server (IP: 8.8.8. it pointed to itself
to local loopback Adapter (127.0.0.1) which of cause responded to DNS entries about the local Active Directory DNS-Domain
but doesnt know anything about the external, outside Webhosting package on the Internet.
The Solution was to add the Googles Public DNS-Server (IP 8.8.8. first in order and secondary the local Active Directory
MS-DNS-Server with Ip address (127.0.0.1) to make sure Active Directory doesnt fail.
After this, the missing MX Record of the external Webhosting Package DNS-Server could be resolved.
Additional, the Ports 25 (STARTTLS optional) and 587 and Port 143 (with Port STARTTLS Required) had to be opened by the
Windows Firewall and that it was.
User is happy and hMailServer is up and running.
We solved the Problem in a Teamviewer session.
Main Problem was
The User is running Active Directory on the same Computer as hMailServer, which has setup a Primary Domain Forrest with its own
Microsoft DNS-Server. The Installation Assistant of Active Directory added Microsrofts DNS-Server as primary DNS-Server but the User
purchased a external Webhostingpackage which had exactly the same DNS name as the Active Directoy Domain
For example:
Instead of using the Broadband DSL/Cable-Routers DNS-Server or Googles public DNS-Server (IP: 8.8.8. it pointed to itself
to local loopback Adapter (127.0.0.1) which of cause responded to DNS entries about the local Active Directory DNS-Domain
but doesnt know anything about the external, outside Webhosting package on the Internet.
The Solution was to add the Googles Public DNS-Server (IP 8.8.8. first in order and secondary the local Active Directory
MS-DNS-Server with Ip address (127.0.0.1) to make sure Active Directory doesnt fail.
After this, the missing MX Record of the external Webhosting Package DNS-Server could be resolved.
Additional, the Ports 25 (STARTTLS optional) and 587 and Port 143 (with Port STARTTLS Required) had to be opened by the
Windows Firewall and that it was.
User is happy and hMailServer is up and running.