bbs.spamgourmet.com

An addition i'd love to see for Reply Address Masking is the ability to include the full name portion of the From: and Reply-To: headers i.e.:

From: Joe Blow <jblow@server.com>

vs.

From: jblow@server.com

I want to use SG to correspond safely with friends that i know have unsafe emailing habits (non-BCC emailing to large groups, forwarding chain letters, etc) that will get my real email address on spamlists. SG disposable email addresses are fine for impersonal corporations' email bots and web forms, but are kind of jarring in my friends' inbox lists, where they would normally be replaced by a full name if it was provided.

I don't know anything about how it would be implemented on the back end, but the 'send a message from one of your disposable addresses' page would require only one more text field.

This idea has similar goals to what xdcdx was requesting in this post but from another angle.

what do you think?

Josh,

That sounds like a good idea. Of course, this is one more field in the database.

Maybe if when the disposable address is create on the send page if you selected the option it could use the name as stored in our registration at SG or entered. This would at least limit having to store stuff. Once the address is formatted once if it is like my outlook the actual description is a part of the email address Joe Smith <xxx.t.jsmith@SG.com> if I remember correctly

what if it used the display name (if there was one) from the message as it received it? E.g, I want to send a message through sg -- from my email client, I send a message that's from

Joe Blo <joeblo@example.com>

to the redirecting address, then sg replaces it with:

Joe Blo <someword.joeb@s g .com>

-- it would still need to be an optional feature -- if it's an account-wide option, we wouldn't have to make any database changes to do it.

That's a very good idea!

Yeah, what they said.

I came to the forum today to request this feature (a way to send messages with a human name in addition to an email address), and I see it's already been suggested (a few places).

I have suggested this and several similar ideas here. To sum up the differences:

The one thing I suggested that I don't see here is that it would be nice if the "from" field on messages sent to a disposable were not modified at all, but a "reply-to" field was added specifying the sg passthru address -- or, if a "reply-to" field exists already, simply replace it with an sg passthru address going there. This should be an easy patch.

3 years ago, there seemed to be some enthusiasm for Display Name retention. Has anything happened with it since?


> it would be nice if the "from" field on messages sent to a
> disposable were not modified at all

If "no modification" is merely one selectable variation of From field treatment, then I do not care if "no modification" is selectable. I just will not select the "no modification" variation.

The From field treatment I want is the treatment Josh suggested

what if it used the display name (if there was one) from the
message as it received it?

I'd like to see this feature added too - it would be most useful when emailing "non-technical users" (who are the least reliable in keeping addresses private) who otherwise might mistake emails from xyz.20.abc@spamgourmet.com as junk.

crazycomputers wrote:it would be nice if the "from" field on messages sent to a disposable were not modified at all, but a "reply-to" field was added specifying the sg passthru address

My suggestion would be to move the original From and Reply-To fields into custom headers (like X-sg-orig-reply-to and X-sg-orig-from). You'd have to View Full Headers on the message to see these headers, but you'd only need to do that if you needed to relay the email address to someone else.

Leaving the original address in the From: field is a bit dangerous - you never know some email software might actually send it there direct!!

My strong consent to Josh's great idea.

I cannot remember a single mail in which I would have preferred to not have this happen.

I may have misunderstood other options mentioned here, but I would strongy regret if my protected address would show up anywhere in a message, of course including the header.
Arick

Josh's suggestion applies to messages that you send out "from one of your disposables" to a Ty Coon.

I fully support Josh's idea (hopefully there's no-one here that also wants to hide their identity).

My suggestion applies to messages that Ty Coon sends to one of your disposable addresses. Usually the system makes it obvious what their address is, but not always. That's why I would like those extra headers.

Nick.

Thanks nick4mony, I understand now (bejond Josh's idea).

And yes, since 2003 I also have had a few rare cases where I needed the sender's (Ty Coon's) clear address. To relay it, or to start communicating with a different "from" of mine, like in some cases my protected address. This seemed a bit risky to do, as my head is dominated by work, beauty and speed rather than with what sg actually does within return address masking.

Recently I happened to get two identical newsletters from one Ty Coon. One to an sg address, one to my protected (forgot I had registered in pre-sg days). This case showed me, that sg does reliably deliver the clear text sender address:
Original FROM = "name" <address>
Masked FROM = "name - address" <masked address>

But the original REPLY TO is found masked only in the header. It may really be a good idea to add X-SG-FROM and X-SG-REPLY TO fields. If just for consistency...

I also found a masked RETURN PATH field, but dunno if it is ever needed.
Arick

(I'd like to again expess my support toward Guest's initial idea and Josh's solution for a full name portion of our FROM)

WOW! is this an old thread!

josh wrote:-- it would still need to be an optional feature --

FWIW:
It being an option is inherent. Adding a display name could turn it on, omitting it cannot.
Arick

miniscus wrote:This case showed me, that sg does reliably deliver the clear text sender address:
Original FROM = "name" <address>
Masked FROM = "name - address" <masked address>

It doesn't always do that. A few times, I've got a FROM line like this:

Code: Select all

From: +MYWORD+MYSGUSERNAME+25112eebc7.CCCustomerAdvocacy#virginCOMPANY.COM@spamgourmet.com

No sign of the clear-text address. Bits in capitals have been replaced (including the tld of the company's domain name). It's one of many Virgin companies.

Nick.

miniscus wrote:my head is dominated by work, beauty and speed

<SIGH>Fast women and slow horses, huh?</SIGH>