| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
| |
I think I was wrong in a83b379fd2d676172855825d0592937b234371e2 in
assuming that all email gets properly encoded for transfer. Looking
at the mail gem load method
https://github.com/mikel/mail/blob/b159e0a542962fdd5e292a48cfffa560d7cf412e/lib/mail/mail.rb#L175a,
it reads raw email content from a file in binary mode. So this commit
makes both reading and writing the raw_email a binary mode operation
and adds a data_as_text method for displaying the data in the admin
interface that coerces it to valid utf-8.
|
|
|
|
| |
Move setup to spec - not in common with other specs.
|
|
|
|
|
| |
We don't write the data for a raw email to the database anymore.
It's written to a file.
|
|
|
|
| |
Picks these up in `rake notes` and adds semantic meaning
|
| |
|
|
|
|
|
|
| |
be in the database (we never write to them, for example), and they bloat it unecessarily, making backups etc difficult.
NOTE: this migration could take a *very* long time.
|
|
|
|
| |
flexible (because STDERR is always the system standard error file descriptor, whereas $stderr can be replaced by some other ruby object to handle error output).
|
| |
|
|
|
|
| |
Rails
|
| |
|
|
http://blog.aradine.com/2009/09/rubys-marshal-and-activerecord-and.html
https://rails.lighthouseapp.com/projects/8994/tickets/1063-binary-data-broken-with-postgresql-adapter
|