Re: Question about how to run a deny in access_rules.

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA36C5B187A5F89A2071727DD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 10/04/09 00:50, quoth Steven W. Orr:
> On 09/30/09 22:42, quoth Michael Yount:
>> Use a rule in the inform configuration setting, e.g.,
>>  post | fail | inform
>>
>> Michael
>>
>> Steven W. Orr wrote:
>>> I have a few situations in my lists when I want the person to be
>>> automatically
>>> denied, but I would also like to be informed on when it happens.
>>> Currently, I
>>> see no way to do this.
>>>
>>> For example, I currently have a number of these constructs in my
>>> access_rules:
>>>
>>> post
>>> deny, replyfile=3DMultiTo2
>>> $admin_bothlist2 >=3D 2
>>>
>>> The person who sends the message is getting the rejection, but is
>>> there some
>>> way that I as the list owner can get a copy when this happens?
>>>
>>> Thanks.
>>>
>>>  =20
>=20
> Ok. One more followup. I'm getting the inform that I wanted but I'd als=
o like
> to both see the reply contain the content that caused the deny and for =
the
> poster to also see it.
>=20
> Doable?
>=20
>=20


Sorry to be a pain, but this is a piece of functionality that I really ne=
ed.
Is there anything that I can do, or even a trick, a hack, a tweak, anythi=
ng,
that will cause the replyfile to contain the text that was sent? I realll=
y
need to see both the headers and the content. The post | fail| inform got=
 me
halfway there.


--=20
Time flies like the wind. Fruit flies like a banana. Stranger things have=
  .0.
happened but none stranger than this. Does your driver's license say Orga=
n ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all=
- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net


--------------enigA36C5B187A5F89A2071727DD
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkrU5IIACgkQRIVy4fC+NyRvjwCbBFmj+tjV5TCFY8AC+vNxy8TU
33QAn3hl+uHlS20iPT8ikapTeQdFHyyA
=8jC4
-----END PGP SIGNATURE-----

--------------enigA36C5B187A5F89A2071727DD--