From: George Georgalis <georgw@galis.org>
To: netfilter@lists.samba.org
Subject: doh! lost mail...
Date: Wed, 10 Jul 2002 14:08:14 -0400 [thread overview]
Message-ID: <20020710140814.A27614@trot> (raw)
Well I blew it, never ran into a problem like this before so thought I'd
share. I have lost mail. BTW - Thanks Lauren for all your help, support
and escalations on my shell account at http://he.net ...and I thought
it was your server that was stuck!
(If you run Linux/Unix) The scenario I suspect is not so uncommon. Here's
part of my procmailrc.
:0 Whc: msgid.lock
| formail -D 8192 msgid.cache
:0 a:
/dev/null
:0 Wc
| razor-check
:0 Wa
razor-caught/
In a nutshell, if the razor-check program hangs or is slow to respond,
fetchmail times out. When it runs again the message is flagged as a
duplicate per the first recipe and sent to /dev/null
So if you were wondering what happened the the message I never responded
to... I've been doing this in the background for years. :) Don't know
how long or frequently the razor-check has been overloaded. But seems
often in recent times.
// George
--
GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229
Security Services, Web, Mail, mailto:george@galis.org
File, Print, DB and DNS Servers. http://www.galis.org/george
reply other threads:[~2002-07-10 18:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020710140814.A27614@trot \
--to=georgw@galis.org \
--cc=netfilter@lists.samba.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