foodsoft/config
Patrick Gansterer 4e35e2d58e Add handling for message reply via email
If the reply_email_domain configuration is set the messages plugin will
use unique Reply-To addresses for every email. They contain enough
information to reconstruct the message context and a hash to avoid
user forgery and spam.
A mail transfer agent must be configured to call the new rake task
foodsoft:parse_reply_email for incoming mails. The rake task requires
the receipt of the mail in the RECIPIENT variable and the raw message
via standard input. An example invocation would look like:
rake foodsoft:parse_reply_email RECIPIENT=f.1.1.HASH < test.eml
2016-03-04 18:11:27 +01:00
..
environments Merge branch 'dockerization' 2015-05-08 13:06:15 +02:00
initializers Disable error page for development 2015-09-05 15:04:56 +02:00
locales Make unassigned tasks more prominent in the dashboard 2016-03-04 17:15:45 +01:00
app_config.yml.SAMPLE Add handling for message reply via email 2016-03-04 18:11:27 +01:00
application.rb Avoid Rails 4.2 deprecation warning 2015-11-14 18:23:33 +01:00
boot.rb First step for upgrading to rails 3. 2011-05-11 01:32:21 +02:00
database.yml.MySQL_SAMPLE adds a foodsoft:setup_development rake task 2013-05-26 14:02:16 +02:00
database.yml.SQLite_SAMPLE adds a foodsoft:setup_development rake task 2013-05-26 14:02:16 +02:00
deploy.rb.SAMPLE deploy: persist changes to session_store iniitalizer [ci skip] 2014-02-03 10:53:22 +01:00
environment.rb migrate to Rails 4.0 (closes foodcoops#214) 2014-02-24 12:46:28 +01:00
i18n-js.yml handle ajax errors (closes foodcoops#300) 2014-07-02 13:55:05 +02:00
navigation.rb Add role_invoices 2016-03-04 16:06:02 +01:00
routes.rb Upgrade to rails 4.2 2015-01-02 17:43:44 +01:00
schedule.rb Fixed whenever cron config. 2013-09-18 14:52:23 +02:00