cant really figure it out.
I just reinstalled and Market is working again..

When I click on MarketPlace App page pops up for sec and then goes to webpage

Market page pops up for about 5 sec then goes to web page in chrome.

Sorry, the page you were looking for does not exist or is not available. We performed a web search for “ Marketplace” and here's what we found.

You need to put the uverse modem in bridge mode and let clearos take care of the firewall.

I will check in to the jail.local file and try setting the default max try to 3 and see what happens.

Thanks for the reply.

Merry Christmas.

Here some more logs from failtoban.

Same Ip's 91.200 still not banned.

016-12-24 09:46:03,906 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 09:55:29,093 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:04:55,831 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:14:18,209 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:23:45,221 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:30:35,719 fail2ban.filter [2388]: INFO [postfix-sasl] Found 80.82.77.83
2016-12-24 10:33:10,111 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:35:23,331 fail2ban.filter [2388]: INFO [postfix-sasl] Found 195.22.126.189
2016-12-24 10:42:38,876 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 10:52:04,747 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:01:32,891 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:10:57,444 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:20:23,320 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:24:28,181 fail2ban.filter [2388]: INFO [postfix-sasl] Found 80.82.77.83
2016-12-24 11:29:45,723 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:39:13,256 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 11:48:37,463 fail2ban.filter [2388]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-24 12:14:42,429 fail2ban.server [2388]: INFO Stopping all jails
2016-12-24 12:14:42,542 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- stdout: ''
2016-12-24 12:14:42,542 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- stderr: "iptables v1.4.21: Couldn't load target `f2b-postfix-sasl':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\niptables: No chain/target/match by that name.\niptables: No chain/target/match by that name.\n"
2016-12-24 12:14:42,543 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- returned 1
2016-12-24 12:14:42,543 fail2ban.actions [2388]: ERROR Failed to stop jail 'postfix-sasl' action 'iptables-multiport': Error stopping action
2016-12-24 12:14:43,368 fail2ban.jail [2388]: INFO Jail 'postfix-sasl' stopped
2016-12-24 12:14:43,541 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd
iptables -w -F f2b-sshd
iptables -w -X f2b-sshd -- stdout: ''
2016-12-24 12:14:43,541 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd
iptables -w -F f2b-sshd
iptables -w -X f2b-sshd -- stderr: "iptables v1.4.21: Couldn't load target `f2b-sshd':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\niptables: No chain/target/match by that name.\niptables: No chain/target/match by that name.\n"
2016-12-24 12:14:43,542 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd
iptables -w -F f2b-sshd
iptables -w -X f2b-sshd -- returned 1
2016-12-24 12:14:43,542 fail2ban.actions [2388]: ERROR Failed to stop jail 'sshd' action 'iptables-multiport': Error stopping action
2016-12-24 12:14:44,369 fail2ban.jail [2388]: INFO Jail 'sshd' stopped
2016-12-24 12:14:44,539 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd-ddos
iptables -w -F f2b-sshd-ddos
iptables -w -X f2b-sshd-ddos -- stdout: ''
2016-12-24 12:14:44,540 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd-ddos
iptables -w -F f2b-sshd-ddos
iptables -w -X f2b-sshd-ddos -- stderr: "iptables v1.4.21: Couldn't load target `f2b-sshd-ddos':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\niptables: No chain/target/match by that name.\niptables: No chain/target/match by that name.\n"
2016-12-24 12:14:44,540 fail2ban.action [2388]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports ssh -j f2b-sshd-ddos
iptables -w -F f2b-sshd-ddos
iptables -w -X f2b-sshd-ddos -- returned 1
2016-12-24 12:14:44,540 fail2ban.actions [2388]: ERROR Failed to stop jail 'sshd-ddos' action 'iptables-multiport': Error stopping action
2016-12-24 12:14:45,371 fail2ban.jail [2388]: INFO Jail 'sshd-ddos' stopped
2016-12-24 12:14:45,376 fail2ban.server [2388]: INFO Exiting Fail2ban
2016-12-24 12:14:49,750 fail2ban.server [6221]: INFO Changed logging target to /var/log/fail2ban.log for Fail2ban v0.9.5
2016-12-24 12:14:49,751 fail2ban.database [6221]: INFO Connected to fail2ban persistent database '/var/lib/fail2ban/fail2ban.sqlite3'
2016-12-24 12:14:49,753 fail2ban.jail [6221]: INFO Creating new jail 'sshd'
2016-12-24 12:14:49,769 fail2ban.jail [6221]: INFO Jail 'sshd' uses systemd
2016-12-24 12:14:49,790 fail2ban.jail [6221]: INFO Initiated 'systemd' backend
2016-12-24 12:14:49,792 fail2ban.filter [6221]: INFO Set maxRetry = 5
2016-12-24 12:14:49,793 fail2ban.actions [6221]: INFO Set banTime = 86400
2016-12-24 12:14:49,793 fail2ban.filter [6221]: INFO Set findtime = 600
2016-12-24 12:14:49,794 fail2ban.filter [6221]: INFO Set maxlines = 10
2016-12-24 12:14:49,874 fail2ban.filtersystemd [6221]: INFO Added journal match for: '_SYSTEMD_UNIT=sshd.service + _COMM=sshd'
2016-12-24 12:14:49,885 fail2ban.jail [6221]: INFO Creating new jail 'sshd-ddos'
2016-12-24 12:14:49,885 fail2ban.jail [6221]: INFO Jail 'sshd-ddos' uses systemd
2016-12-24 12:14:49,886 fail2ban.jail [6221]: INFO Initiated 'systemd' backend
2016-12-24 12:14:49,887 fail2ban.filter [6221]: INFO Set maxRetry = 5
2016-12-24 12:14:49,888 fail2ban.actions [6221]: INFO Set banTime = 86400
2016-12-24 12:14:49,888 fail2ban.filter [6221]: INFO Set findtime = 600
2016-12-24 12:14:49,891 fail2ban.filtersystemd [6221]: INFO Added journal match for: '_SYSTEMD_UNIT=sshd.service + _COMM=sshd'
2016-12-24 12:14:49,902 fail2ban.jail [6221]: INFO Creating new jail 'postfix-sasl'
2016-12-24 12:14:49,902 fail2ban.jail [6221]: INFO Jail 'postfix-sasl' uses systemd
2016-12-24 12:14:49,903 fail2ban.jail [6221]: INFO Initiated 'systemd' backend
2016-12-24 12:14:49,904 fail2ban.filter [6221]: INFO Set maxRetry = 5
2016-12-24 12:14:49,905 fail2ban.actions [6221]: INFO Set banTime = 86400
2016-12-24 12:14:49,906 fail2ban.filter [6221]: INFO Set findtime = 600
2016-12-24 12:14:49,911 fail2ban.filtersystemd [6221]: INFO Added journal match for: '_SYSTEMD_UNIT=postfix.service'
2016-12-24 12:14:49,924 fail2ban.jail [6221]: INFO Jail 'sshd' started
2016-12-24 12:14:49,928 fail2ban.jail [6221]: INFO Jail 'sshd-ddos' started
2016-12-24 12:14:49,939 fail2ban.jail [6221]: INFO Jail 'postfix-sasl' started
2016-12-24 12:18:09,078 fail2ban.filter [6221]: INFO [postfix-sasl] Found 80.82.77.83

Attack Detector post-sasl

I think im having a problem with smtp part of Attack detector. Checking the the mail logs shows a bunch of ips trying to hack email server.
Checking the fail to ban logs and it shows the the ips that are trying to hack the email server and tries to ban those ips but then shows an error.

26]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 01:35:41,042 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 01:45:09,110 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 01:54:34,104 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:04:00,022 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:13:25,322 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:22:54,790 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:32:23,477 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:41:51,906 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 02:46:32,904 fail2ban.filter [2126]: INFO [postfix-sasl] Found 80.82.77.83
2016-12-20 02:51:16,842 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:00:45,832 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:10:09,802 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:19:40,984 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:29:05,128 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:38:36,840 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:48:04,210 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 03:57:39,687 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:07:08,204 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:16:39,563 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:18:55,533 fail2ban.filter [2126]: INFO [postfix-sasl] Found 80.82.77.83
2016-12-20 04:26:04,696 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:35:33,684 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:45:02,503 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 04:51:03,811 fail2ban.actions [2126]: NOTICE [postfix-sasl] Unban 108.35.48.154
2016-12-20 04:51:03,919 fail2ban.action [2126]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-postfix-sasl[ \t]' -- stdout: ''
2016-12-20 04:51:03,919 fail2ban.action [2126]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-postfix-sasl[ \t]' -- stderr: ''
2016-12-20 04:51:03,919 fail2ban.action [2126]: ERROR iptables -w -n -L INPUT | grep -q 'f2b-postfix-sasl[ \t]' -- returned 1
2016-12-20 04:51:03,920 fail2ban.CommandAction [2126]: ERROR Invariant check failed. Trying to restore a sane environment
2016-12-20 04:51:04,025 fail2ban.action [2126]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- stdout: ''
2016-12-20 04:51:04,025 fail2ban.action [2126]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- stderr: "iptables v1.4.21: Couldn't load target `f2b-postfix-sasl':No such file or directory\n\nTry `iptables -h' or 'iptables --help' for more information.\niptables: No chain/target/match by that name.\niptables: No chain/target/match by that name.\n"
2016-12-20 04:51:04,025 fail2ban.action [2126]: ERROR iptables -w -D INPUT -p tcp -m multiport --dports smtp,465,submission,imap3,imaps,pop3,pop3s -j f2b-postfix-sasl
iptables -w -F f2b-postfix-sasl
iptables -w -X f2b-postfix-sasl -- returned 1
2016-12-20 04:51:04,025 fail2ban.actions [2126]: ERROR Failed to execute unban jail 'postfix-sasl' action 'iptables-multiport' info '{'matches': u'2016-12-19T04:50:53.412132 gateway.ganncom.com postfix/smtpd[20494]: warning: static-108-35-48-154.nwrknj.fios.verizon.net[108.35.48.154]: SASL LOGIN authentication failed: authentication failure2016-12-19T04:50:55.986579 gateway.ganncom.com postfix/smtpd[20495]: warning: static-108-35-48-154.nwrknj.fios.verizon.net[108.35.48.154]: SASL LOGIN authentication failed: authentication failure2016-12-19T04:50:58.081102 gateway.ganncom.com postfix/smtpd[20455]: warning: static-108-35-48-154.nwrknj.fios.verizon.net[108.35.48.154]: SASL LOGIN authentication failed: authentication failure2016-12-19T04:51:00.752822 gateway.ganncom.com postfix/smtpd[20497]: warning: static-108-35-48-154.nwrknj.fios.verizon.net[108.35.48.154]: SASL LOGIN authentication failed: authentication failure2016-12-19T04:51:02.755586 gateway.ganncom.com postfix/smtpd[20495]: warning: static-108-35-48-154.nwrknj.fios.verizon.net[108.35.48.154]: SASL LOGIN authentication failed: authentication failure', 'ip': '108.35.48.154', 'time': 1482144662.919717, 'failures': 5}': Error stopping action
2016-12-20 04:54:34,937 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:04:00,241 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:13:32,935 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:22:58,196 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:32:31,216 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:41:58,733 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 05:51:32,822 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:01:03,908 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:10:42,010 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:20:12,182 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:29:50,196 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:39:22,071 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:49:00,114 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 06:58:33,745 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 07:08:14,682 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 07:17:46,535 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 07:27:23,117 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 07:36:57,382 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125
2016-12-20 07:46:34,066 fail2ban.filter [2126]: INFO [postfix-sasl] Found 91.200.12.125


Here's what the Attack Detector webpage inside clearos portal has blocked.

Log

IP Address Rule Date/Time
108.35.48.154 postfix-sasl 2016-12-19 - 04:51:02

From what im seeing the 91.200 ips should of been banned but there not.
Anyone else having same problem? or how to fix this?
Thanks
Merry Christmas.

Since update to 7.1 release i can no longer access server from out of town. I've tried pinging and logging into web access without success.
I've had the server restarted and that didnt help. I've logged into the portal and can see that the external ip is right.
I cannot access anything on the server. I think there is something wrong with the firewall.
Anyone have an idea i can try to fix this?

Thanks
Sam

Peter Baldwin wrote:

Sam Gann wrote:

... snip ...

Again when I port forward to the exchange server port 25 email works. just when using the smtp on clearos 7.1 RC for spam filter
I get the logs above.

here are some more logs from system:
Sep 27 03:48:24 gateway mailfilter: starting up (sender=mailer-daemon, recipients=root@somewhere.lcl, client_address=)
Sep 27 03:48:24 gateway mailfilter: PHP Error: fsockopen(): unable to connect to localhost:2003 (Connection refused) <ID ...

The mail server is attempting to deliver a message to the local IMAP server (via LMTP / port 2003). I assume there's no IMAP server installed and that would definitely lead to the "connection refused" error. Take a look at the SMTP Server app settings and make sure Mail Domain and Mail Hostname are set to something other than any domain used in an e-mail address.

Ok mail Domain set to newdomain.com and Mail Host gateway.newdomain.com still same problem.

Logs:
Sep 29 19:22:13 gateway postfix/smtpd[9152]: connect from mail-yk0-f169.google.com[209.85.160.169]
Sep 29 19:22:14 gateway postfix/smtpd[9152]: Anonymous TLS connection established from mail-yk0-f169.google.com[209.85.1 ...
Sep 29 19:22:14 gateway postgrey[774]: action=pass, reason=client whitelist, client_name=mail-yk0-f169.google.com, clien ...
Sep 29 19:22:14 gateway postfix/smtpd[9152]: 33FCB10452068: client=mail-yk0-f169.google.com[209.85.160.169]
Sep 29 19:22:14 gateway postfix/cleanup[9156]: 33FCB10452068: message-id=<CAPw+UjTYRC=JGmqi6hw4sA_KUeJfkJVRwiE489TTXiLyj ...
Sep 29 19:22:14 gateway postfix/qmgr[8871]: 33FCB10452068: from=<someonecom@gmail.com>, size=1765, nrcpt=1 (queue active ...
Sep 29 19:22:14 gateway postfix/smtpd[9152]: disconnect from mail-yk0-f169.google.com[209.85.160.169]
Sep 29 19:22:14 gateway postfix/smtpd[9160]: connect from localhost[127.0.0.1]
Sep 29 19:22:14 gateway postfix/smtpd[9160]: 6509110452069: client=localhost[127.0.0.1]
Sep 29 19:22:14 gateway postfix/smtpd[9160]: lost connection after RCPT from localhost[127.0.0.1]
Sep 29 19:22:14 gateway postfix/smtpd[9160]: disconnect from localhost[127.0.0.1]
Sep 29 19:22:14 gateway postfix/pipe[9157]: 33FCB10452068: to=<someone@somewhere.com>, relay=mailprefilter, delay=0.24, de ...
Sep 29 19:22:14 gateway postfix/cleanup[9156]: 6D3EE10452069: message-id=<20150930002214.6D3EE10452069@gateway.doghelp.c ...
Sep 29 19:22:14 gateway postfix/bounce[9161]: 33FCB10452068: sender non-delivery notification: 6D3EE10452069
Sep 29 19:22:14 gateway postfix/qmgr[8871]: 6D3EE10452069: from=<>, size=3888, nrcpt=1 (queue active)
Sep 29 19:22:14 gateway postfix/qmgr[8871]: 33FCB10452068: removed
Sep 29 19:22:14 gateway postfix/smtp[9162]: connect to gmail-smtp-in.l.google.com[173.194.64.27]:25: No route to host
Sep 29 19:22:14 gateway postfix/smtp[9162]: connect to alt1.gmail-smtp-in.l.google.com[74.125.21.27]:25: No route to hos ...
Sep 29 19:22:14 gateway postfix/smtp[9162]: connect to alt2.gmail-smtp-in.l.google.com[173.194.208.27]:25: No route to h ...
Sep 29 19:22:14 gateway postfix/smtp[9162]: connect to alt3.gmail-smtp-in.l.google.com[74.125.141.26]:25: No route to ho ...
Sep 29 19:22:14 gateway postfix/smtp[9162]: connect to alt4.gmail-smtp-in.l.google.com[64.233.190.26]:25: No route to ho ...
Sep 29 19:22:14 gateway postfix/smtp[9162]: 6D3EE10452069: to=<someonecom@gmail.com>, relay=none, delay=0.16, delays=0.0 ...

not really understanding the no route to host from google. The email im using to send test email to me exchange server is gmail.
If I send email from gmail to the exchange using the port forward 25 to exchange it works. but will not work if I open port 25 incoming and close port forwarding 25 port.

Kinda lost I do know this was working on beta 7.3.

thanks
sam

After update to 7.3 beta mail filtering stopped working. I then went ahead and installed 7.1 RC and then configured for mail filtering again for my exchange server.

I know all i have to to do is install smtp from market and configure smtp with domain and then ip address also change the mail domain to use different domain than domain i am trying to filter. Then open port 25 threw firewall. I still have clearos 6 as a virtual machine and the filtering works.
yesterday my filtering was working so the updates install on the 26th are causing the problems.
If i port forward port 25 to my email server and close the 25 port on incomming than my email works fine.

Has anyone else had this problem?

Thanks Sam

I just figured it out. had to select new install on the registration.