mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julien Oster <usenet-20040502@usenet.frodoid.org>
To: "David S. Miller" <davem@redhat.com>
Cc: jmerkey@comcast.net, root@chaos.analogic.com,
	linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: kallsyms 2.6.8 address ordering
Date: Fri, 20 Aug 2004 00:07:00 +0200	[thread overview]
Message-ID: <87llgaok8r.fsf@killer.ninja.frodoid.org> (raw)
In-Reply-To: <20040819124211.2e4d57e4.davem@redhat.com> (David S. Miller's message of "Thu, 19 Aug 2004 12:42:11 -0700")

"David S. Miller" <davem@redhat.com> writes:

Hello David,

>> jmerkey@drdos.com is blocked from posting to this list.  I have
>> verified it though smtp, so I use my comcast.net account instead.
>> David Miller **WONT** respond to emails or the other list
>> maintainers.

> Well, you're not in the by-hand SPAM filter, so it must be something else.

> ? egrep drdos /opt/mail/db/smtp-policy.spam.manual
> ? egrep jmerkey /opt/mail/db/smtp-policy.spam.manual

> What message do you get back from direct smtp tests?

My messages also won't get through if I send them directly using
postfix from my workstation (with dynamic IP). I switched to using a
smarthost and now everything seems ok.

I thought it might be spam prevention. However, the SMTP server lkml
is attached to accepted the messages perfectly and just dropped it
silentily. It really should give an error when it's preventing spam,
otherwise you might not even notice that your message got dropped.

At least one message really didn't get anywhere while the SMTP server
said that everything is fine. Or maybe it's a bug somewhere that drops
messages unintendedly? Drop me a line if you need the log entry.

However, I never suspected that I was dropped on purpose, and I still
don't think so right now.

Regards,
Julien

  reply	other threads:[~2004-08-19 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 19:27 jmerkey
2004-08-19 19:42 ` David S. Miller
2004-08-19 22:07   ` Julien Oster [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19 22:43 jmerkey
2004-08-20  1:23 ` Horst von Brand
2004-08-19 22:40 jmerkey
2004-08-19 23:11 ` Francois Romieu
2004-08-19 19:24 jmerkey
2004-08-19 19:22 jmerkey
2004-08-19 19:14 jmerkey
2004-08-19 18:26 jmerkey
2004-08-19 18:33 ` Christoph Hellwig
2004-08-19 18:10 jmerkey
2004-08-19 18:19 ` Christoph Hellwig
2004-08-19 18:30 ` Rik van Riel
2004-08-19 18:40 ` Richard B. Johnson
2004-08-19 19:00 ` Robin Holt
2004-08-20 11:42   ` Paulo Marques
2004-08-19 20:10 ` Horst von Brand

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=87llgaok8r.fsf@killer.ninja.frodoid.org \
    --to=usenet-20040502@usenet.frodoid.org \
    --cc=davem@redhat.com \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    /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

Powered by JetHome