Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2. - Mozilla

This is a discussion on Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2. - Mozilla ; Our bugmail message bodies are all blank (message headers like Subject, To and From are intact though) after upgrading to Bugzilla 3.4.2 (CVS) from 3.2 last Friday, 16 Oct 2009. I don't see any useful errors about this in my ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

  1. Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    Our bugmail message bodies are all blank (message headers like
    Subject, To and From are intact though) after upgrading to Bugzilla
    3.4.2 (CVS) from 3.2 last Friday, 16 Oct 2009.

    I don't see any useful errors about this in my Apache2 error log.

    I thought it was perhaps a perl module @INC array path problem so I
    ran

    install-module.pl --upgrade-all --global

    with no obvious error messages displayed afterward. But that didn't
    fix my bugmail problem -- new bugmail messages are still blank.

    checksetup.pl doesn't log a single complaint about perl modules.

    I can provide example blank bugmail messages offline for anyone who
    needs details.

    Any ideas? Thanks for any help. I'm stumped at the moment.

  2. Re: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    Not the same problem. I'm not just missing comments.

    /eiren

    On Oct 20, 10:33*am, "Brandon" wrote:
    > I am having this same problem after upgrading from 3.2.1 to 3.4.2. *I have
    > all the required Perl modules and verified that the email template file is
    > intact.
    >
    > Emails contain the bug link and the link to configure bugmail *but no
    > comments.....
    >
    > Please help!!
    >
    > Running on RHEL5.3
    >
    > -Brandon
    >

    ....

  3. Re: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    On Oct 20, 3:08*pm, Frédéric Buclin wrote:
    > As said on IRC, this is because you have files in template/en/custom/,
    > and those are not upgraded by CVS (because they are custom files, not
    > official ones). As format_comments.txt.tmpl (which is the template which
    > formats and paste comments in e.g. emails) is new in Bugzilla 3.4, you
    > old email template has no reference pointing to it and so you get no
    > comments anymore.
    >
    > So either delete custom/ or update (manually) templates which are there.
    >
    > LpSolit


    Thanks, Frederic, but I'm not just missing comments. I've seen some
    other discussion about that problem. I wish that was my problem as I'd
    be working again already.

  4. Re: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    Here's an example of a message I received that Mail.app renders with a
    blank body:

    Delivered-To: eirensaxiom@gmail.com
    Received: by 10.216.89.199 with SMTP id c49cs145164wef;
    Tue, 20 Oct 2009 16:37:53 -0700 (PDT)
    Received: by 10.90.174.7 with SMTP id w7mr7618721age.11.1256081873290;
    Tue, 20 Oct 2009 16:37:53 -0700 (PDT)
    Return-Path:
    Received: from static-24.96.69.252.knology.net ([24.96.69.252])
    by mx.google.com with ESMTP id 29si6877135yxe.
    73.2009.10.20.16.37.52;
    Tue, 20 Oct 2009 16:37:53 -0700 (PDT)
    Received-SPF: neutral (google.com: 24.96.69.252 is neither permitted
    nor denied by best guess record for domain of bugzilla-
    daemon@axiomint.com) client-ip=24.96.69.252;
    Authentication-Results: mx.google.com; spf=neutral (google.com:
    24.96.69.252 is neither permitted nor denied by best guess record for
    domain of bugzilla-daemon@axiomint.com) smtp.mail=bugzilla-
    daemon@axiomint.com
    Message-Id: <4ade49d1.1d02be0a.26b6.1d35SMTPIN_ADDED@mx.google. com>
    Return-path:
    Received: from _HOSTNAME_ by axiomint.com
    (MDaemon.PRO.v8.1.6.R)
    with ESMTP id md50003166123.msg
    for ; Tue, 20 Oct 2009 19:37:44 -0400
    Received: by _HOSTNAME_ (sSMTP sendmail emulation); Tue, 20 Oct 2009
    19:16:47 -0500
    Date: Tue, 20 Oct 2009 19:16:47 -0500
    From: bugzilla-daemon@axiomint.com
    To: eirens@axiomint.com
    Subject: [Bug 6] This bug is just for teaching and such.
    X-Bugzilla-Reason: Reporter
    X-Bugzilla-Type: changed
    X-Bugzilla-Watch-Reason: None
    X-Bugzilla-Classification: Development Process
    X-Bugzilla-Product: TestProduct
    X-Bugzilla-Component: TestComponent
    X-Bugzilla-Keywords: Documentation, sticky
    X-Bugzilla-Severity: major
    X-Bugzilla-Who: eirens@axiomint.com
    X-Bugzilla-Status: REOPENED
    X-Bugzilla-Priority: --
    X-Bugzilla-Assigned-To: fredk@axiomint.com
    X-Bugzilla-Target-Milestone: ---
    X-Bugzilla-Changed-Fields:
    In-Reply-To:
    References:
    X-Bugzilla-URL: http://bugs.axiom-direct.com/
    Auto-Submitted: auto-generated
    Content-Type: text/plain; charset="UTF-8"
    MIME-Version: 1.0
    X-MD-Bad-Header:
    http: //bugs.axiom-direct.com/show_bug.cgi?id=6
    X-MD-Bad-Header:
    --- Comment #94 from Eiren (PM) 2009-10-20 19:
    16:47 EST ---
    X-MD-Bad-Header: Test.
    X-MD-Bad-Header:
    X-MD-Bad-Header: --
    Configure bugmail: http://bugs.axiom-direct.com/userprefs.cgi?tab=email
    ------- You are receiving this mail because: -------
    X-Spam-Processed: static-24.96.69.252.knology.net, Tue, 20 Oct 2009
    19:37:44 -0400
    (not processed: spam filter disabled)
    X-MDRcpt-To: eirens@axiomint.com
    X-Rcpt-To: eirens@axiomint.com
    X-Return-Path: bugzilla-daemon@axiomint.com
    X-MDRedirect: 1
    X-MDaemon-Deliver-To: eirensaxiom@gmail.com


  5. Re: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    On Oct 21, 8:13*pm, Max Kanat-Alexander wrote:
    > On 10/20/2009 04:39 PM, EirenS wrote:
    >
    > > MIME-Version: 1.0
    > > X-MD-Bad-Header:
    > > http: //bugs.axiom-direct.com/show_bug.cgi?id=6

    >
    > * * * * Have you edited your templates or BugMail.pm? It looks like there's an
    > entirely missing newline before the body of the email, which would cause
    > this problem.
    >
    > * * * * -Max
    > --http://www.everythingsolved.com/
    > Competent, Friendly Bugzilla and Perl Services. Everything Else, too.


    Nope, I haven't edited either. There's a blank line there that's been
    flagged with a "X-MD-Bad-header: " prefix. I've confirmed that the
    empty newline is there in the email Bugzilla sends out by looking at
    the email output the smtp_debug puts in my Apache error log.

    /eiren

  6. Re: Blank bugmail messages after upgrade from Bugzilla 3.2 to 3.4.2.

    On Oct 23, 10:19*am, EirenS wrote:
    > On Oct 21, 8:13*pm, Max Kanat-Alexander wrote:
    >
    > > On 10/20/2009 04:39 PM, EirenS wrote:

    >
    > > > MIME-Version: 1.0
    > > > X-MD-Bad-Header:
    > > > http: //bugs.axiom-direct.com/show_bug.cgi?id=6

    >
    > > * * * * Have you edited your templates or BugMail.pm? It looks like there's an
    > > entirely missing newline before the body of the email, which would cause
    > > this problem.

    >
    > > * * * * -Max
    > > --http://www.everythingsolved.com/
    > > Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

    >
    > Nope, I haven't edited either. There's a blank line there that's been
    > flagged with a "X-MD-Bad-header: " prefix. I've confirmed that the
    > empty newline is there in the email Bugzilla sends out by looking at
    > the email output the smtp_debug puts in my Apache error log.
    >
    > /eiren


    Clarification: I assume that "X-MD-Bad-Header: " header is added by my
    company's MDaemon 8.1.6 installation. However, I can't figure out why
    Bz 3.2 wouldn't cause MDaemon to do that but 3.4.2 does. (And MDaemon
    8.1.6 doesn't have an option to not add that header -- but MDaemon
    version 10 does.)

    I'm using sSMTP as a sendmail substitute, in case that helps. Bugzilla
    server is Gentoo Linux.

    Also note that I added three more newlines between the header and the
    body in newchangedmail.txt.tmpl and the result was an additional "X-MD-
    Bad-Header: " prefix for each newline I added to the template.

+ Reply to Thread