public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: <overseers@gcc.gnu.org>, Joel Sherrill <joel.sherrill@oarcorp.com>
Subject: Re: posting to gcc-testresults  help
Date: Tue, 12 Feb 2008 23:31:00 -0000	[thread overview]
Message-ID: <47B22634.9080808@oarcorp.com> (raw)
In-Reply-To: <20080212221901.GB11308@ednor.casa.cgf.cx>

Christopher Faylor wrote:
> On Tue, Feb 12, 2008 at 02:02:22PM -0600, Joel Sherrill wrote:
>   
>> Hi,
>>
>> I am sure the problem is on my side but I am baffled.   I can send
>> to my gmail.com account so things aren't completely FUBAR'ed. :-D
>>
>> I am trying to send to gcc-testresults using the script which
>> invokes Mail.  When I send a full test log or this short test
>> message
>>
>> echo "Testing email" | Mail -s "Test" gcc-testresults@gcc.gnu.org
>>
>> I see this in  /var/log/maillog
>>
>> Feb 12 13:55:35 iceland sendmail[16972]: m1CJtZKe016972:
>> to=gcc-testresults@gcc.gnu.org, ctladdr=joel (510/100), delay=00:00:00,
>> xdelay=00:00:00, mailer=relay, pri=30061, relay=[127.0.0.1] [127.0.0.1],
>> dsn=2.0.0, stat=Sent (m1CJtZw5016973 Message accepted for delivery)
>> Feb 12 13:56:08 iceland sendmail[16975]: m1CJtZw5016973:
>> to=<gcc-testresults@gcc.gnu.org>, ctladdr=<joel@localhost.localdomain>
>> (510/100), delay=00:00:33, xdelay=00:00:33, mailer=esmtp, pri=120407,
>> relay=gcc.gnu.org. [209.132.176.174], dsn=2.0.0, stat=Sent (Queued!
>> 1202846168 qp 29757 <200802121955.m1CJtZKe016972@localhost.localdomain>)
>>
>> I am a DHCP'ed laptop running Fedora 8.  Can you see
>> what is wrong with my setup from your side?
>>     
>
> Your email is being represented as being from "joel@localhost.localdomain" and
> is triggering these spamassassin rules: BOTNET,HELO_LH_LD,NO_DNS_FOR_FROM.
>   
Ok.  I think I have fixed that so the email comes out now
as "joel@iceland.oarcorp.com".  I am Fedora 8 and it looks
like the Mail/mail program does not honor the REPLYTO
environment variable.  I don't see anything on .mailrc
that would help either.

Any ideas?
> You'll have to fix your From address so that it reflects a real email address
> and then subscribe that email address to global-allow as per:
>
>   
joel@iceland.oarcorp.com isn't a valid email address.  I could change
that but would prefer to find a way to make the Reply-To use a valid
email address. <sigh>
> http://sourceware.org/lists.html#spam
>
> Although if you had a real DNS and host name that might be enough to fix the
> problem.
>   
Given that I won't ever run this on a machine directly on the Internet,
I doubt that's really an option.

Thank you. I know you must get tired of the same ignorant questions.

--joel
> cgf
>   


-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel.sherrill@OARcorp.com        On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985


  reply	other threads:[~2008-02-12 23:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 21:06 Joel Sherrill
2008-02-12 23:05 ` Christopher Faylor
2008-02-12 23:31   ` Joel Sherrill [this message]
2008-02-12 23:55     ` Hans-Peter Nilsson
2008-02-13  7:44       ` Joel Sherrill
2008-02-13 17:24       ` Joel Sherrill

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=47B22634.9080808@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=overseers@gcc.gnu.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).