Whats going on with Group Email Incoming??

My number one favourite feature with SuiteCRM is its Helpdesk ability. To be able to convert a clients email into a Case. But for some reason its stopped working. I found the bugtracker for this and apparently its known, but the bug has been closed. It was found in 7.11.1 I believe.

I upgraded to 7.11.3 but it doesnt appear to be resolved. I did a clean install of 7.11.3, same issue. I then did a clean issue of 7.10.15. Still not working.

Running on Ubuntu 18.04 LTS with all default versions (Apache, PHP, MariaDB).

I found a few things in the SuiteCRM log that look suss. This text only displays when I set the log to ‘Info’.

Wed Apr 10 09:59:05 2019 [2471][1][INFO] Query:UPDATE job_queue 					SET `assigned_user_id`='1',`name`='Check Inbound Mailboxes',`date_modified`='2019-04-09 23:59:02',`scheduler_id`='4afc8809-dfd6-59bb-94ed-5cac9c655c08',`execute_time`='2019-04-09 23:59:00',`status`='done',`resolution`='success',`message`='Warning [2]: Declaration of AOPInboundEmail::handleCreateCase(Email $email, $userId) should be compatible with InboundEmail::handleCreateCase($email, $userId) in /var/www/html/suitecrm/modules/InboundEmail/AOPInboundEmail.php on line 27\nWarning [2]: count(): Parameter must be an array or an object that implements Countable in /var/www/html/suitecrm/modules/InboundEmail/InboundEmail.php on line 6126\nWarning [2]: imap_append() expects at least 3 parameters, 1 given in /var/www/html/suitecrm/include/Imap/ImapHandler.php on line 456\n',`target`='function::pollMonitoredInboxesAOP',`data`=NULL,`requeue`=0,`retry_count`=NULL,`failure_count`=NULL,`job_delay`=0,`client`='CRONe0f3855106ec70d44f4ededfc583bcc8:2471',`percent_complete`=NULL 

The comes up when Log set to ‘Error’. Keeps coming up.

Wed Apr 10 10:14:01 2019 [2759][1][ERROR] ImapHandler trying to use a non valid resource stream.

If I am missing something, great. But I have been trying to find a reason for days. Outbound emails work fine. I can connect to my external IMAP server and send emails from the servers Terminal. Definitely no connection issues. Cron is working fine as I can see other scheduled tasks going ahead.

The external server isOffice365 which has been setup to pass traffic, and as mentioned, I can connect via command line.

Any assistance would be greatly appreciated. I would prefer not to have to roll back to resolve this.

Regards,
Mike.

Just set the logs to ‘Warn’ and notice this.

Wed Apr 10 10:23:06 2019 [2896][1][WARN] An Imap error detected: "IMAP search error"
Wed Apr 10 10:23:06 2019 [2896][1][WARN] An Imap error detected: "IMAP expunge error"

Am I the only one having this issue guys? Or is there a fix on the way?

No response?

I found bug #6876 in Github that appears to be the same issue. But this bug was logged back in Feb and has been closed. I would assume it was fixed, but apparently not. I’m new to Github so not sure how to check.

OK, this seems to be an issue with Exchange Online. I created a subdomain email account through my hosting provider and the emails come through???

Still trying to figure out why.

Mallen1278,
I’m having the same issue. I’m upgrading from 7.8.2 to latest version, but both 7.11.3 and 7.10.15 can’t create cases reading an Exchange Online mailbox (7.8.2 does it). Same error as yours.

I’m trying to work it out (there’s also GitHub issue #6866).

Any luck figuring it out? Fresh install of 7.11.4 and still not sending emails. Extremely frustrating. I’m not using most of the CRM features. Mainly Case Creation. Prefer not to have to downgrade. But this issue has been around for months. Bug is still open with no responses. And no Dev responses to this post.

I know Linux is connecting as I could connect to Exchange Online via CLI and send emails. I can send fine in SCRM. Just cannot receive.

Bug #7186 is around a month old and is exactly the same issue.

Bit concerning that a bug like this goes without acknowledgement. 7186 is with Gmail so we know this is a problem on two of the largest email systems out there. Wondering if they are planning on removing Automatic Case creation completely and this is just a Scream test.

Also, the Zuver account I tried with does receive emails and create cases, but the Case Creation email template doesnt work. It sends but its ignoring the From Email in the Group email and AOP. Its sending from the system email and its missing details such as Case number.

Email shows this:

Hi $contact_first_name $contact_last_name,

We’ve received your case $acase_name (# $acase_case_number) on $acase_date_entered

Status $acase_status
Reference $acase_case_number
Description $acase_description

FYI 7.10.11 works with Exchange. But its not perfect. Nothing to do with Exchange. AOP is broken. If you enter in the Support Email address in AOP you get duplicate emails. And the response is still coming from the system email. Trying to figure out if this is a Settings issue. Pretty sure it was working before. Just cannot remember which version was working.

Guys, which version of PHP are you running?

Are they within this spec? https://docs.suitecrm.com/admin/compatibility-matrix/

If they are, I want to focus on this error here:

Wed Apr 10 09:59:05 2019 [2471][1][INFO] Query:UPDATE job_queue 					SET `assigned_user_id`='1',`name`='Check Inbound Mailboxes',`date_modified`='2019-04-09 23:59:02',`scheduler_id`='4afc8809-dfd6-59bb-94ed-5cac9c655c08',`execute_time`='2019-04-09 23:59:00',`status`='done',`resolution`='success',`message`='Warning [2]: Declaration of AOPInboundEmail::handleCreateCase(Email $email, $userId) should be compatible with InboundEmail::handleCreateCase($email, $userId) in /var/www/html/suitecrm/modules/InboundEmail/AOPInboundEmail.php on line 27\nWarning [2]: count(): Parameter must be an array or an object that implements Countable in /var/www/html/suitecrm/modules/InboundEmail/InboundEmail.php on line 6126\nWarning [2]: imap_append() expects at least 3 parameters, 1 given in /var/www/html/suitecrm/include/Imap/ImapHandler.php on line 456\n',`target`='function::pollMonitoredInboxesAOP',`data`=NULL,`requeue`=0,`retry_count`=NULL,`failure_count`=NULL,`job_delay`=0,`client`='CRONe0f3855106ec70d44f4ededfc583bcc8:2471',`percent_complete`=NULL

@mallen1278, do you still get this error?

@incofast do you have it too?

Running Ubuntu 18.04 LTS with all default packages. So PHP 7.2.

Are you saying that others are not having this issue? Can you confirm the latest release works on your end. Because I seem to be having issues with all versions. Version 7.10.11 (The oldest I tested) seems to have the least issues. I have 7.10.11, 7.10.16, and 7.11.4 running side by side, but all on the same server. If a different Distro would be better, fine, I’ll give it a go.

I can’t run any email tests right now, sorry

If you can let me know about the PHP errors, I think I can do something about those even with the limited time I have.

Well I downloaded a fresh copy of CentOS 7.6 for testing, running PHP 7.1. Same issue. Actually worse. I can see the Cron is running. But for some reason the emails are coming in as emails, and no Case is being created. Was trying to run 7.10.16 on the new Hyper-V instance thinking that would be the least problematic.

I’m going to try 7.8 and see if it works.

This is on 7.10.16. I’m trying to use AOP if at all possible. So I have created the incoming group email with auto case creation. I have added in the group email address here. For the method of response, I have setup AOP Default AND entered the Case Creation template (Not sure why I would need to do this here when AOP is setup). I then also entered the service email into the AOP section.

I should add, I am using another SMTP server for Incoming email as Exchange is a whole different issue. I at least get emails with a basic IMAP/SMTP server.

So now, I get a response to my email that the case has been created which is perfect. But my customer (test email) does not get the notification.

Suite log:

Mon May 6 08:26:01 2019 [2978][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:26:01 2019 [2978][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:27:01 2019 [3167][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:27:01 2019 [3167][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:28:01 2019 [3187][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:28:01 2019 [3187][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:29:01 2019 [3203][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:29:01 2019 [3203][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:30:01 2019 [3220][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:30:01 2019 [3220][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:31:01 2019 [3238][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:31:01 2019 [3238][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:31:02 2019 [3238][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From-name is not set.
From address and name pair does not match to from name.
From address and name pair is invalid.
codes:1, 7, 22, 15
Mon May 6 08:31:02 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:02 2019 [3238][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 08:31:02 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:09 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:15 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:15 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:15 2019 [3238][1][ERROR] send: PHPMailer Exception: { SMTP Error: data not accepted.

}
Mon May 6 08:31:15 2019 [3238][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From-name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 7, 16, 15
Mon May 6 08:31:15 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:15 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:15 2019 [3238][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:31:22 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:22 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:22 2019 [3238][1][ERROR] send: PHPMailer Exception: { SMTP Error: data not accepted.

}
Mon May 6 08:31:22 2019 [3238][1][ERROR] Invalid email address given: [Client Name] Called at /var/www/html/suitecrm_7_10/modules/InboundEmail/AOPInboundEmail.php:201 from function handleReplyType.
Mon May 6 08:31:22 2019 [3238][1][ERROR] Invalid email address given: [Client Name ] Called at /var/www/html/suitecrm_7_10/modules/InboundEmail/AOPInboundEmail.php:202 from function displayComposeEmail.
Mon May 6 08:31:22 2019 [3238][1][FATAL] Attachements not found
Mon May 6 08:31:22 2019 [3238][1][ERROR] Invalid email from address or name detected before sending. Details:
From field is not set.
From-name is not set.
From address and name pair is not set.
codes:1, 7, 13

Mon May 6 08:31:28 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:28 2019 [3238][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 08:31:28 2019 [3238][1][ERROR] send: PHPMailer Exception: { SMTP Error: data not accepted.

}
Mon May 6 08:32:01 2019 [3255][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:32:01 2019 [3255][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 08:32:02 2019 [3255][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 08:32:02 2019 [3255][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:32:02 2019 [3255][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:32:02 2019 [3255][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 08:32:02 2019 [3255][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 08:32:02 2019 [3255][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a

So, take the email details out of the AOP page and when this happens, I get 2 emails now. One for the case Creation as expected, and another for a case update, which should not happen as the case was not updated as yet. This email is coming from the Admin email entered during installation which is expected.

The client is now getting an email, but its also coming from the admin login even though I input the support email in the Group mail address. And if the client replies, it replies to the admin login… so no case update.

Now all I need is for the system to send the email to the client via the support email and we are good to go. Then next stage, get back to using Office 365 Exchange or Gmail.

Log:

Mon May 6 09:01:01 2019 [4403][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:01:01 2019 [4403][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:01:02 2019 [4403][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:01:02 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:02 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:02 2019 [4403][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:01:02 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:02 2019 [4403][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a
Mon May 6 09:01:02 2019 [4403][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From-name is not set.
From address and name pair does not match to from name.
From address and name pair is invalid.
codes:1, 7, 22, 15
Mon May 6 09:01:02 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:02 2019 [4403][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:01:02 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:08 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From-name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 7, 16, 15
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:15 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:22 2019 [4403][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:01:22 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:22 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:22 2019 [4403][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:01:22 2019 [4403][1][ERROR] Invalid email address given: [Michael Allen ] Called at /var/www/html/suitecrm_7_10/modules/InboundEmail/AOPInboundEmail.php:201 from function handleReplyType.
Mon May 6 09:01:22 2019 [4403][1][ERROR] Invalid email address given: [Michael Allen ] Called at /var/www/html/suitecrm_7_10/modules/InboundEmail/AOPInboundEmail.php:202 from function displayComposeEmail.
Mon May 6 09:01:22 2019 [4403][1][FATAL] Attachements not found
Mon May 6 09:01:22 2019 [4403][1][ERROR] Invalid email from address or name detected before sending. Details:
From field is not set.
From-name is not set.
From address and name pair is not set.
codes:1, 7, 13

Mon May 6 09:01:28 2019 [4403][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 09:01:28 2019 [4403][1][FATAL] SugarPHPMailer encountered an error: SMTP Error: data not accepted.
Mon May 6 09:01:28 2019 [4403][1][ERROR] send: PHPMailer Exception: { SMTP Error: data not accepted.

}
Mon May 6 09:02:01 2019 [4420][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:02:01 2019 [4420][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:02:02 2019 [4420][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:02:02 2019 [4420][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:02:02 2019 [4420][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:02:02 2019 [4420][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:02:02 2019 [4420][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:02:02 2019 [4420][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a
Mon May 6 09:02:02 2019 [4420][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:02:02 2019 [4420][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:02:02 2019 [4420][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:02:02 2019 [4420][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:02:02 2019 [4420][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a
Mon May 6 09:03:01 2019 [4437][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:03:01 2019 [4437][1][ERROR] ImapHandler trying to use a non valid resource stream.
Mon May 6 09:03:02 2019 [4437][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:03:02 2019 [4437][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:03:02 2019 [4437][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:03:02 2019 [4437][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:03:02 2019 [4437][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:03:02 2019 [4437][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a
Mon May 6 09:03:02 2019 [4437][1][FATAL] *** FOLDERS: addBean() is trying to save to a non-saved or non-existent folder
Mon May 6 09:03:02 2019 [4437][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:03:02 2019 [4437][1][ERROR] Saving Email with invalid From name and/or Address. Details:
From field is not set.
From address is not set.
From-name is not set.
From name is not set.
From address and name pair format is incorrect, use "from@emailaddress.org " format.
From address and name pair is invalid.
codes:1, 4, 7, 10, 16, 15
Mon May 6 09:03:02 2019 [4437][1][ERROR] Unable to find relationship emails_email_templates
Mon May 6 09:03:02 2019 [4437][1][ERROR] Contact address is incorrect to Email: b233ab88-b44f-555f-550f-5ccf646baa3a

One more thing. I am currently running latest 7.8 and 7.10 side by side and they are both doing the same thing. Like I said before, I was sure I tested this to work some time ago with success. So not sure whats changed.

Apologies for the bombardment of emails. I really need to get to the bottom of this ASAP as I’m about to launch a small business on the side. Being its a second job to my full time job, and I already get maybe a hundred emails a day, I just need a way to manage incoming information. And SuiteCRM is perfect.

Just wondering how the system can possibly send out via any email other than admin? Neither the AOP or the Group email have Outgoing email settings. So I created an Outgoing email, but how do Ink that to AOP?

That’s probably how I tested this a year ago. The admin and support emails were the same so it worked. Now that they are different its become a problem.

Oh my god. The more I test the LTS. the more I feel this should not be an LTS. Its really a Beta, or even just an Alpha.

You guys have some serious issues. The whole email system is broken.

When I go to add Email details for a user, it doesnt do what its supposed to do. I simply create IMAP and SMTP for the user. Then click email address of a contact while logged in to that user, and it states FROM is the User name, but the address from is the admin email???

The correct email is default. First time I tried it was System email by default, with option to send from the correct email. I deleted that user, unselected in email settings for user to use the System email, then re-created the user with the users SMTP and IMAP settings. Then no option, just send through the System email only.

Are other people having these issues??? Seems like email would be a pretty common used feature in a CRM.