Errors sent to server

[yorkiedale]

I'm building a CBox site

Just after enabling this plugin, using gmail, and setting pingdom to check the site at 1minute intervals, lots of errors were reported to my server, and the host contacted me ...

copy of their message and logs as below:
hi
you are getting loads of errors on this account
the sites main error log
[24-Dec-2012 02:02:16] PHP Warning: include_once(wp-load.php) [function.include-once]: failed to open stream: No such file or directory in /home/natural/public_html/wp-content/plugins/bebop/secondary_import.php on line 15
[24-Dec-2012 02:02:16] PHP Warning: include_once() [function.include]: Failed opening 'wp-load.php' for inclusion (include_path='/home/natural') in /home/natural/public_html/wp-content/plugins/bebop/secondary_import.php on line 15

also bp-rbe-debug.log in wp-content folder
[24-Dec-2012 00:49:20] --- Attempting to start new connection... ---
[24-Dec-2012 00:49:21] --- Connection successful! ---
[24-Dec-2012 00:49:21] --- Keep alive for 15 minutes ---
[24-Dec-2012 00:49:21] - Checking inbox -
[24-Dec-2012 00:49:21] Message #1: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:22] Message #2 of 55: email headers successfully parsed
[24-Dec-2012 00:49:22] Message #2: error - no address tag could be found
[24-Dec-2012 00:49:22] Message #3 of 55: email headers successfully parsed
[24-Dec-2012 00:49:22] Message #3: error - no address tag could be found
[24-Dec-2012 00:49:22] Message #4 of 55: email headers successfully parsed
[24-Dec-2012 00:49:22] Message #4: error - no address tag could be found
[24-Dec-2012 00:49:23] Message #5 of 55: email headers successfully parsed
[24-Dec-2012 00:49:23] Message #5: error - no address tag could be found
[24-Dec-2012 00:49:23] Message #6 of 55: email headers successfully parsed
[24-Dec-2012 00:49:23] Message #6: error - no address tag could be found
[24-Dec-2012 00:49:23] Message #7 of 55: email headers successfully parsed
[24-Dec-2012 00:49:23] Message #7: error - no address tag could be found
[24-Dec-2012 00:49:23] Message #8: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:24] Message #9: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:24] Message #10: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:24] Message #11 of 55: email headers successfully parsed
[24-Dec-2012 00:49:24] Message #11: error - no address tag could be found
[24-Dec-2012 00:49:25] Message #12 of 55: email headers successfully parsed
[24-Dec-2012 00:49:25] Message #12: error - no address tag could be found
[24-Dec-2012 00:49:25] Message #13: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:25] Message #14: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:26] Message #15: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:26] Message #16 of 55: email headers successfully parsed
[24-Dec-2012 00:49:26] Message #16: error - no address tag could be found
[24-Dec-2012 00:49:26] Message #17: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:26] Message #18: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:27] Message #19 of 55: email headers successfully parsed
[24-Dec-2012 00:49:27] Message #19: error - no address tag could be found
[24-Dec-2012 00:49:27] Message #20: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:27] Message #21: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:28] Message #22: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:28] Message #23 of 55: email headers successfully parsed
[24-Dec-2012 00:49:28] Message #23: error - no address tag could be found
[24-Dec-2012 00:49:29] Message #24 of 55: email headers successfully parsed
[24-Dec-2012 00:49:29] Message #24: error - no address tag could be found
[24-Dec-2012 00:49:29] Message #25 of 55: email headers successfully parsed
[24-Dec-2012 00:49:29] Message #25: error - no address tag could be found
[24-Dec-2012 00:49:29] Message #26: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:29] Message #27: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:30] Message #28 of 55: email headers successfully parsed
[24-Dec-2012 00:49:30] Message #28: error - no address tag could be found
[24-Dec-2012 00:49:30] Message #29 of 55: email headers successfully parsed
[24-Dec-2012 00:49:30] Message #29: error - no address tag could be found
[24-Dec-2012 00:49:30] Message #30: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:30] Message #31: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:31] Message #32: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:31] Message #33: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:31] Message #34 of 55: email headers successfully parsed
[24-Dec-2012 00:49:31] Message #34: error - no address tag could be found
[24-Dec-2012 00:49:32] Message #35: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:32] Message #36: error - this is some type of bulk / junk / mailing list email, so stop now!
[24-Dec-2012 00:49:32] Message #37: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:33] Message #38: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:33] Message #39: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:33] Message #40: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:33] Message #41 of 55: email headers successfully parsed
[24-Dec-2012 00:49:33] Message #41: error - no address tag could be found
[24-Dec-2012 00:49:34] Message #42: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:34] Message #43 of 55: email headers successfully parsed
[24-Dec-2012 00:49:34] Message #43: error - no address tag could be found
[24-Dec-2012 00:49:34] Message #44: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:35] Message #45: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:35] Message #46: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:35] Message #47 of 55: email headers successfully parsed
[24-Dec-2012 00:49:35] Message #47: error - no address tag could be found
[24-Dec-2012 00:49:36] Message #48 of 55: email headers successfully parsed
[24-Dec-2012 00:49:36] Message #48: error - no address tag could be found
[24-Dec-2012 00:49:36] Message #49 of 55: email headers successfully parsed
[24-Dec-2012 00:49:36] Message #49: error - no address tag could be found
[24-Dec-2012 00:49:36] Message #50 of 55: email headers successfully parsed
[24-Dec-2012 00:49:36] Message #50: error - no address tag could be found
[24-Dec-2012 00:49:36] Message #51 of 55: email headers successfully parsed
[24-Dec-2012 00:49:36] Message #51: error - no address tag could be found
[24-Dec-2012 00:49:37] Message #52 of 55: email headers successfully parsed
[24-Dec-2012 00:49:37] Message #52: error - no address tag could be found
[24-Dec-2012 00:49:37] Message #53: error - this is auto-reply from MS Exchange, so stop now!
[24-Dec-2012 00:49:37] Message #54 of 55: email headers successfully parsed
[24-Dec-2012 00:49:37] Message #54: error - no address tag could be found
[24-Dec-2012 00:49:37] Message #55 of 55: email headers successfully parsed
[24-Dec-2012 00:49:37] Message #55: error - no address tag could be found
[24-Dec-2012 00:49:49] - Checking inbox -
[24-Dec-2012 00:49:49] Message #1 of 1: email headers successfully parsed
[24-Dec-2012 00:49:49] Message #1: error - no address tag could be found
[24-Dec-2012 00:55:16] - Checking inbox -
[24-Dec-2012 00:55:16] Message #1 of 1: email headers successfully parsed
[24-Dec-2012 00:55:16] Message #1: error - no address tag could be found
[24-Dec-2012 00:59:16] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 01:04:21] --- Closing current connection automatically ---
[24-Dec-2012 01:05:12] --- Attempting to start new connection... ---
[24-Dec-2012 01:05:12] --- Connection successful! ---
[24-Dec-2012 01:05:12] --- Keep alive for 15 minutes ---
[24-Dec-2012 01:05:43] - Checking inbox -
[24-Dec-2012 01:05:43] Message #1 of 1: email headers successfully parsed
[24-Dec-2012 01:05:43] Message #1: error - no address tag could be found
[24-Dec-2012 01:06:16] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 01:20:15] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 01:20:17] --- Closing current connection automatically ---
[24-Dec-2012 01:21:16] --- Attempting to start new connection... ---
[24-Dec-2012 01:21:16] --- Connection successful! ---
[24-Dec-2012 01:21:16] --- Keep alive for 15 minutes ---
[24-Dec-2012 01:23:16] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 01:36:24] --- Closing current connection automatically ---
[24-Dec-2012 01:36:50] --- Attempting to start new connection... ---
[24-Dec-2012 01:36:51] --- Connection successful! ---
[24-Dec-2012 01:36:51] --- Keep alive for 15 minutes ---
[24-Dec-2012 01:38:16] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 01:51:37] - Checking inbox -
[24-Dec-2012 01:51:37] Message #1 of 1: email headers successfully parsed
[24-Dec-2012 01:51:37] Message #1: error - no address tag could be found
[24-Dec-2012 01:51:57] --- Closing current connection automatically ---
[24-Dec-2012 01:52:16] --- Attempting to start new connection... ---
[24-Dec-2012 01:52:16] --- Connection successful! ---
[24-Dec-2012 01:52:16] --- Keep alive for 15 minutes ---
[24-Dec-2012 01:53:16] --- Cronjob wants to connect - however according to our DB indicator, we already have an active IMAP connection! ---
[24-Dec-2012 02:01:39] - Checking inbox -
[24-Dec-2012 02:01:39] Message #1 of 2: email headers successfully parsed
[24-Dec-2012 02:01:39] Message #1: error - no address tag could be found
[24-Dec-2012 02:01:39] Message #2 of 2: email headers successfully parsed
[24-Dec-2012 02:01:39] Message #2: error - no address tag could be found

the wp cron is also taking a very long time to run
Time: Mon Dec 24 01:23:13 2012 +0000
PID: 4557
Account: natural
Uptime: 118 seconds

Executable:

/usr/bin/php

Command Line (often faked in exploits):

/usr/bin/php /home/natural/public_html/wp-cron.php

Network connections by the process (if any):

tcp: 83.170.114.14:55452 -> 173.194.67.109:993

Files open by the process (if any):

/tmp/session_mm_cgi-fcgi1620.sem (deleted)
/tmp/sess_45a1992e85a7fe92a8a5d9040ab0ad30
/home/natural/public_html/wp-content/plugins/bebop/extensions

i have had to rename bebop to bebop –problem in plugins so the error log does not fill up the server to you can sort this out
please turn off if you are unable to fix

[r-a-y]

Sounds like the Bebop plugin is causing some problems that are not related to this plugin. If you are not using Bebop, disable the plugin from the CBOX plugins admin page.

As for your Reply By Email log, judging by the number of errors in your log, it appears that you were using an existing email address. The documentation in the quick setup guide states that you should not use an already, active GMail address.

[yorkiedale]

Ah yes, I was using an existing gmail account - oops
The host only contacted me after I enabled the Reply By Email plugin, so I assumed somehow all the errors were down to this, and not bebop, which has been enabled for a few days
cheers for the help

[r-a-y]

Are you on a shared host? If so, then I can understand that they would contact you as the plugin is quite intensive:
https://github.com/r-a-y/bp-reply-by-email/wiki/Quick-Setup-with-GMail#wiki-server

Because the original intension of the plugin was to have a persistent connection to the inbox, the plugin needs to run almost all the time.

It might be possible to use a real cron job instead of using WordPress' built-in version of cron to solve your wp-cron.php issues, but I'm not 100% sure as I have never tested this.

If you are interested in this method and your host allows you to set cron jobs, let me know and I'll try and steer you in the right direction. If this works, then I can add this information into the wiki!

[yorkiedale]

Yes, I'm on a shared host, but it is my own reseller account. I can set crons etc, not done this before, but I know there is the option in cpanel - so, any help and advice is needed/welcome

[r-a-y]

Hi, sorry for the late response!

Try disabling WP cron and setting it up as a real cron job:
http://www.inmotionhosting.com/support/website/wordpress/disabling-the-wp-cronphp-in-wordpress

For step 5, you'll need to replace that with your relative path to wp-cron.php.
Also, set the time limit to whatever your "Keep Alive" connection limit is in RBE. Perhaps add a minute to that.

Note: I have no idea if this will work so keep me posted.

[r-a-y]

I'm closing this because it's a shared host problem, but feel free to reply if you are still encountering issues, YorkieDale.

[vinhtq]

I have exactly the same problem, seem like all the plugins try to reply via email have this issue.
We should try to send mail asynchronously or use cron job.

[r-a-y]

@vinhtq - If you're on a shared host, use Inbound Mode instead of IMAP:
https://github.com/r-a-y/bp-reply-by-email/wiki/Starter-Guide#1-inbound-email-mode

[vinhtq]

@r-a-y Thank you!