mlandauer / cuttlefish Goto Github PK

This is possible. Handle this by attaching the logs to the most recent email with that queue id. Currently it's just picking the first one it finds in the db (in some arbitrary order).

When emails have hard bounced any subsequent emails to the same address will not be sent.

Add option to reenable sending for a particular address
Add this feature to the API as well so that the app can do it

This project looks like a brilliant starting point
http://designmodo.github.io/Flat-UI/

And do this on a per-application basis.

You could something like figure out the domain where all the emails for a particular application are coming from. Say that was "mydomain.org". Then assume you'll want to use a CNAME like email.mydomain.org. When Cuttlefish starts up it checks for email.mydomain.org being a CNAME for the cuttlefish server. If it is just use that for the link and open tracking. If it isn't then offer a suggestion to set it up.

Some directory looks to be wrong

There is some magic that can partially achieve this...

Useful to find out how emails are being used. Are people forwarding them? If so, what emails?

Because it is apparently the standard

http://en.wikipedia.org/wiki/Feedback_loop_(email)

Or is there a more direct / modern way?

http://xkcd.com/520/

5.2.2 is mailbox full. It is a permanent error that should be treated as temporary.

This is so when you are using Cuttlefish and you're looking at the email history for a particular email address and trying to figure out what's going on you'll get a link in the interface that links to your application admin interface for that user.

This makes things very easy.

http://en.wikipedia.org/wiki/Variable_envelope_return_path

To make the tests a little more concise

Currently it will parse over the old stuff first.

Perhaps it could sit and tail the new stuff first and in the background catch up with the old stuff.

Navigate to page that shows logs that can be toggled to display.

Refresh the page.

Press the toggle. Everything display and hides nicely.

Then navigate to another page and then hit back.

Press the toggle again. It flickers weirdly on and off.

No doubt something to do with turbolinks / js

RFC 3463 helpfully lists all the extended codes. 2.x.x means successful delivery.

2.6.0 doesn't actually even make sense as status code. See this awesome exchange from 2003:

http://www.zmailer.org/mhalist/2003/msg00256.html

A place where all the messages of recommendations go

This could be a fixed number of emails, a certain amount of disk space or a certain amount of time

Instead of browsing email addresses it could be useful to see which domains are getting the most emails and if some of them are responsible for more of the hard bounces.

I think it doesn't run deploy:update on deploy:migrations. There's a comment in deploy.rb about it