Issue #3480 resolved

support@bitbucket.org email does not work

Jeff Sherk
created an issue

The support@bitbucket.org email address listed on the following page does not work. It says "Message rejected by Google Groups" https://bitbucket.org/support

Comments (5)

  1. Tatto de Castro
    • changed status to open

    I am receiving the same error during this week.

    Follows the message with headers..

    Delivered-To: tattodecastro@gmail.com
    Received: by 10.223.155.70 with SMTP id r6csp7237faw;
            Wed, 29 Feb 2012 11:53:41 -0800 (PST)
    Received: from mr.google.com ([10.216.136.152])
            by 10.216.136.152 with SMTP id w24mr887326wei.50.1330545221479 (num_hops = 1);
            Wed, 29 Feb 2012 11:53:41 -0800 (PST)
    Received: from mr.google.com ([10.216.136.152])
            by 10.216.136.152 with SMTP id w24mr713575wei.50.1330545220717 (num_hops = 1);
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Received: by 10.216.136.152 with SMTP id w24mr713575wei.50.1330545220716;
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    MIME-Version: 1.0
    Return-Path: <>
    Received: by 10.216.136.152 with SMTP id w24mr887319wei.50; Wed, 29 Feb 2012
     11:53:40 -0800 (PST)
    From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
    To: tattodecastro@gmail.com
    X-Failed-Recipients: support@bitbucket.org
    Subject: Delivery Status Notification (Failure)
    Message-ID: <00504502d1b03d06b304ba1fb342@google.com>
    Date: Wed, 29 Feb 2012 19:53:40 +0000
    Content-Type: text/plain; charset=ISO-8859-1
    
    Delivery to the following recipient failed permanently:
    
         support@bitbucket.org
    
    Technical details of permanent failure: 
    Message rejected by Google Groups. Please visit http://mail.google.com/support/bin/answer.py?hl=en&answer=188131 to review our Bulk Email Senders Guidelines.
    
    ----- Original message -----
    
    Received: by 10.216.136.152 with SMTP id w24mr713568wei.50.1330545220343;
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Received: by 10.216.136.152 with SMTP id w24mr713565wei.50.1330545220321;
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Return-Path: <tattodecastro@gmail.com>
    Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182])
            by mx.google.com with ESMTPS id l67si11421304weq.38.2012.02.29.11.53.40
            (version=TLSv1/SSLv3 cipher=OTHER);
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Received-SPF: pass (google.com: domain of tattodecastro@gmail.com designates 74.125.82.182 as permitted sender) client-ip=74.125.82.182;
    Authentication-Results: mx.google.com; spf=pass (google.com: domain of tattodecastro@gmail.com designates 74.125.82.182 as permitted sender) smtp.mail=tattodecastro@gmail.com; dkim=pass header.i=@gmail.com
    Received: by werl4 with SMTP id l4so2897377wer.13
            for <support@bitbucket.org>; Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Return-Path: <tattodecastro@gmail.com>
    Received-SPF: pass (google.com: domain of tattodecastro@gmail.com designates 10.180.99.7 as permitted sender) client-ip=10.180.99.7;
    Received: from mr.google.com ([10.180.99.7])
            by 10.180.99.7 with SMTP id em7mr3873134wib.7.1330545220282 (num_hops = 1);
            Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
            d=gmail.com; s=gamma;
            h=mime-version:date:message-id:subject:from:to:content-type;
            bh=qr9VpxcCpRiUABeLKvNTiYy5spgfwdcPsKQBBLO6/Lc=;
            b=orNeLHoBl8ceD5uW/+qA3IjTzJJJZReiSBZX6BfX+YbJNY2BNCGruHy6Z47jq57Ec4
             oO0twUP5xQngT96eag2RC+UOopah2m6VD3YLMoL5FGkZx/bNuAZAGDnBLU59mfATNcma
             meknEfgLQPvIgz8a2XvlqVSiRAa9BWR4jr/uY=
    MIME-Version: 1.0
    Received: by 10.180.99.7 with SMTP id em7mr3112227wib.7.1330545220240; Wed, 29
     Feb 2012 11:53:40 -0800 (PST)
    Received: by 10.223.155.70 with HTTP; Wed, 29 Feb 2012 11:53:40 -0800 (PST)
    Date: Wed, 29 Feb 2012 16:53:40 -0300
    Message-ID: <CAAG0dUD5RftXpZMSwgG3jJ43ONBCiFxoRkSJgAp+ZWoBt4Ly4Q@mail.gmail.com>
    Subject: Repository corruption on the remote side
    From: Tatto de Castro <tattodecastro@gmail.com>
    To: support@bitbucket.org
    Content-Type: multipart/alternative; boundary=f46d0418280435c58b04ba1fb339
    
     Hi,
    
        First I would like to thank you for the great service you delivery. My
    dev team is finally upgrading to the paid plan, but we are currently having
    a strange error, every git pull or git clone is returning the same message:
    "aborting due a possible repository corruption on the remote side".
    
        Bellow follows a test:
    tatto@tattobook3:~/Desktop/teste$ git clone
    https://bitbucket.org/serverdoin/mercadodetroca.git
    Cloning into mercadodetroca...
    Username:
    Password:
    remote: Counting objects: 2634, done.
    remote: Compressing objects: 100% (1659/1659), done.
    remote: aborting due to possible repository corruption on the remote side.
    fatal: early EOFs:  11% (290/2634), 124.00 KiB | 113 KiB/s
    fatal: index-pack failed
    
    
        The error is always in the same part. We tried a lot of thing but error
    is always happening.
    
        Can you give us a little help?
    
        Thanks in advance,
    
    -- 
    Thiago Augusto Franz de Castro
    +55 48 9122 4073
    +55 48 9911 3170
    +55 48 3039 8636
    http://serverdo.in/
    
  2. Charles McLaughlin

    We talked about this via IRC. We narrowed down the problem to something in the original email triggering Google's spam filter causing the bounce back. There's not much we can do about this since we want to continue using Google Apps to receive mail.

  3. Log in to comment