From: "matt" <matt@proweb.co.uk>
To: "Fco. J. Ballesteros" <nemo@plan9.escet.urjc.es>
Cc: <9fans@cse.psu.edu>
Subject: [9fans] Re: mailcollector
Date: Tue, 23 Jul 2002 12:11:11 +0100 [thread overview]
Message-ID: <009201c23239$a8591410$6501a8c0@KIKE> (raw)
In-Reply-To: <e3591ed4b26580667a9616e5cfa9e344@plan9.escet.urjc.es>
----- Original Message -----
From: "Fco. J. Ballesteros" <nemo@plan9.escet.urjc.es>
To: <matt@proweb.co.uk>
Sent: Tuesday, July 23, 2002 11:45 AM
Subject: Re: mailcollector
> Thanks
>
> There's one thing I saw just looking at the source (didn't try it yet)
> IMHO, if the local upas/send fails, the script would delete the mail
> from the remote folder. This looks dangerous. Is this right?
yes
I suppose checking $status after cat $msg/raw | upas/send -r -b $user
is called for
that is why I added the -k option actually
Problem with that though is that the same messages are retrieved next time
I suppose grep /mail/fs/mbox/*/Message-ID `{cat /mail/fs/$key(3)} would fix
that but strikes me as a bit expensive
parent reply other threads:[~2002-07-23 11:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <e3591ed4b26580667a9616e5cfa9e344@plan9.escet.urjc.es>]
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='009201c23239$a8591410$6501a8c0@KIKE' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
--cc=nemo@plan9.escet.urjc.es \
/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).