Posted by Jody Lynn on November 23, 2011 at 10:13pm
3 followers
Jump to:
| Project: | Reroute Email |
| Version: | 7.x-1.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
We needed to allow a wildcard for the username (*@example.com) in the pass-through list.
| Attachment | Size | Status | Test result | Operations |
|---|---|---|---|---|
| reroute_email.patch | 1.62 KB | Idle | PASSED: [[SimpleTest]]: [MySQL] 56 pass(es). | View details | Re-test |
Comments
#1
I'm not inclined to favor this patch, as the module is intended for development, not for fancier things. I haven't come to terms with the pass-through yet :-)
#2
Well, we're using it for development, but we have 15 developers working on the site and a whole slew of testers with email addresses of one organization, so it's inconvenient to add every email for everyone who ever might test the dev site to see how various emails are working.
#3
That's reasonable. I'd think it would be a lot easier to have a shared email account that you deliver these things to.
I'm listening :-)
#4
I'm using it now for another project, so it's proving useful. It seems a lot faster to add passthrough for ours and our clients' domain rather than asking them for a list of all staff members that might be involved in QA and setting up a shared email account for all of them (and then confusing them by having them all get all of the emails). The main reason these QA folks even need to be getting emails is that they keep needing password reset, so whatever I do needs to be simpler than remembering a password.
#5
I don't currently like the way the passthrough email is jammed into the same field with the "to" emails. IMO we should make these two separate fields. I'd probably be more OK with this at that point.
#6
Cross-referencing with #1571500: Separate the recipient (list) from the address whitelist. Add domain whitelist.