emails not sending from sugar (receive works)

[florenceit]

I have a few email related problems since migrating to a new server, using php5 and mysql5. latest sugar OS (4.5.1d)

when i compose an email and click send in sugar the screen goes blank within the web browser (all white). nothing in sugarcrm log.

when i send email campaigns the screen goes mostly blank leaving a number 1 under the sugar menues and a link to view the scheduler. the scheduler shows the emails with a scheduled send date of 1996

sugarcrm.log says "scheduler got a bad execute time" with a date of 1969-12-31
(only for the nightly attempts to send from cron: no errors are reported when i manually try to send)

does anyone know if the dates are the problem , and/or where the heck these dates are coming from? my system date and time are correct.

when i try to manually send queued emails it does the same thing with a mostly blank screen, a number 1, and a link to view queued emails. status says checked, send attempts is 0. nothing in the logs. i have other php mail enabled software on this system that is sending emails ok.

i was getting a curl error and i installed the curl module and that error disappeared (just mentioning not sure if related).

any tips? my primary use for sugar is email at the moment. thanks.

[florenceit]

anyone have any idea where i can look to get a clue as to where its failing?
thanks

[andydreisch]

Hi florenceit, the upcoming patch 451e has a few bugs that address date issues generally.

Please enter a bug in bugs.sugarcrm.com and I'll ask the Dev team to look into this as well.

Andy

[florenceit]

thanks Andy i will.
we went through this recently on another issue. are you sure its abug though? i opened a case with no response on thios from yesterday. is there a method i am doing wrong for opening a support case as a sugar open source customer ?thanks.

i just enterewd bug info and the screen said (after a lot of typing) "please enter a valid bug"

i think you might need to have a talk with some of your software andy

-matt

[susiewilliams]

Hi there,

I'll answer for Andy, as I saw him running off to a meeting just now.

Regarding the Bug portal, yes there is an issue with it now and IT is working to resolve it as quickly as possible.

Regarding submitting support cases as an Open Source user, our Support team handles cases from customers who have a contract with us; either Enterprise or Professional customers, customers of SugarNetwork, or any other type of customer who has a support contract with us. As a matter of fact, the newest podcast (just released yesterday) explains the differences between cases and bugs, and describes who can file which type.

For Open Source users, you can always ask questions and get support from the community by posting your questions in the forum. The community exists for people to help each other out!

[florenceit]

im an open source customer (not user,) i forget the name you call it, sugar network? it's paid support for a year on the open source version: with outlook and word plugins. how does that type of customer submit support.

[susiewilliams]

Hi FlorenceIT,

It looks like you did the right thing... I checked with support, and they have your case number and will be contacting you shortly.

[florenceit]

I received a response on my case from a Jennifer: she suggested checking if mbstrings were enabled in my php5 stack: it wasn't installed or enabled (opensuse 10.1) , that did the trick, all is good!! i have learned a lot about php extensions recently, namely, that there are some and that specific ones need to be installed (ahem... )
thanks for your help and i hope this helps someone else w/this prob.


as a way of testing if mbstrings is your issue she told me to
enable display_errors in php.ini,
then try sending an email and check to see if a fatal error is showing that looks like the following?

Fatal error: Call to undefined function: mb_encode_mimeheader() in /usr/local/sugarcrm/sugar/include/Localization/Localization.php on line 314

if so enable/install mbstrings did it for me.

[tclevela]

There are a bunch of mbstring entries in the php.ini file. Which ones did you actually turn on or set that fixed the issue?

[florenceit]

Hi
I had to install the modules and fortunately there was a RPM for that so it was easy, didnt have to edit anything as i recall.if this is what you think your prob is try researching installing php modules for your platform