Extension addresses with "-" (for example [email address]) don't
work.  They bounce.  This is the case with GA and standard gmail.
This makes it nearly impossible to migrate from an account that used
TMDA to gmail or GA.

Extension addresses with "+" (for example [email address]) work
in GA but not in standard gmail.  This is sort of strange because a
gmail blog article says they should, but at least for me the messages
disappear (don't bounce, never get delivered).

Most TMDA sites use "-" because that is the recommend extension
delimiter.

Is there anyway to get extension addresses with "-" delivered in GA or
gmail?  Or will these services remain forever unaccessible to former
TMDA users?

(For those who don't know, TMDA users have handed out zillions of
addresses extended this way as a spam reduction mechanism.  It is
impossible to migrate if all these addresses bounce.)

If I send a message to an address containing a "-" and have it
forwarded to Gmail, it is delivered without problems in both a GA and
standard Gmail account,

I routinely use "plus addresses" in both accounts as well, and
messages sent to those addresses are delivered without problems.

Maybe the problem is TMDA.

On Jul 5, 1:12 pm, BigBaaadBob wrote:

On Jul 6, 1:17 am, bkennelly wrote:

I think the OP is referring to migrating a domain that previously used
TMDA to a Google hosted domain, not forwarding a domain hosted
elsewhere using TMDA to a Google hosted domain.

There is a workaround for the "+"/"-" mismatch, but probably
impractical. GA lets you create aliases for users, which can contain a
"-" character, so if you previously had user-foo[AT]example.com, you
can edit the account for "user" and add an alias of "user-foo".

On Jul 5, 4:12 pm, BigBaaadBob wrote:

In my experience they work in both. I've been using them with Gmail
for a couple of years, and GA for about a year.

Can you post a link to that? I ran across your posting when trying to
find Google's official documentation on address extensions for a
colleague, and never could find it. Apparently they don't refer to it
using any of the common terms, and you can't search on a literal "+".

There's a larger, more general problem with the "+" separator
character: due to buggy validation rules in common use, about 50% of
websites incorrectly reject addresses containing a "+" character. This
substantially limits the usefulness of address extensions. I've
reported this to Google, but even early in the Gmail beta, this kind
of thing is hard to change once people start depending on a particular
separator character.

This is probably why TMDA systems use "-" by default.

 -Tom

On Jul 14, 2:43 pm, tmetro wrote:

http://gmailblog.blogspot.com/2008/03/2-hidden-ways-to-get-more-from-...

also: http://mail.google.com/support/bin/answer.py?hl=en&answer=12096