-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 2 May 1996, Paul O Bartlett wrote:
The problem is with the listservers themselves (well, at least two
of them, so far). If I send a request to the server, it answers back
one way or the other. However, my recipe treats the response as
ordinary mail and sends a receipt, which the listserver treats as
another incoming request, to which it answers with an invalid-request
message, to which my recipe responds, ... . You get the idea. We have
a "ringing mail" situation. Just yesterday I added the listserv@ and
listproc@ conditions, but I still seem to be having the problem.
Check the from address on the mail. I guess it will be from
`listserv-owner' or `listserv-request' (and the same for listproc). The
`@' at the end of your condition prevents matching on these.
I find this very strange, as ^FROM_DEAMON should catch them.
:0hc
* !^Return-Receipt-To
* !^FROM_DAEMON
* !^FROM.*listserv@
* !^FROM.*listproc@
* !^FROM.*MAILER-DAEMON
* !^FROM.*POSTMASTER
* !^X-Loop: $MY_ADDR
* !^Precedence.*junk
| (formail -r -A"Precedence: junk" \
-A"X-Loop: $MY_ADDR"; \
echo "Your mail arrived dated: $DATE"; \
echo "and concerning Subject: $SUBJECT"; \
echo "It will be read as soon as possible: Paul Bartlett <$MY_ADDR>" \
) | $SENDMAIL -oi -t
- --
Guy Geens <guy(_dot_)geens(_at_)elis(_dot_)rug(_dot_)ac(_dot_)be>: Ph.D.
student at ELIS -- TFCG / IMEC
Home Page: http://www.elis.rug.ac.be/ELISgroups/tfcg/staff/gg.html
finger ggeens(_at_)elis(_dot_)rug(_dot_)ac(_dot_)be for PGP public keys (or use
keyserver)
Say KNOW to drugs.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
Comment: pgp fingerprints in message headers
iQBVAwUBMYjVeXwHoCha5QR1AQHDZAH/WxQvsX3u1FGppVfPeLF/5GOzQVX3hDhw
4Ewm15ori2BPyhoj7DkEMGARv3RMstt1k3BHQx6pruZkMIegxgcB8Q==
=qPMO
-----END PGP SIGNATURE-----