reply no longer uses TO address in FROM address
 

A while back REPLY used to (at least sometimes, wasn't consistent) the FROM address of the email I was replying to <edit: as the TO address of my reply>. I liked that because I assign all my addresses individually (e.g. yourname@mynmame.fastmail.com).

When it doesn't use the FROM address, I have to click 'change' and paste (or type) custom address in.

Anyway to tell it to use (default to) the FROM address of the received email being replied to as the TO address of the REPLY?

If you have a "personality" set up, that has the same address as the address that the message was sent to, then that address will be used as the "from address" when you reply.

If you have no personality set up your "default personality" will be used.

You can create and delete personalities (and set your default personality) by going to the "Options" "Personalities" section, from the menu at the top of the screen.

Actually, until recently this wasn't needed. The X-Delivered-To header of the original email was used. This means that even external addresses (such as @spamgourmet.com) were automatically used in the From field.

I can confirm that this is a new bug.

Prog.

thanks Prognathous!
 

I edited my original post because I realized I might not have explained it clearly. Hope I didn't make it worse, but I think you know what I am referring to. Hope they kill the bug.

The problem with using the X-Delivered-To header is that it doesn't work with external addresses. Spamgourmet is a special case because its header rewriting.

What do you mean it doesn't work? It sure used to work until some change in the code caused a regression and now it doesn't.

Prog.

I mean in the sense that for an external address that's forwarded to Fastmail, the x-delivered-to address is not the correct one to choose, it's often an address one is trying to conceal.

Ok forget the X-delivered-to, let's focus on the fact that it worked perfectly well until recently, but doesn't anymore. It's definitely a regression.

Prog.

here here
 

was my favorite 'feature'

For a while (for around 2 weeks, some months ago) we used x-delivered-to, but it broke on forwarded messages, so we reverted that change.

I'm not aware of any other regression - am I missing something?

Are you sure it was only for 2 weeks? :confused: it seemed quite a bit longer than that.

Anyway, this was an extremely useful feature, and I hate to see it going away. I must say that whatever the regression was with forwarded messages, I didn't notice it. Was it a serious enough breakage that warranted backing out this feature?

Prog.

Yes it caused a lot of complaints, since it caused people's real username to be revealed.

That sounds like a darn good reason so thanks for that but are there still 3 ways a "real" address can be revealed when a user only uses aliases? (sieve rejects, FM rejects of certain file types and FM notices of accounts over quota)
Am I missing any?

Sherry

Sherry, are those all in the wiki?

I don't think so. I rarely go to the wiki so I can't be sure. Also, I don't know if any of those things have been fixed yet or even if I have it right. I just remember different post about what I mentioned and usually remember things if they have something to do with security of my account (real address).

Sherry