#1402
- Created on2013-02-27 18:39
- Reported by
- StatusMigrated
- PriorityNormal (3)
- Assigned to-
- Milestone
- Plan Level-
- Due Date-
Cloudmailin integration not adding tasks to Tracks
When setting up my install I inserted the "secret code" in the correct area of the site.yml file.
I then created a context @NoContext.
Under Preferences I set the Incoming email to be my personal email address that I would use to send an email to the cloudmailin address.
I then sent an email to the cloudmailin address that is supposed to then post to my tracks.
I then get a undeliverable notice back in my email.
However the email reached the cloudmailin servers because
when I view my cloudmailin account the message shows up with error code 403 and when
I click on the message details it reads "Message signature verification failed."
The only place I know to put anything about signatures is the "secrect code" in the site.yml file
Did I make a mistake by putting my personal email address in the Preferences section???
Should this have been the cloudmailin email address that I am sending tasks to?
I was not able to find documentation on how to properly configure this integration...
There were other documentation by clicking the ? and then Integrate Tracks on the menu but I have not been able to find it for the Cloudmailin integration.
If this integration can be setup to be functional and I can get it working, I would be happy to write the accompanying documentation on the proper configuration.
Thanks
Steve
I then created a context @NoContext.
Under Preferences I set the Incoming email to be my personal email address that I would use to send an email to the cloudmailin address.
I then sent an email to the cloudmailin address that is supposed to then post to my tracks.
I then get a undeliverable notice back in my email.
However the email reached the cloudmailin servers because
when I view my cloudmailin account the message shows up with error code 403 and when
I click on the message details it reads "Message signature verification failed."
The only place I know to put anything about signatures is the "secrect code" in the site.yml file
Did I make a mistake by putting my personal email address in the Preferences section???
Should this have been the cloudmailin email address that I am sending tasks to?
I was not able to find documentation on how to properly configure this integration...
There were other documentation by clicking the ? and then Integrate Tracks on the menu but I have not been able to find it for the Cloudmailin integration.
If this integration can be setup to be functional and I can get it working, I would be happy to write the accompanying documentation on the proper configuration.
Thanks
Steve
Leave a comment
According to the commit where the plugin was added: c0956a7e761aaf7c2bfd34e31e84e54f2628c2f6 this requires the gem 'mail'.
This dependency was removed with commit 393eae193722c71473900de610ff73aa5f366f37
So could just be a case of adding this back in as a dependency?
EDIT
No. This is definitely already a dependency. I can see it in the Gemfile.lock and the following looks good on my setup.
bundle check
Resolving dependencies...
The Gemfile's dependencies are satisfied
root@home:/var/www/tracks# bundle show mail
/var/lib/gems/1.9.1/gems/mail-2.5.3
So with this in place I now get the same error as the original poster. The 403 is returned because the check of the signature has failed.
In my site.yml I have the following which should get picked up:
which is obtained from the pages at cloudmailin.
I'll try to look at this further as time permits.
This dependency was removed with commit 393eae193722c71473900de610ff73aa5f366f37
So could just be a case of adding this back in as a dependency?
EDIT
No. This is definitely already a dependency. I can see it in the Gemfile.lock and the following looks good on my setup.
bundle check
Resolving dependencies...
The Gemfile's dependencies are satisfied
root@home:/var/www/tracks# bundle show mail
/var/lib/gems/1.9.1/gems/mail-2.5.3
So with this in place I now get the same error as the original poster. The 403 is returned because the check of the signature has failed.
In my site.yml I have the following which should get picked up:
- Cloudmailin Secret:
which is obtained from the pages at cloudmailin.
I'll try to look at this further as time permits.
Migrated to GitHub issue #1402