From: boyd@sdgm.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] [GWAVA:sheta7nd] Body text filter message notification
Date: Thu, 2 Oct 2003 22:40:45 -0400 [thread overview]
Message-ID: <cbf531fd25e93c6fb4d6330150b71608@sdgm.net> (raw)
In-Reply-To: <binamvnpjtd22>
hmm, this could be some unstable sumbitch, we had better watch our fucking step -- bouncing stuff leading to loops :(
i'm with ron, we wither import /mail or shut 'em down at the smtp level
or do some sort of auth. the import of /mail has a certain elegance
and simplicity about it.
this will require thought ... and maybe a lot of Zep on DVD.
next prev parent reply other threads:[~2003-10-03 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-03 1:23 GWAVA
2003-10-03 2:27 ` boyd
2003-10-03 2:40 ` boyd [this message]
2003-10-03 11:38 ` [9fans] Pegasus 2.0b Kenji Arisawa
2003-10-03 8:53 ` [9fans] [GWAVA:sheta7nd] Body text filter message notification boyd
2003-10-03 8:55 ` boyd
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=cbf531fd25e93c6fb4d6330150b71608@sdgm.net \
--to=boyd@sdgm.net \
--cc=9fans@cse.psu.edu \
/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).