Hello Gary,

Actually the test connection is not for the cronjob. However, I've checked the cron command and it seems fine to me. The Test connection is to test the connection with the server. You might want to check with your webhosting about the mail server address and port. Because, there is one user has mentioned that his webhosting using different server address and port to make it works. Hope this helps narrowing down the problem.

So I read every post on here I could find on this problem. I seem to get the same error as this fellow Title. I originally had this set up via Gmail too so decided to try a different known working email.

I tried setting up an e-mail account via my web host and get the same results. I know the account works as I set up a new account for my Outlook and it can access the account and server using the settings I have set up in the easyblog. My revised setup screen is below.

I am also wondering if it is possible to undo the "select a user" setting on the other column on settings? I can change it, but I cannot find a way to not select anyone not that I have selected someone. Based on my reading of the other posts on that selection, it would appear leaving it blank would work better since I will have 3-5 offsite bloggers and have set it to auto identify them based on their e-mail. Is that correct?

Anyway, until I can get the software to connect to my mail server I cannot move ahead with this anyway.

Thank you.

Hello Gary,

The user cannot be empty because there will be no author for the blog post. The map user will check if the email of the sender matched to any email of the user in database. If matched, the user will be the author.

Thanks Nick. That explains that well.

My problem is I cannot get the extension to connect to any of several known e-mail addresses. It simply times out. I know it is trying to connect, and I have the settings the same as I tested using Outlook to successfully connect and test the port settings. I tried Gmail (2 different accounts) as well as an account at 1and1, my web host. I get the same exact result each place.

Is there a place to set the timeout setting? or is there something else I should be looking at?

Thank you.

Gary

This is the setup information that Google gives for folks to use imap - I have tried this to the letter and reconfirmed everything.

Many clients will automatically configure the appropriate IMAP connection settings for your account, but confirm that the connection settings your client configures are the same as what's listed below.

If you're using a client that's not listed above, you can also use the following information to configure your IMAP. If you have problems, contact your mail client's customer support department for further instructions.

Incoming Mail (IMAP) Server - Requires SSL
imap.gmail.com
Port: 993
Requires SSL:Yes
Outgoing Mail (SMTP) Server - Requires TLS
smtp.gmail.com
Port: 465 or 587
Requires SSL: Yes
Requires authentication: Yes
Use same settings as incoming mail server
Full Name or Display Name: [your name]
Account Name or User Name: your full Gmail address (username@gmail.com). Google Apps users, please enter username@your_domain.com
Email address: your full Gmail address (username@gmail.com) Google Apps users, please enter username@your_domain.com
Password: your Gmail password
If your client does not support SMTP authentication, you won't be able to send mail through your client using your Gmail address.

Also, if you're having trouble sending mail but you've confirmed that encryption is active for SMTP in your mail client, try to configure your SMTP server on a different port: 465 or 587.

Hello Gary,

So sorry for the late reply. After debugging your site, it seems like the issue is only happen when you using the Test Connection. Can you provide us the gmail account used to receive email so that we can run a test to see if it is connected or not? Please advise.

Hi Nick:

The gmail account set up for this login is attached. thank you for helping with this.

I recently migrated my remote publishing account to Gmail as well, and changing the Remote Publishing settings to follow the Gmail recommended IMAP settings are not working. I don't see a final resolution to this ticket. What is the correct settings to implement to get Gmail working with Remote Publishing? Thanks!

Hello Brad,

I've tried to access your backend and I got this: http://screencast.com/t/mLc18whZ1T . Please advise.

Sorry, we had locked down our site to prevent Brute Force attacks. Try it again.

Hi Brad Wendel,

Sorry for late reply to this,

I have checked in your site, I hitting this following error :

<b>Warning</b>:  imap_open() [<a href='function.imap-open'>function.imap-open</a>]: Couldn't open stream {imap.gmail.com:993/imap/novalidate-cert} in <b>/home/pcmomaha/public_html/components/com_easyblog/classes/mailbox.php</b> on line <b>127</b><br />

[["script","$('#remote_test_result').html('Connection failed to gmail-imap.l.google.com,993: Connection timed out');"]]

based on this error message, it seems like connection get failed.
Can you check with your following detail and see how it goes?
#1. is it set correctly for you Username & password from the remote publishing configuration setting
#2. Is it imap.gmail.com using this PORT number 995

Keep us updated then. If still can't, can you provide us some info regarding with your mail server detail?

Hey Arlex ... thanks for the info. Confirmed what I was seeing too. I double-checked and confirmed the username and password are correct. Below are the exact instructions that Gmail provided for remote access. The Mailbox name may be the problem. I've tried Inbox, INBOX, Mail and the e-mail address and none of them have worked (connection still times out). If I leave the Mailbox name field blank, the connection fails immediately. I know with my old IMAP provider I had to enter a specific mailbox name for it to work properly. What is the Mailbox name for a Gmail account?

Thanks!
Brad

Incoming Mail (IMAP) Server - Requires SSL
imap.gmail.com
Port: 993
Requires SSL:Yes
Outgoing Mail (SMTP) Server - Requires TLS
smtp.gmail.com
Port: 465 or 587
Requires SSL: Yes
Requires authentication: Yes
Use same settings as incoming mail server
Full Name or Display Name: [your name]
Account Name or User Name: your full Gmail address (username@gmail.com). Google Apps users, please enter username@your_domain.com
Email address: your full Gmail address (username@gmail.com) Google Apps users, please enter username@your_domain.com
Password: your Gmail password

Hi Brad Wendel ,

Sorry for late reply to this,

Okay, ignore the test connection error. Because I tested using my email address send to your email, then manually run the cronjob, then it process correctly. (You can check my following attachment screenshot, this is what i setup the current configuration setting)

By the way, may i know did you have configure the cronjob in your site yet? If no, can you provide us with your Cpanel access so we can help you configure with this? So it will every time automatically help you process cronjob.

Confirmed manual cronjob resulted in successful remote publishing. Guess the Test Connection feature inside Easy Blog needs fix. Here is our current cronjob config. Please advise of change needed:

/usr/bin/wget -O /dev/null "http://pcmwindow.org/index.php?option=com_easyblog&task=cron";

Thanks!

Hi Brad,

Sorry for late reply to this,

Try this without ';' and set your email address in your cron email, so we can see what is your server response if run this following command.

/usr/bin/wget -O /dev/null "http://pcmwindow.org/index.php?option=com_easyblog&task=cron"

Looks like we're good now. Did you make any changes?

--2015-07-02 14:40:02-- http://pcmwindow.org/index.php?option=com_easyblog&task=cron
Resolving pcmwindow.org... 173.236.53.234
Connecting to pcmwindow.org|173.236.53.234|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 98 [text/html]
Saving to: “/dev/null”

0K 100% 19.0M=0s

2015-07-02 14:40:12 (19.0 MB/s) - “/dev/null” saved [98/98]

Hi Brad Wendel,

Yes, look like your server response to this cron command is look fine now.

If I'm not wrong, what I did is just remove this -> ; from your cron command.

Hope this help.