Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Feature Req: Allow user to set envelope "from" in composition or complete name/address pairs per-source

#128

Users can currently set "Email Address(es)" as comma-seperated values when you edit a Mail Source.

Users cannot change the value of the Full Name for each of those addresses, nor can the envelope be edited during composition.

It would be nice to either have name/address pairs per Source, or a way to edit the envelope-from, or both.

Reported by emory · May 23rd, 2011 @ 07:06 PM

State: accepted
Milestone: none
Assigned to: benny benny

Activity

  1. benny
    benny
    • State changed from new to accepted

    Due to a bug, the list of possible From addresses is not shown in the
    composer when only a single account (with multiple addresses) is
    configured. It is fixed in the next update.

    I guess the comma-separated list could allow explicit full names as
    well. I'll consider that a feature request tracked by this ticket. (You
    are the first to request such a feature.)

    [state:accepted]

    May 23rd, 2011 @ 07:12 PM

  2. emory
    emory

    If it matters to you or anyone else, the reason I use this feature is two-fold.

    1) I use delimited email addresses for list memberships. I don't know if this is a silly practice anymore, it's just habit from years of Internet email and getting a lot of spam. So some of my addresses are user+listname@domain.tld or user+keyword or user+vendor.

    I like knowing when someone I've given my email address to has sold it or used it for marketing. It's entirely possible most users have moved to "throw away" email accounts for that type of thing.

    2) I routinely correspond with people who write a "role account" such as "security@" or "abuse@". I usually don't want to have my Full Name with those emails, instead electing to use "FictCo Security" or "FictCo Abuse Desk". Sometimes those IMAP spools are shared stores, "public folders", etc.

    May 23rd, 2011 @ 07:20 PM

  3. benny
    benny

    Always nice to know the use cases.

    1) If your messages have an X-Original-To or X-Delivered-To header then
    you do not need to add these addresses. They should be used
    automatically when replying. Try it out in the next update where you can
    actually see the From-field. (And I definitely do not consider it a
    silly practice to use multiple addresses.)

    May 23rd, 2011 @ 08:59 PM

  4. Emory  Lundberg
    Emory Lundberg

    For some reason I can't login with my OpenID again, but I'm the author of the req.

    Do you know when the next update will be available?

    May 25th, 2011 @ 08:46 PM

  5. benny
    benny

    It always takes longer than I expect, but it is a matter of days and not
    weeks. If you want to test it early you can write a feedback email.

    Lighthouseapp are good at answering support questions, so maybe you
    should write them about the OpenID issue.

    May 26th, 2011 @ 04:46 AM

  6. benny
    benny
    • State changed from accepted to fixreleased

    I think you have all you asked for in this ticket now, but I've forgotten to update it. Just to be clear then the “Email Address(es)” field in account settings can, for example, be:

    address1@example.com, Name Two <address2@example.com>, Name Three <address3@example.com>
    

    Also described in the manual.

    May 10th, 2012 @ 12:43 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.