I tried also to disable selinux, but that was also no the solution

"Permission denied" is what caught my eye. It seems that you'd get an "Invalid login or password" type error if that's the problem. It also seems that you'd get a connection failure if the port is incorrect. Is there a firewall that might be blocking outbound connections?Can you connect to this Gmail account using these same settings, but on a desktop mail client (Thunderbird, Outlook, etc.)?I hope someone else will weigh in on this, as I'm at work and things are getting busy.Jack

Permission denied.You appear to be using gmail, did you go into your gmail account and authorize POP?

Hi Jack,Yes i doublechecked it and i can login succesfully with my mail-client.The strange thing is i cant telnet to : pop.gmail.com 995                                                     imap.gmail.com 993I disabled selinux and i disabled my iptables, so i guess the firewall is not the issue here, the strange thing is i cant figure out what is causing this problem.

Hi Ntozier,Yes this is enabled i uploaded a screenshot 3 Is there any information that i can give you what might be helpfull ?

Your uploaded screen shot did not show POP enabled, or if it did it wasn't in english and didn't look like a radial was selected at all.What do you mean that you cannot telnet to pop.gmail.com 995 or imap.gmail.com 993.  What happens when you try?

POP is ingeschakeld means in English POP is enabled.Im getting a different error now : Can not authenticate to IMAP server: Please log in via your web browser: http://support.google.com/mail/accou

Im trying with imap know to see if there is a difference 

I tried with another domain Fetching Email via IMAP or POP   Connection failed to mail.mcxess.com,110: Connection timed outPOP 110SMTP 25

The strange thing is i cant telnet to : pop.gmail.com 995

                                                     imap.gmail.com 993

I disabled selinux and i disabled my iptables, so i guess the firewall is not the issue here, the strange thing is i cant figure out what is causing this problem.

I think this tells us the problem is not in osTicket.  You need to solve this before osTicket can fetch mail. Do you have tcpwrappers that might be blocking the connections?Jack

firstly check dns resolution, from the cli on the server with osticket installed:ping pop.gmail.com ping imap.comregardless of whether you get a reply or not, does it resolve an ip address? if not then it's dns. try ping 64.233.167.109 (pop)or ping 64.233.167.108 (imap) or ping 74.125.206.108 (another gmail imap address)if these work the problem is your dns.if these still fail, then there's something wrong with the routing somewhere.try traceroute pop.gmail.com (linux) or tracert pop.gmail.com (windows) and see where that gets to.the last ip you get to before you start receiving a string of asterisks is where the problem is. it's almost certainly going to be a firewall or router, with an outside chance of being a switch.

Hi Jack and nhybgtvfr,Here is an update is SMTP is working now, the only problem for now is pop and imap.i cant telnet to ports : 995,993 and 110.I even disabled iptables, firewall-tui.Does anyone have an idea ? 

as already said. check dns resolution first, forget whether or not there's a response, does a ping pop.gmail.com return a first line like:PING gmail-pop.l.google.com (173.194.78.109) 56(84) bytes of data.64 bytes from wg-in-f109.1e100.net (173.194.78.109): icmp_req=1 ttl=48 time=12.7 ms64 bytes from wg-in-f109.1e100.net (173.194.78.109): icmp_req=2 ttl=48 time=12.6 mssee the ip? if it's not returning an ip, then there's a dns problem somewhere.try pinging the ip rather than the name, if that works, then again, it's a dns issue, you can set your pop/imap server using the ip instead of the name, it'll get you up and running, but it's not the recommended way, and doesn't provide for server failure.if you can ping the ip, but can't telnet to the ports, then there's definitely a firewall/iptable rule somewhere blocking it.  if pinging the ip address fails, you'll need to run a traceroute to that ip, and see where it fails, and start troubleshooting from there. also, it may seem silly, but are you absolutely sure you can't connect?, when trying telnet, does it show a connecting to... message, followed by 'could not open a connection to the host', or do you just get a black window with a flashing white box in the top left corner?if it's the latter, it is connected.

Write a Reply...