Emails in FAS

[brett lentz]

Perhaps what's needed (or needed to be leveraged, if it already
exists) is a central mail gateway or two (one for production, one for
staging?) that can serve as a choke point for applying management and
routing policies.

Postfix can be configured to do some fairly fancy routing, and it
would allow you to route all staging e-mail to a central place for
grepping or reporting.

Additionally, the Lamson project (http://lamsonproject.org/) might
provide a good framework for developing more complex mail processing
applications or tighter integration of existing apps with SMTP if
there's desire for such things.

---Brett.



On Sat, Aug 28, 2010 at 6:00 PM, Mike McGrath <mmcgrath at redhat.com> wrote:
> Starting from our upgrade to this afternoon emails in FAS weren't being
> generated correctly.  The biggest impact from this was new users, who
> signed up but never got their welcome email with a password.
>
> I've corrected the issue (configuration needed to be set to smtp) and I've
> sent emails to the impacted new users (there were 39 of them total).
>
> The bigger thing here is that we need to think about how to do email in
> staging.  Right now it's disabled.  I'd like emails that come through
> those hosts to be easily identifiable somehow.
>
> I'm open to ideas?  Is there a way to inject [staging] into their subject
> with an appended --- staging body at the bottom so we can link to the wiki
> explaining why they got the email and what it means.
>
> Maybe even limit recipients.  My concern here is, lets say I'm testing
> packagers.  If I apply for packagers in staging for testing.  All the
> packagers (the actual ones) are going to get emails about it.  That's just
> going to cause confusion.  I'd prefer that doesn't happen... so we
> disabled emails altogether.  But clearly this fas error is a good reason
> to be able to test emails in staging.
>
> I'm open to ideas here, I'll keep chewing on it myself.
>
>        -Mike
> _______________________________________________
> infrastructure mailing list
> infrastructure at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure
>