From: octoploid <octoploid@yandex.com>
To: Christopher Faylor <overseers@sourceware.org>
Subject: Re: mails from markus@trippesldorf.de don't make it to libc-alpha@sourceware.org
Date: Wed, 01 Feb 2017 17:43:00 -0000 [thread overview]
Message-ID: <177031485971014@web5j.yandex.ru> (raw)
In-Reply-To: <20170201172547.GA4148@ednor.casa.cgf.cx>
01.02.2017, 18:25, "Christopher Faylor" <overseers@sourceware.org>:
> On Wed, Feb 01, 2017 at 05:44:01PM +0100, octoploid wrote:
>> I cannot post messages to libc-alpha@sourceware.org with my
>> markus@trippesldorf.de account anymore.
>> (Posting to gcc-patches@gcc.gnu.org however works fine).
>>
>> All mails are just silently rejected after 24h.
>>
>> Could you please remove my email address from the black list?
>
> You're not in a "blacklist".
>
> If you can send email to gcc-patches you should be able to send email to
> libc-alpha. There are no records in the logs indicating any spam
> bounces for markus@trippesldorf.de (sic). There are records indicating
> successful email sent by markus@trippelsdorf.de .
>
> From: <markus@trippelsdorf.de>
> To: <gcc-patches@gcc.gnu.org>
> System ud10.udmedia.de [194.117.254.50] (EHLO mail.ud10.udmedia.de)
> Pid: 29805, from Wed Feb 1 11:50:03 2017 to Wed Feb 1 11:50:18 2017
> Â Â (connect) earlytalker: pass, not spontaneous
> Â Â (connect) relay: skip, no match
> Â Â (ehlo) helo: pass
> Â Â (mail) badmailfrom: pass (markus@trippelsdorf.de)
> Â Â (rcpt) badrcptto: pass
> Â Â (rcpt) rcpt_ok: pass: gcc.gnu.org in rcpthosts
> Â Â (data_post) headers: pass
> Â Â (data_post) pass, Ham, -2.5 < 10, learn=ham
> Â Â (data_post) virus::clamdscan: pass, clean
> Â Â 221 sourceware.org closing connection. Have a wonderful day.
>
> There is nothing indicating any attempts to send email from
> markus@trippelsdorf.de to libc-alpha in the logs at all. So, it seems
> like any problems are probably on your side.
>
> It looks like "ud10.udmedia.de" is the system that is sending mail and
> there are a lot of these in the logs:
>
> From:
> To:
> System ud10.udmedia.de [194.117.254.50] (EHLO ylmf-pc)
> Pid: 106700, from Tue Jan 31 21:07:31 2017 to Tue Jan 31 21:07:31 2017
> Â Â (connect) earlytalker: fail, remote started talking before we said hello
> Â Â 550 Connecting host started transmitting before SMTP greeting
>
> So, if this is you, something seems to be misconfigured on your end.
>
> Btw, the place to send email problems like this for this site or any
> other site is "postmaster@".
Well, I did send to postmaster@ at first, but from markus@trippesldorf.de,
so the mail didn't reach you...
Yes, ud10.udmedia.de is the mail server I'm using. I will contact my provider.
prev parent reply other threads:[~2017-02-01 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 16:44 octoploid
2017-02-01 17:15 ` octoploid
2017-02-01 17:44 ` Christopher Faylor
2017-02-01 17:48 ` octoploid
[not found] ` <20170201172547.GA4148@ednor.casa.cgf.cx>
2017-02-01 17:43 ` octoploid [this message]
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=177031485971014@web5j.yandex.ru \
--to=octoploid@yandex.com \
--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).