Contribute Confirmation Emails Not Being Sent on Upgrade to WP 4.0/CiviCRM 4.5.3

[peoute]

Another user, Derek, and I have experienced this problem that never seemed to be resolved from a year ago.

http://forum.civicrm.org/index.php/topic,30615.msg147679.html#new

I found the thread via Google, but I wasn't sure if commenting on a thread that old is really the best thing to do, especially if the issue is related to a recent upgrade or something.

There was talk in the old thread about IPN from PayPal . . .

I know double-posting is not great thing to do in forums, but I checked with Donal Lobo and he said go for it. . . :-)

I just upgraded WP to 4.0 and CiviCRM to 4.5.3 over the weekend and am noticing that our contribution forms are not triggering the normal email receipt.

I also noticed the timestamp for the transaction looked right in CiviCRM, but the receipt time sent in the contribution was off in the future a couple of hours.

I can manually send the receipt, though, and when I do, the timestamp is right.

Code: [Select]

Nov 10 01:18:07  [info] Contribution record updated successfully   \\\first transaction?

Nov 10 01:18:26  [info] returning since contribution has already been handled

Nov 10 13:52:18  [info] Contribution record updated successfully    \\\second transaction attempt?

Nov 10 13:52:30  [info] returning since contribution has already been handled

Nov 10 16:39:50  [info] Amount values dont match between database and IPN request   \\\refund of first transaction in PayPal?

[diegov]

Hi, maybe it's not the same thing, I had some problems too with IPN from PayPal and it looks like it was related to PayPal shutting down SSLv3 due to the Poodle vulnerability. PayPal even sent me a PDF about this, suggesting to use TLS in the place of SSL.
In my specific case PayPal was repeating the IPN 16 times each, what lead Civi to send 16 confirmation emails do contributors. PayPal was not being able to see that Civi was acknowledging the payments, but I thing other error could happen.
Here, it looks like I was able to solve the problem shutting down the "Verify certificate" option in CiviCRM administration. Maybe you could try that there.