The āFromā dropdown still does not work and trying to send email results in the "call your adminā pop-up.
It has been a month now. Is there something that I might not have configured correctly? All the permissions look correct.
The ātestā email works fine.
Is it just me or are others having the same issue?
Nope us too, itās completely rooted.
We just tried a brand new clean install of 7.9.3. Added emailed settings and one contact record and still CANNOT send email. Get ācall your adminā message and then you click elsewhere and it logs you out.
I thought that by now they would have fixed this. Obviously not. Fortunately I donāt use email from the CRM all that often.
Iām rather disappointed in this new version. The theme is hard on my eyes (I want my old black and white screen back) and the response is easily 4 times slower than the previous version.
Iām looking at making a change to a different CRM although I know that any migration will be a nightmare to do.
The āFromā bug has been fixed at least twice, but it keeps creeping up in new forms. Anyway letās try to check this thoroughly, case by case (Iāll be doing a few tests myself, I installed 7.9.3 today):
Have you configured an individual email account, not just a system account?
Do you have configured inbound accounts, or just outbound?
Hi,
Can you confirm if you are using mssql? Iāve raised an issue here: https://github.com/salesagility/SuiteCRM/issues/3901 that I think may be related.
Thanks
There is an email address for me, the admin. Do I need an āindividualā account? I never had to do this in previous versions of Suite.
I do not want inbound email. That is a security risk that I want to avoid. I only want to send email from SuiteCRM.
Where is the documentation for setting up email?
Thanks.
@dev77 please answer the Microsoft SQL Server question, there is a known issue with that.
There is no documentation yet for the new module, itās still being worked on.
My questions about inbound accounts and individual outbound accounts are just meant to gather information about any possible bug, I understand why you might not want to configure inbound email.
We are using mySQL 5.1.73
We will upgrade in early September to 5.6 or 5.7 ā¦ not yet sure which.
Have you tried to re-enter the password in settings?
It seems to get forgotten quite often, Re-entering it in the email settings worked for me.
I re-entered password. No change. The ātestā email works fine. There is still nothing in the āFromā box.
Whatās next?
Oops! That is not a supported version of MySQL for a long time, since SuiteCRM 7.4!
https://suitecrm.com/wiki/index.php/Compatibility_Matrix
I think this will bring you many more problems besides this oneā¦ you really need to consider working on that upgrade. Otherwise it is better to delay the SuiteCRM upgrade alsoā¦
@phil that bug with not saving the password is supposedly fixed in 7.9.3
not sure if you tried deleting the email account in SuiteCRM and then re-entering the info as a new email account?
Also, fixing permissions seems to need to be done quite often so that couldnāt hurt,
Fixing the permissions via a SSH command line works better than just using an ftp program or a Cpanel file manager in my experience
Permissions are fine, TTBOMK. I run this after each update via ssh
chmod -R 755 suite
cd suite
chmod -R 775 cache custom modules themes data upload config_override.php
As for mySQL version, I didnāt know about the need for 5.5+. Everything works wellā¦ except email so I would tend to think this is not the problem. We canāt update until after Sept. so I guess we will just lumber along with what we have.
The deprecation of SQL and PHP versions normally is done for a reason - to introduce some code that wonāt run on the old version. So itās safe to assume that SuiteCRM will break somewhere because of your MySQL version. You just donāt know where. And it adds a shadow of suspicion over any bug that you have - is it because of the SQL version or not? Very hard to manage a system like thatā¦
Maybe you can try the upgrade on a clone just to see what it changes?
Another thing, both to you and to Phil: if you have to keep resetting your permissions, youāre doing something wrong. It really shouldnāt be necessary. Permissions donāt change themselves, something changes them, and there are only two or three possible causes (cronjobs running with the wrong user, default_permissions in config.php, changes you make when logged in as a different user, etc)
Iāve never figured out why a Suite update changes permissions on: /suite/cache/jsLanguage/en_us.js
and a few other files I forget.
Same thing happened with SugarCRMā¦ so we just make it part of our upgrade process to set permissions with chmod above. Only takes a few secondsā¦ quicker than trying to figure out what the problem is in the first place.
No, it doesnāt change permissions on those files, or on any files, if correctly configured.
I admit it sometimes is too tricky to get to a point where it is ācorrectly configuredā, but itās well worth reaching that point.
If you just cover the wrong permissions with a generic command to reset everything, that means you never find out the cause of the problem. Furthermore, your system runs for hours/days/months with wrong permissions, you notice some of the issues that creates, but not necessarily all of them. Random code can break in random moments and create random problems in your database or files, and these problems donāt get fixed with your next chwon/chmodā¦
We upgraded to MySQL 5.6 and Suite email in 7.9.3 still does not work. There is nothing in the From box.
Did 7.9.4 fix this? If not, I donāt plan to upgrade. Iām to the point where I am going to have to look for a replacement for Suiteā¦ either free or paid. Maybe this https://www.x2crm.com/ or something similar. We donāt use 95% of the functionality of SuiteCRM but we do need outbound emailā¦ and so far we are no closer to getting this to work than weāve been since the beginning of 7.9.
Iād like to stay with Suite. Does anyone have any ideas on what to do. We do NOT want (nor will we permit) inbound email. Just plain old outbound email is all we need (and it would be nice if Suite was as fast as the previous versions and if we could get rid of the horrible colors of this theme. We have a color blind person who has difficulty with it.)
Upgrading to 7.9.4 is a no-brainer - itās just a simple fix or two. But donāt do it with hopes of getting your Email magically fixed, I donāt think that will happen.
Some reconfiguration might help. Checking your logs might give you clues that you can use to search the current GitHub Issues.
But jumping onto SuiteCRM in version 7.9, hoping to use the Email module more than anything else, is really bad, bad luck. Terrible moment. One thing you could do is simply use 7.8.5 - that sends emails.
If you stick it out with 7.9, it should be working any moment now (I know, this is being promised for a long time nowā¦)
When everything is fixed I donāt expect inbound email to be necessary to send outbound email.
Iāll give Suite another couple of weeks. I guess what really bothers me is that the new theme has been roundly panned by the community and yet nothing has been done to fix it. I know there is a third-party theme out there but that is not a path I want to take right now.
So you have a production version of the CRM with a theme that vision impaired people canāt use, that does not send outbound email, and which contains a bunch of other bugs, some minor some major. Iām just wondering if Suite is going down the same road as Sugar did and is putting more resources into their commercial business (as expected) and very little into the open source area.
Iāve been a software developer for 40 years now and in my wildest dreams I canāt figure out how this new theme ever made it past any kind of peer review or community discussion. And to not have a major function like email be broken for as long as it has gives me the distinct impression that something else is going on behind the green curtain! Sugar went this directionā¦ I hope Suite isnāt as well.
I am not worried about them going āthe SugarCRM wayā because their promise to stay open-source forever keeps getting repeated over and over again.
The simplest explanation is that theyāre trying, but they have limited resources, and they make mistakes like everyone else.
Greg Soper, the CEO recently explained it like this: