remail 0.0.1 → 0.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. data/README.markdown +11 -11
  2. data/VERSION +1 -1
  3. data/remail.gemspec +1 -1
  4. metadata +2 -2
@@ -9,8 +9,9 @@ Google App Engine gives you a free quota of 2000 emails per day or, with the
9
9
  paid version, 7,400,000 emails per day.
10
10
 
11
11
  ## Features
12
- * POST emails to your Remail App Engine in order to send them
13
- * Remail POSTS received emails back to a configurable URL
12
+ * ActionMailer POSTs emails to your Remail App Engine in order to send them
13
+ * Remail POSTs received emails back to a configurable URL
14
+ * Remail will retry the callback if the endpoint is not available
14
15
 
15
16
  ## Setup
16
17
  * Configure and deploy the [Remail App Engine](http://github.com/maccman/remail-engine)
@@ -29,8 +30,9 @@ paid version, 7,400,000 emails per day.
29
30
  If you want to send email on behalf of the application but do not want to use a single administrator's personal Google Account as the sender, you can create a new Google Account for the application using any valid email address, then add the new account as an administrator for the application.
30
31
 
31
32
  ## Receiving email
32
- * Configure the callback URL in your Remail App Engine.
33
- * Create a email controller, that looks a bit like this (remember to configure the routes):
33
+ First, configure the callback URL in your Remail App Engine.
34
+
35
+ Then create a email controller, that looks a bit like this (remember to configure the routes):
34
36
 
35
37
  class EmailsController < ApplicationController
36
38
  skip_before_filter :verify_authenticity_token
@@ -43,17 +45,15 @@ paid version, 7,400,000 emails per day.
43
45
  head :success
44
46
  end
45
47
  end
46
-
47
- The API key is also passed through as an Authorization header,
48
- you should definitely validate that.
49
48
 
50
- You might want to add :email to the filter_parameters configuration, you
51
- don't want your logs being clogged up with emails.
49
+
50
+ The API key is passed through in the Authorization header, you should definitely validate that.
51
+
52
+ You might want to add :email to the filter_parameters configuration - you don't want your logs being clogged up with emails.
52
53
 
53
54
  Your app can receive email at addresses of the following form:
54
55
  string@appid.appspotmail.com
55
56
 
56
57
  ## Misc
57
58
 
58
- To ensure your email doesn't get caught in spam filters, you should follow
59
- the tips in this tutorial I [wrote](http://madebymany.co.uk/getting-email-around-spam-filters-00221) - the important points being setting SPF and MX records.
59
+ To ensure your email doesn't get caught in spam filters, you should follow the tips in this tutorial I [wrote](http://madebymany.co.uk/getting-email-around-spam-filters-00221) - the important points being setting SPF and MX records.
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.0.1
1
+ 0.0.2
@@ -5,7 +5,7 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = %q{remail}
8
- s.version = "0.0.1"
8
+ s.version = "0.0.2"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Alex MacCaw"]
metadata CHANGED
@@ -5,8 +5,8 @@ version: !ruby/object:Gem::Version
5
5
  segments:
6
6
  - 0
7
7
  - 0
8
- - 1
9
- version: 0.0.1
8
+ - 2
9
+ version: 0.0.2
10
10
  platform: ruby
11
11
  authors:
12
12
  - Alex MacCaw