| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Joe Peterson wrote: |
| 5 |
> I suspect |
| 6 |
> "not" is the way it was set up, since clearly all posts to the new |
| 7 |
> -dev-announce will not be technical, and so they should not be relayed |
| 8 |
> to -dev automatically. Anyone know? |
| 9 |
> |
| 10 |
|
| 11 |
I like the idea of auto-crossposting, but for those who need it here is |
| 12 |
a nice procmail recipe to handle either case: |
| 13 |
|
| 14 |
:0 Wh: msgid.lock |
| 15 |
| formail -D 8192 msgid.cache |
| 16 |
|
| 17 |
:0 a: |
| 18 |
/dev/null |
| 19 |
|
| 20 |
This maintains an 8k cache of message IDs and tosses any message it has |
| 21 |
already seen. Then you can send both -dev and -dev-announce to the same |
| 22 |
folder and get every message once. |
| 23 |
|
| 24 |
If you're like me and have 14 email addresses forwarded to the same box |
| 25 |
the rule is invaluable in general. |
| 26 |
|
| 27 |
Note - I'm not responsible if the code above destroys your system or |
| 28 |
loses mail - understand procmail before you use it... |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 32 |
|
| 33 |
iD8DBQFGnln+G4/rWKZmVWkRAtP9AKCbBVq97mw5LA0CjhaExvn7O8YqGACfY1RQ |
| 34 |
/3awXBPpZfy0LfNVIaOMXuw= |
| 35 |
=8oKZ |
| 36 |
-----END PGP SIGNATURE----- |
Archives