inbound e-mail failure

[jceelen]

Hi All,

i'm very happy with using sugar but there are some things with e-mail that I cannot get to work.

1. Outbound e-mail works perfectly (with smtp.gmail.com on googleapps works like a charm)
2. Inbound e-mail give's me the biggest problems, imap will not connect through SSL or nonSSL providers (imap.gmail.com / imap.gmx.com) POP3 won't work either.
When I test or try to select de folders for trash or sent etc i will get the pop-up, it loads and then it's finished loading and gives me no error or result. Only:

Test Settings
One moment please...

Or with the SSL statement that it's possible that i have to wait a little longer.

After i try that my sugar installation is busy for several minutes, i cannot reach it while other sites on my server are working perfect.

I searched and read all threads about this topic but no-one seems to know what's going wrong

When i use the stack installer with my mail accounts everything goes well so it has to be something on the server.

I can't find any alerts in my logs at the moments i tried to test or use inbound e-mail. Can anybody help me with this problem? I already tried a lot with together with my web host based on the information provided on these forums but we cannot figure out what's

This is my server info:
» Operating system type and version Linux
» Sugar version and edition (i.e. 5.2.0b Community Edition)
» Webserver type and version Apache 2.0 Handler
» PHP version (i.e. 5.2.1.0)
» MySQL server version (Client API version 5.0.81)


This is my php info: http://www.dialectro.nl/info.php

if you need more info I will be happy to provide you with it!

[sugarchris]

Hi jceelan,

Although I haven't worked on the email code in 2+ years, what i do remember is that some hosts will configure their servers to disallow inbound traffic on common ports such as the ones used by Gmail/IMAP. The fact that the stack installer works on your dev machine, but the hosted version doesn't suggests just this.

I would open a trouble ticket with whoever your host company is and see if they can make exceptions for well known MX addresses (such as those used by Gmail).

Other than this, switching hosts is the only other alternative since Sugar can't control anthing beyond the web server layer.

Sorry there isn't a better fix to try out.

[jceelen]

UPDATE:
my apache error log shows these failures after testing:

[Sat Aug 29 22:11:26 2009] [error] [client 82.169.145.174] File does not exist: /home/dialectron/domains/dialectro.nl/public_html/sugar/Array, referer: http://www.dialectro.nl/sugar/index....s&action=index
[Sat Aug 29 22:11:26 2009] [error] [client 82.169.145.174] File does not exist: /home/dialectron/domains/dialectro.nl/public_html/404.shtml, referer: http://www.dialectro.nl/sugar/index....s&action=index
[Sat Aug 29 22:11:27 2009] [error] [client 82.169.145.174] File does not exist: /home/dialectron/domains/dialectro.nl/public_html/sugar/Array, referer: http://www.dialectro.nl/sugar/index....s&action=index
[Sat Aug 29 22:11:27 2009] [error] [client 82.169.145.174] File does not exist: /home/dialectron/domains/dialectro.nl/public_html/404.shtml, referer: http://www.dialectro.nl/sugar/index....s&action=index

@Sugarchris: thnx for your time and tips!