GoDaddy + Gmail = problem!
AudioWaves
is REJECTED by GoDaddy...
So, users can't setup forwarding!
Gmail side:
Many Gmail users know that they can create an email "alias" by using
the plus sign (+) in gmail addresses, for example: "XXX+YYY @gmail.com"
goes to the inbox XXX with YYY as a "tag" on it. It's a way to have
various Gmail pseudo-addresses in one inbox... for using filters and
labels, etc... or to track the usage of any GMAIL address that's given
out... anti-spam... or help find out where the leaks are... a very
useful Gmail innovation!
GoDaddy side:
GoDaddy allows webmasters to redirect email, but GoDaddy is not
Gmail-friendly, since GoDaddy will NOT permit the + (plus) character in
an email address.
>From GoDaddy's Account Manager control panel:
On the Hosting & Email menu, click Email Accounts ...
Manage Email Forwarding ...
Setup Account ...
Redirect Mail To ... xxx+yyy @ gmail.com (no spaces)
Save ...
Result: ERROR message from GoDaddy:
... Please correct the following errors:
... At least one Redirect Mail To does not appear to be valid ...
*** If you use GoDaddy email forwarding, and Gmail, please report this
to GoDaddy, so we can get proper attention on this... I reported it
seven months ago, and it is still "PENDING"... ***
GoDaddy [Incident ID 1003407] of (3 Sep 06) and
GoDaddy [Incident:060205-000827] of (5 Feb 06)
still "Pending, escalation..."
===
Here's more Gmail info:
http://gmail.google.com/support/bin/answer.py?answer=12096&topic=1564
GMAIL Help Center Home > Reading & Receiving Mail
Can I receive messages at a different Gmail address?
Gmail doesn't offer traditional aliases, but you can receive messages
sent to your.userna...@gmail.com. For example, messages sent
to jane.do...@gmail.com are delivered to jane...@gmail.com.
You can set up filters to automatically direct these messages to Trash,
apply a label or star, skip the inbox, or forward to another email
account.
===
Also, GoDaddy, PLEASE NOTE:
Valid characters in an email address include:
_ underscore
- hyphen or dash
. dot or period
+ plus sign
among others...
see http://www.faqs.org/rfcs/rfc2822.html (RFC 2822; 3.2.4. Atom.) for
a FULL list! Let's follow the RFC, dudes!
===
I've sent several emails and spoken on the phone to several support
agents in the past seven months about this serious problem. Except for
GoDaddy's lack of attention to this matter, I am satisfied with my
GoDaddy accounts and domain management.
The bottom line:
The plus sign (+) should be allowed by GoDaddy, but it isn't. "It only
needs a few lines of code..."
This will need to be fixed by the GoDaddy support team. Let's see how
we can get some attention from GoDaddy, to fix this soon? Thanks!
HughesOnTheNet
I know I've used the '+YYY' in several situations. Sometimes the site
I'm providing it to will swallow it, and in some cases, I've received
the message that there's an invalid character in the address.
AARGH!
Zack (Doc)
themselves), it's a failure of web programmers in several places to
accept the + as a valid e-mail character.
GeoFan49.lit
http://www.faqs.org/rfcs/rfc2822.html
See 3.2.4. Atom, defines acceptable characters for an email address.
The dot-atom definition allows these:
"!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "/" / "=" / "?" /
"^" / "_" / "`" / "{" / "|" / "}" / "~"
1. Some email providers will not allow users to register a name
containing some of these, which are deemed acceptable in the RFC
standard.
2. Even if an email address can be registered, draconian application
programs and web pages often filter these out... allowing only a-z,
A-Z, 0-9, "-", "_" and "." in email addresses.
3. The text input edit should allow what the RFC defines. (See RFC
2822, See 3.2.4. Atom)
AudioWavesPlus
BCC: via GoDaddy then into GMAIL.
Zack (Doc)
"to" address it was going to. If you want to filter BCC'd messages,
search on the part of the TO, or FROM that doesn't change.
On 9/30/06, AudioWavesPlus <audiowa...@gmail.com> wrote:
>
> Filters for Labels and forwarding DO NOT work if the email goes to a
> BCC: via GoDaddy then into GMAIL.
>
>
> >
>
--
Yours in Scouting,
Zack Tennant
Assistant Cubmaster, Pack 319
http://www.packsonline.com/fl/319/
AudioWavesPlus
We need to use multiple addresses with GoDaddy's email forwarding
service, to forward to GMAIL, for collection and then forwarding to
other addresses.
GoDaddy forwarding won't use the GMAIL + (plus) symbol, so the all have
to go into one address in GMAIL.
GeoFan49.lit
AudioWavesPlus
For example, (the actual emails have been changed, to prevent
spamming...
Here's what happens when there is a BCC: USER-ONE @ MyDomain1.com
((( WE cannot control the BCC, that is the SENDER's choice. )))
The USER-ONE @ MyDomain1.com gets forwarded by GoDaddy to MyDomain1 @
GMAIL.com
That's good, but the GMAIL filter does NOT see the BCC:
"... BCC: USER-ONE @ MyDomain1.com ..."
even though, USER-ONE @ MyDomain1.com is found in the email headers:
X-Gmail-Received: 45a51be6c3afd574dc5e29d3a221e752486e0b33
Delivered-To: MyDomain1 @ gmail.com
Received: by 10.82.130.14 with SMTP id c14cs172583bud;
Wed, 25 Oct 2006 12:06:35 -0700 (PDT)
Received: by 10.78.200.3 with SMTP id x3mr295390huf;
Wed, 25 Oct 2006 12:06:35 -0700 (PDT)
Return-Path: in...@dbdragracing.com
Received: from smtp04-02.prod.mesa1.secureserver.net
(smtp04-02.prod.mesa1.secureserver.net [64.202.189.10])
by mx.google.com with ESMTP id
y18si856123hua.2006.10.25.12.06.34;
Wed, 25 Oct 2006 12:06:35 -0700 (PDT)
Received-SPF: softfail (google.com: domain of transitioning
in...@dbdragracing.com does not designate 64.202.189.10 as permitted
sender)
Received: (qmail 23891 invoked by uid 1000); 25 Oct 2006 19:06:33 -0000
Delivered-To: USER-ONE @ MyDomain1.com
Precedence: bulk
Received: (qmail 23884 invoked from network); 25 Oct 2006 19:06:33
-0000
Received: from pre-smtp20-02.prod.mesa1.secureserver.net
([64.202.166.35])
(envelope-sender <in...@dbdragracing.com>)
by smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <USER-ONE @ MyDomain1.com>; 25 Oct 2006 19:06:33 -0000
Received: (qmail 8319 invoked from network); 25 Oct 2006 19:06:33 -0000
Received: from unknown (HELO termpro.com) ([12.174.189.130])
(envelope-sender <in...@dbdragracing.com>)
by pre-smtp20-02.prod.mesa1.secureserver.net
(qmail-ldap-1.03) with SMTP
for <USER-ONE @ MyDomain1.com>; 25 Oct 2006 19:06:31 -0000
Result, tags and rules from GMAIL filters for USER-ONE never get
processed...
Although, the GMAIL filters work OK for TO: and for CC: USER-ONE
the BCC: USER-ONE does not trigger the GMAIL filter rules.
So, we are caught between GoDaddy and Gmail..
A workaround would be to have GoDaddy send USER-ONE @ MyDomain1.com to
MyDomain1+USER-ONE @ GMAIL.com
That does NOT work because GoDaddy forwarding will not allow the GMAIL
+ (plus) in an email address.
POTENTIAL SOLUTION #1:
Can Gmail fix the filters so they process the BCC info, it's there in
the headers!
We are using ONE GMAIL account to tag and forward emails via GMAIL
filters.
We send all the domain mail to GMAIL via GoDaddy forwarding.
It all works fine, except for the email to BCC case.
POTENTIAL SOLUTION #2:
Can GoDaddy allow the GMAIL + (plus) email address convention?
On Sep 30, 9:37 pm, "Zack (Doc)" <z...@tnan.net> wrote:
> Filters will never work for BCC, there is no reliable way to tell what
> "to" address it was going to. If you want to filter BCC'd messages,
> search on the part of the TO, or FROM that doesn't change.
>
AudioWavesPlus
SO, it would be a reasonable expectation for GMAIL to process it via
FILTERS.
...
POTENTIAL SOLUTION #1:
POTENTIAL SOLUTION #2:
> Filters will never work for BCC, there is no reliable way to tell what
> "to" address it was going to. If you want to filter BCC'd messages,
> search on the part of the TO, or FROM that doesn't change.
>
Fuzzy Logic
From? Nope, that doesn't make sense.
To? No, it's in neither To nor Cc, as described in the helps.
So, no, not a reasonable expectation.
Fuzzy
AudioWavesPlus
Delivered-To: USER-ONE @ MyDomain1.com
That would solve the problem.
Bill Holmes
perhaps that would solve the problem.
I have a domain mail account for my domain gmusers.com and it works just fine.
Bill
--
GMail FAQ:
http://4or.us/gmailfaq.html