Issue #3415 resolved
Micah Peterson
created an issue

I have problems with confirmation, my email is hosted on gmail. Every time I click on the link received in the confirmation request I get "We were unable to confirm your email address. The validation email may have expired." I have resend confirmation several time and it doesn't help.

micah63 %at% gmail dott com and mpeterson %at% twofowzand dott com (google apps) are not working currently.

Comments (3)

  1. Charles McLaughlin

    Hi Micah,

    I don't see a problem on our end and we haven't changed anything recently. Here are excerpts from our maillog:

    Dec 19 09:01:58 bitbucket10 postfix/smtp[28463]: 0258C1402B6: to=<micah63.... REMOVED>,[]:25, delay=0.53, delays=0/0/0.1/0.42, dsn=2.0.0, status=sent (250 2.0.0 OK 1324306918 h69si9510390yhe.65)

    Dec 19 08:55:29 bitbucket10 postfix/smtp[31705]: 1628A1402B6: to=<mpeterson....REMOVED>,[]:25, delay=30, delays=0/0/0.23/30, dsn=2.0.0, status=sent (250 2.0.0 OK 1324306529 v13si8062750anl.26)

    Dec 19 08:58:15 bitbucket10 postfix/smtp[31146]: B47D51402B6: to=<mpeterson....REMOVED>,[]:25, delay=0.39, delays=0/0/0.19/0.19, dsn=2.0.0, status=sent (250 2.0.0 OK 1324306695 d50si9010360yhh.68)

    Dec 19 08:58:44 bitbucket10 postfix/smtp[22339]: CF4B21402B6: to=<mpeterson....REMOVED>,[]:25, delay=0.29, delays=0/0/0.11/0.18, dsn=2.0.0, status=sent (250 2.0.0 OK 1324306724 o30si9495840yhl.129)

    Dec 19 09:10:13 bitbucket10 postfix/smtp[9700]: 6D240140FF7: to=<mpeterson....REMOVED>,[]:25, delay=0.26, delays=0/0/0.1/0.16, dsn=2.0.0, status=sent (250 2.0.0 OK 1324307413 24si18161351yhs.93)

    Dec 19 12:08:36 bitbucket10 postfix/smtp[6567]: 1827A14131C: to=<mpeterson....REMOVED>,[]:25, delay=0.43, delays=0/0/0.2/0.23, dsn=2.0.0, status=sent (250 2.0.0 OK 1324318116 g31si8474080ani.109)

    Dec 19 12:09:00 bitbucket10 postfix/smtp[6575]: 0E94D14131D: to=<mpeterson....REMOVED>,[]:25, delay=0.28, delays=0/0/0.11/0.17, dsn=2.0.0, status=sent (250 2.0.0 OK 1324318140 n12si3828957anm.125)

    Maybe Google throttled our IPs.



  2. Log in to comment