Zoltán Lehóczky

I'd add two things we'd really need, both of which I opened threads about before on the old UserVoice:

1. E-mail archiving: even if a given e-mail is deleted from the corresponding mailbox, keep it visible in Sell (even without attachments it'd be fine). Currently it depends on the owner of the mailbox how long an e-mail is visible in Sell, and this can lead to issues where other people can't access them anymore.
2. Ignore patterns of e-mail addresses: Basecamp notifications are sent from e-mail addresses unique to that notification (e.g. jon-doe-7239aodwo8d@replies.3.basecamp.com). Similarly for GitHub (e.g. reply+8ksd83llg03jdslsd93sdfldoe@reply.github.com). This means that each and every single such notification shows up as a new person under "Suggested people" in the e-mail integration, and I routinely have to clean this list up. Instead, I'd like to see a way to tell Sell to ignore all of the e-mails with a pattern, at least along the lines of "ignore e-mails coming from @replies.3.basecamp.com".

I see, thanks, Pati.

Anybody with feedback on this?

Sell will bring every single new e-mail address under Communication Center -> Suggested people. This is mostly what we want, but there are services that use random e-mail addresses for each message for the Reply-To field, and these need to be continuously cleaned up there too. Examples:

• GitHub sends notifications from notifications@github.com but this is not causing an issue. However, the Reply-To field is always something random (so you can reply in an e-mail), like reply+LONGRANDOMIDENTIFIER@reply.github.com. These all show up in the Communication Center.
• Same thing with Basecamp. These all are sent from but the issue is that the Reply-To field is something like user-name-LONGRANDOMIDENTIFIER@replies.3.basecamp.com.

If we could just tell Sell to always ignore the domains reply.github.com and replies.3.basecamp.com, or perhaps a pattern (like "e-mail ends with @replies.3.basecamp.com") for more flexibility, it would cut down on so much mindless cleanup chore.

Please consider implementing this!