From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: acidentally used total-expire
Date: Thu, 14 Aug 2003 23:32:12 +0200 [thread overview]
Message-ID: <84ptj8ylgj.fsf@slowfox.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <usmo85yex.fsf@hschmi22.userfqdn.rz-online.de>
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> (BTW: WIBNIG did at least warn, when it doesn't find a matching rule
> for incoming mails?)
Fancy splitting has the `bogus' safety net. But I'm afraid regular
splitting doesn't.
I hereby propose to add a safety net to regular splitting.
--
Two cafe au lait please, but without milk.
prev parent reply other threads:[~2003-08-14 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wudogxe9.fsf@lux99.home>
[not found] ` <u7k5offc1.fsf@hschmi22.userfqdn.rz-online.de>
[not found] ` <87bruwip3t.fsf@lux99.home>
2003-08-11 9:36 ` Frank Schmitt
2003-08-11 11:59 ` Raymond Scholz
2003-08-14 21:32 ` Kai Großjohann [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=84ptj8ylgj.fsf@slowfox.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).