From: Dennis Heuer <dh@triple-media.com>
To: linux-c-programming@vger.kernel.org
Subject: strange message received after posting to here
Date: Mon, 15 Oct 2007 20:05:48 +0200 [thread overview]
Message-ID: <20071015200548.a26892be.dh@triple-media.com> (raw)
to my last message (which has no bcc or whatever untypical in the
header) i received the following answer. do you know about them?
Return-path: <root@ctf.com.br>
Envelope-to: dh@triple-media.com
Delivery-date: Mon, 15 Oct 2007 17:47:53 +0200
Received: from mail.ctf.com.br ([201.63.119.87] helo=ctf.com.br)
by srvh02.vc-server.de with esmtps (TLSv1:AES256-SHA:256)
(Exim 4.68)
(envelope-from <root@ctf.com.br>)
id 1IhSAa-0005nj-Gq
for dh@triple-media.com; Mon, 15 Oct 2007 17:47:53 +0200
BrmaOutput: root@localhost
Received: (from root@localhost)
by ctf.com.br (8.12.11.20060308/8.12.11) id l9FGsYGl022991;
Mon, 15 Oct 2007 14:54:34 -0200
Date: Mon, 15 Oct 2007 14:54:34 -0200
Message-Id: <200710151654.l9FGsYGl022991@ctf.com.br>
From: postmaster@ctf.com.br
To: dennis heuer <dh@triple-media.com>
Subject: (BRMA) Mensagem n_o autorizada
Mensagem n_o autorizada
----------------------------------------
Palavra (FF) proibida no campo Subject
----------------------------------------
Para: linux-c-programming@vger.kernel.org
Assunto: Re: how to best map/buffer a file to memory by being able to
lock
next reply other threads:[~2007-10-15 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:05 Dennis Heuer [this message]
2007-10-15 20:17 ` strange message received after posting to here Steve Graegert
2007-10-16 11:08 ` Glynn Clements
2007-10-16 17:34 ` Dennis Heuer
2007-10-16 18:56 ` Glynn Clements
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=20071015200548.a26892be.dh@triple-media.com \
--to=dh@triple-media.com \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).