CiviCRM Community Forums (archive)

This info is only for CiviSMTP clients using Drupal 7 + CCRM 4-4.0.5

THIS ISSUE WAS FIXED AS OF CIVICRM 4.0.6

There are 2 known issues:

1. in CCRM < 4.0.5 you will get "Invalid login" error when testing your CiviSMTP settings. This will also prevent replies/bounces/unsubscribes and etc from working
2. in CCRM 4.0.5 processing of replies/bounces/unsubscribes and etc doesn't work. more details here: http://issues.civicrm.org/jira/browse/CRM-8638

This issue was fixed as of CiviCRM 4.0.6.

If you cannot upgrade to CiviCRM 4.0.6 or higher you can follow the instructions below and apply a temporary patch.

Please note: CiviSMTP is not responsible for any issues that this patch might cause and we won't provide any support for it. Though it worked in our tests and didn't cause any issues, if you decide to use it it will be at your own risk.

We will only provide support for the official fix once it comes out in 4.0.6

**************************************************************

For all users using CCRM 4:

- download and rename attached soap.php.txt to soap.php and DrupalNewAuth.php.txt to DrupalNewAuth.php
- on your server go to <path_to_drupal>/sites/all/modules/civicrm/extern
- cp soap.php soap.php.orig
- now upload the provided soap.php into that dir - you can do this using sftp client
- then go into <path_to_drupal>/sites/all/modules/civicrm/CRM/Utils/System and place the DrupalNewAuth.php into that dir

Additionally for users running CCRM 4.0.5

Locate  <path_to_drupal>/sites/all/modules/civicrm/CRM/Utils/SoapServer.php and make the following change:

Index: CRM/Utils/SoapServer.php
===================================================================
--- CRM/Utils/SoapServer.php   (revision 35660)
+++ CRM/Utils/SoapServer.php   (working copy)
@@ -122,7 +122,7 @@
      * @access public
      * @static
      */
-    public function authenticate($name, $pass, $loadCMSBootstrap = true ) {
+    public function authenticate($name, $pass, $loadCMSBootstrap = false ) {
 

CiviSMTP Support

Is this issue fixed in CiviCRM 4.07?