From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: overseers@sourceware.org
Subject: [Bugzilla-generated e-mails lack Message-ID header]
Date: Sun, 22 Apr 2012 19:35:00 -0000 [thread overview]
Message-ID: <20120422193516.GA24872@ednor.casa.cgf.cx> (raw)
#427 in the "Although everyone else clearly uses your system without
issue, I can't use it, so please change your system for me" series.
cgf
----- Forwarded message from "Mikhail T." -----
From: "Mikhail T." <mi+thun <at> aldan <dot> algebra <dot> com>
To: postmaster, sourceware-bugzilla
Subject: Bugzilla-generated e-mails lack Message-ID header
Date: Sun, 22 Apr 2012 15:27:47 -0400
Comment: DKIM? See http://www.dkim.org
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
Hello!
I just signed up for an account in Sourceware's Bugzilla. The server
sent me the confirmation e-mail, however, because the message did not
contain Message-ID, my server took it for spam and rejected. The other
problem is that server1.sourceware.org claims to be sourceware.org
(perhaps, the latter should simply be a CNAME for the former, instead
of having a separate A-record with the same IP-address in it?)
All in all, the combination of warnings below may be making your
e-mails undeliverable even to servers less paranoid than mine:
Apr 22 15:06:30 narawntapu sm-mta[2642]: q3MJ6TtA002642:
Authentication-Warning: narawntapu.narawntapu: Host
server1.sourceware.org [209.132.180.131] claimed to be
sourceware.org
Apr 22 15:06:31 narawntapu sm-mta[2642]: q3MJ6TtA002642:
ruleset=check_eoh, arg1=18, arg2=1706, relay=server1.sourceware.org
[209.132.180.131], reject=553 5.0.0 Header Error(spammers often skip
Message-ID)
Please, look into it. Thank you. Yours,
-mi
----- End forwarded message -----
reply other threads:[~2012-04-22 19:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120422193516.GA24872@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=overseers@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).