Menu
▾
▴
nymserv-devel — Nymserv Development
You can subscribe to this list here.
| 2002 |
Jan
(13) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
(6) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2004 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Erik A. <er...@aa...> - 2004-06-09 18:41:53
|
Howdy folks, I have made a few changes to the nymserver.pl script, as follows: 1. Instructed folks to email/finger so...@ho... and li...@ho... for the source code and license, respectively. 2. Added error checking to the remail() subroutine to make sure encryption worked correctly. 3. Reformatted some of the whitespace so it would be consistent with the rest of the file. Also, I think I successfully added a doohickey to automagically send email to this list every time a commit happens. We'll see if it works. :) -- ;; Erik Arneson <er...@aa...> GPG Key ID: 2048R/8B4CBC9C ;; ;; <http://www.transformason.org/> <http://erik.arneson.org/> ;; ;; "Civilization is only savagery silver-gilt." - H. Rider Haggard ;; |
|
From: Remailer A. <rem...@pa...> - 2004-01-13 15:17:05
|
Hi all, we have just implemented the amavis-new antivirus on our server, I've seen some messages rejected and it seems a nymserv related problem because I haven't the same error with remailer messages. i.e. I've a lot of messages like this in the nilsimsa directory: Your message could not be delivered to: <pi...@bi...>: 554 5.6.0 Message with invalid header rejected, id=3D03602-02 - Improper use of control character (char 0D hex) in message header 'Subject' ------------=3D_1073982158-3602-1 Content-Type: message/delivery-status Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Description: Delivery error report Reporting-MTA: dns; chernobyl Received-From-MTA: smtp; chernobyl.investici.org ([127.0.0.1]) Arrival-Date: Tue, 13 Jan 2004 09:22:38 +0100 (CET) Final-Recipient: rfc822; pi...@bi... Action: failed Status: 5.6.0 Diagnostic-Code: smtp; 554 5.6.0 Message with invalid header rejected, id=3D03602-02 - Improper use of control character (char 0D hex) in message header 'Subject' Last-Attempt-Date: Tue, 13 Jan 2004 09:22:38 +0100 (CET) ------------=3D_1073982158-3602-1 Content-Type: text/rfc822-headers Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Description: Undelivered-message headers Received: by chernobyl.investici.org (Postfix, from userid 1012) id B86114C00A; Tue, 13 Jan 2004 09:22:38 +0100 (CET) From: uk5...@ny... To: pi...@bi... Subject: -------MKS-RSP------- any hint ?=20 |
|
From: Peter P. <pe...@pa...> - 2003-03-24 18:38:16
|
On Mon, 24 Mar 2003, Remailer Admin wrote:
> P.S.
> I can't use postfix transport because of a local_recipient_maps
> restriction we have.
Whitelisting that for only one domain or making a table with all valid
addresses @nym should not be that hard.
[don't know about the rest]
Peter
--=20
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
|
|
From: Remailer A. <rem...@pa...> - 2003-03-24 18:30:54
|
Hi all!
I'm testing the nym server at @nymph.paranoici.org,
and there's a problem, I don't know if it's a bug=20
or what else.
As reported also on alt.privacy.anon-server
if I send a message from a nym account to a "normal" email address,
I receive a message that contains in the body something
like this:
Message-Id: <200...@as...>
Date: Sun, 16 Mar 2003 21:42:22 +0100 (CET)
Message-Id: <200...@as...>
Date: Sun, 16 Mar 2003 21:42:22 +0100 (CET)
Message-Id and Date headers are repeated 2 times.
I've configured the nym server so that messages to @nymph.paranoici.org
are delivered to the user anon, and then piped to the nymserver script
through procmail.
Messages sent TO a nym address doesn't show this problem.
Is it a known problem ?
Is there something I can do to debug it ?
P.S.
I can't use postfix transport because of a local_recipient_maps
restriction we have.
Anyway documentation on the sourceforge site is wrong, in the master.cf
file
the parameter for the transport is not -d ${recipient} (name@domain)
but -d ${user} (name without domain).
|
|
From: Doc.Cypher <doc...@ny...> - 2003-01-01 20:43:16
|
-----BEGIN PGP SIGNED MESSAGE----- On Tue, 31 Dec 2002, Erik Arneson <er...@aa...> wrote: >Note: I've CC'ed this to nymserv-devel so we can have a record over >there of some good feature ideas. Okay, I've done the same. :) Let me know if the discussion moves there, it's a list I don't follow. >On 31 December 2002, Doc.Cypher <doc...@ny...> wrote: >> This idea does remind me of a discussion I had a while back with one >> of the other nym server operators. What was being talked about then >> was permitting someone with a nym to upload one or two small web >> pages, as well as having their key available in that way. > >This, on the other hand, is much trickier. There are some other >features, like SpamAssassin support, that are more important, I think. >:) Yes, having had a nym account flooded I'd be interested in seeing the filtering and control capabilities upped on the server side. Even just being able to bounce mail containing 2 or 3 html tags would cut out 90% of the spam I get through my nyms. Of course, the flood I got would have been impossible to filter. Each message had been separately encrypted to my key before sending. >> I presume the code hasn't been radically altered from that available at >> so...@ny...? If so, how do you have the following parameters set? <snip - nym config parameters> >> To be honest, I'd be really interested in knowing how all nym servers have >> these set. > >Yes, a 'remailer-conf' reply would be a very good idea as well. I'll >start working on that too. :) Well, I'm not sure how other people would expect it to work, but I'd expect a remailer-conf to return the information on the back-end remailer. A nym server is a rather different animal, if it's going to end up with a few more addresses returning information it might be worth looking at the names of all of them and seeing if you can impose some sort of logic or order. ATM I see the following obvious defaults on Alex's test nymserver... abuse, admin, config, confirm, help, list, nobody, postmaster, remailer-key, root, send, source, used. n.a.n. also has a help-html which is where I got my copy of the nym help web page. IIRC, there's also a few non-english versions of the help page loose on the web. help-de, help-nl, and help-fr might be useful additions, although it is going to bulk up the package size. Doc. - -- The bigger the humbug, the better people will like it. ~ Phineas Taylor Barnum. https://vmsbox.cjb.net -----BEGIN PGP SIGNATURE----- Version: N/A iQEVAwUBPhIhcsriC3SGiziTAQGtrQgAiZ8HEd6O4RleqR87RSR0M8cV/0GJFuOK DOlqOz4yEcF2pF1O3QYWyExn/5l61Qf5H8riad+LYhol/hbEMMwdVmkpxa+o9riw Bi+dyYGlahCWsFQ/iKP6ZheME0lwtzfE6RWd50pELs9dShmttRNcJGEiWFQKU5Lt lW+th2IQ1L2vHId7gMEGPaVoVZOMe45383xur2VZEChG+EtQ4bN+a/S6vjJyKb8O Or7Bg8OsBQ1wqt2PVgz8PBmVe6sH49qA+52wwRxSoUU59pgcbbTgogPsfoyzZeJS wih7DFmWYL8xl56XLHiO+DTKLTqa2QrtnehRYXxOh9EzlGymxkHsIA== =nHXq -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-12-31 17:41:47
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Note: I've CC'ed this to nymserv-devel so we can have a record over there of some good feature ideas. On 31 December 2002, Doc.Cypher <doc...@ny...> wrote: > Why not deny creation of nyms starting key- and return the key (with same > constraint that it must contain <account>@[nymswerver] in an ID block? > > Eg, mail to key-doc_cypher@[nymswerver] returns the key? That seems like a more reasonable format, and should be easy to do. I'll start working on that. > This idea does remind me of a discussion I had a while back with one > of the other nym server operators. What was being talked about then > was permitting someone with a nym to upload one or two small web > pages, as well as having their key available in that way. This, on the other hand, is much trickier. There are some other features, like SpamAssassin support, that are more important, I think. :) > I presume the code hasn't been radically altered from that available at > so...@ny...? If so, how do you have the following parameters set? > > # When things get bad: > my $CONFIRM = 0; # Require confirmation of reply-blocks > my $NOCREATE = 0; # Don't allow creation of new nyms > my $QUOTEREQ = 0; # Quote autoresponder requests > > my $WARNAFTER = 90; > my $DELETEAFTER = 120; > > To be honest, I'd be really interested in knowing how all nym servers have > these set. Yes, a 'remailer-conf' reply would be a very good idea as well. I'll start working on that too. :) - -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iQEVAwUBPhHWxdtvZZqLTLycAQIq2wf+JvihHF9+uCvEsMEoN5qw6tRdZ3aVy5n1 4ymBnSmhXW+EDiPVnuz2YfDx/yHb5BHrow5GoNRoz3U51Acsa9aL+YXCdhCGg6hZ p93gQ45M2sTgP4BMMXfkoAussXntnk/xQ4TTvymseVLWXh+Ocf/IBv5AyMOsGL3g fkRR1RKkaDxLdIH2shACwAz4Aks58Ol0r5ZcNA/NxANrUTLg2GLOandozC+eQMt3 UiFBTRid0hujWKIdV5vIDJ4k+hl/sK3/2iWBMIrcWOZiyPc8n0PZibZae/jmRfKx uS/TNnmOiQBDGVUev7+c0MmiMP+Us0zaLOpSl81N96a3NqfD8Ksn/w== =yVxr -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-12-31 15:50:23
|
Guys, I have committed a few fixes to CVS. First, there's a fix for the broken keyring management, which re-implements the old GnuPG keyring creation. I have been using the GnuPG method on hod.aarg.net for a while now, and it seems to be working very well. Second, I have updated the README file to contain better installation instructions. I would appreciate a second pair of eyes on it to help catch errors and such. Any takers? I also added some Postfix instructions, but I'm really not very familiar with Postfix, so I would like it if somebody else took a look at those, too. Happy New Year! -- ;; Erik Arneson <er...@aa...> SD, Ashland Lodge No. 23 ;; ;; GPG Key ID: 2048R/8B4CBC9C CoTH, Siskiyou Chapter No. 21 ;; ;; <http://erik.arneson.org/> <http://www.aarg.net/mason> ;; |
|
From: Erik A. <er...@aa...> - 2002-07-15 18:32:10
|
Hi guys, One thing that I'm sure we all agree should be included with the nymserv code is a 'help' file of some sort, which will be a template that the nymserv operator can start with. Maybe a few places that say <host name here> or something like that. Does anybody want to volunteer to put something together? Maybe somebody that lives in the southeast US and is unemployed for the summer and has lots of free time? ;) -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; |
|
From: Erik A. <er...@aa...> - 2002-07-13 07:13:28
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Hi everybody, Those of you who pay attention to these announcements will remember that hod.aarg.net is a new Nym server that's been open for testing for a while. Well, the testing hit a snag when we found some oddities in verifying signatures with Crypt::OpenPGP, but the author of that piece of software has kindly stepped up to the plate and fixed all of the bugs we've thrown at him so far. Anyhow, I've upgraded Crypt::OpenPGP to a new version, and I would especially like it if people could test the creation of Nyms and sending of messages with PGP versions 5 and up. Please report any successes, failures, or error messages to me personally at er...@aa.... Thanks to all of the testers so far, the nymserver is getting pretty close to feeling stable. I'm hoping that before long hod.aarg.net will actually be open for real business. :) - -- ;; Erik Arneson <er...@aa...> JD, Ashland Lodge No. 23 ;; ;; GPG Key ID: 2048R/8B4CBC9C RAM, Siskiyou Chapter No. 21 ;; ;; <http://erik.arneson.org/> <http://www.aarg.net/mason> ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 and GnuPG iQEUAwUBPS/Sx9tvZZqLTLycAQNJDQf4nYneEY6SpLzb+Tc2u2RnjOQ01D3BkIWt sITkQUi12LbXwimhzFUSHWd0yEehDTkIjeizDHPKexBdbvf5Guj9B7Vf5b6mP/tT NxwhQxpQBNuJMF+dWby4q6eS6DJsNgf7YWwNAjPIbOLFHxqQwaHhWkYSqGOBA3VS j45RoYhRxgcNu2rJoCrgVOnWy3LXGbUNqHNsBQQgce3VRiNQyO7Xy3m52Dt87oAa cnOHB5Ko7YY7X9hpRg2A/4DLd53jNgjAmpthY/DDOVUlm9jE/G/JymBsRuB2fMmV BlV9oYq/XHZtAhS5Z3+QVpUbDh6uBn/psveCfilf0OT09z/aKvYt =zKGE -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-06-10 21:49:42
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ok, I committed the replay log fix. I'd really appreciate it if some of you guys could look over the change and point out any obvious booboos I made in the code. It looked ok to me. :) It seems to test all right as well. It's out there live on hod.aarg.net if anybody wants to throw some good tests its way. - -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iQEVAwUBPQUe7dtvZZqLTLycAQIF0wgApU3XnV2+tMTQdokLby3C6f3dhJs5ILa6 XKyNwZxEc6hvuEYrdQmg3i6O8v02/H9qNpwnYmg/2qlExd0R0logURjOdwrfhFUG ZWit05Xi79bX1ICAufnkeYr59odQoTGBrRcAi4liX7my5YAWrhqvSyCSkF2LyAWg ugI6R9q9tUZaeDIMiTZzhyAiT7mzvvMYcUROhOnjyKWCBfi7eGX1ArMe5tyl1XyV ZR/s/n3kT8QOPuNy4G315fszx0IIYMczvC5vGpjLvFBprYBV1tM8cF/aBS3ra0MD q2S/Das9X+YQupsVKocyJw6e+wGjg3aVGb/xy+/O8vRuMQEYUZtkAQ== =nuFB -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-06-10 20:41:32
|
Damn, sorry about the giant email and non-armoured signature. -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; |
|
From: Erik A. <er...@aa...> - 2002-06-10 20:28:54
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Until Ben releases the next version of Crypt::OpenPGP, here's a patched version which fixes both the strange PGP 6.5.8 signature bug, and adds the ability to grab signature timestamps. I'll be uploading the nymserv.pl fix which gets the replay log working shortly, but I thought you guys would like to have this first. You can generate a diff against Crypt::OpenPGP 1.00 to see what I've changed. I attached my PGP signature, but I don't have one of Ben's. - -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iQEVAwUBPQULm9tvZZqLTLycAQKc4ggAySDQEYmrJgbinDjPUcNmaAuicvHxRZql kq+9n6Bl2Y3hF2OoSKDdhTUh+us3UI+wFAAJbwLPVQFPacocn7NWlooczqnOu6Fx FBVM+tFNihBWpx6UmyGyJQCEckUQymy3lbCK3ubpyLzq8P/tlLqO+O1EnCv0XAU9 U2+xfk90dZzHiPlRdz6n5yw/bB3eKojaBBs81eTwRdmxMxYorWMFdbPMRClXxIrF Q//6G20hXPijQQvQcJepIHBnX5s90pU+sEp/VUYeUQ5nVFlu5G5//GhZMq2AFRJj NLk3cD3YVoimoUg7b65hkzFCXcqEPGmidGacYpgsOOrJHWXEsp9faQ== =J0ED -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-06-10 14:56:02
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Currently the replay cache isn't working correctly. I'll try to get this patched up today, it looks pretty simple. Once again, it's a case of nymserv indiscriminately spawning external programs, so it will at least give us a chance to implement Digest::MD5. :) - -- ;; Erik Arneson <er...@aa...> JD, Ashland Lodge No. 23 ;; ;; GPG Key ID: 2048R/8B4CBC9C RAM, Siskiyou Chapter No. 21 ;; ;; <http://erik.arneson.org/> <http://www.aarg.net/mason> ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPQS9/9tvZZqLTLycAQLm6ggAlwOlS/gezapKsfqWV9AUDbl7n+xj1GYu YmOGCwow/qxvgnuZSJ1ikh4HyClTyt7nAXSbXvtqvzDGpdUrUzc7ICT24EuPMGOU QICOZQ3cEbkUnn5GGCHKtFR7qu0Wj46MJAfMiuWD8imZp+5wJHcBfy1taaKl8rQq mZOhkKhvXwkzuTuUZ4K0dT5HpP1tlA7FT2salT2OmIMRIG/5/rlRDD4RkTmM2u7t CaVD3rclrtTxBIT8F9zSvKhgAeP8ovhhYCN5/J/yTCVcjqyB6D9SOXIo2oplDOca ugsDbkkMeNfBi37k2udOTJzBmfBs/BpdYIT+8rtq90KUbY8ERlLkRg== =Xzh1 -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-06-10 00:41:20
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, good news. We've got lots of good testing going on right now, lots of reply blocks being confirmed, and we've even got at least one reported test using AAM to receive messages. I just uploaded a fix that makes sure outgoing messages sent to 'send' are clearsigned instead of entirely ASCII-armoured. The only other fix I'd like to get in before releasing a good solid version is to make sure that there aren't any instances of Crypt::OpenPGP dying unexpectedly. Also, I guess when Crypt::OpenPGP fails, it should return a valid error code instead of just dying for the helluvit. But it's coming along! - -- ;; Erik Arneson <er...@aa...> JD, Ashland Lodge No. 23 ;; ;; GPG Key ID: 2048R/8B4CBC9C RAM, Siskiyou Chapter No. 21 ;; ;; <http://erik.arneson.org/> <http://www.aarg.net/mason> ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iQEVAwUBPQP1rdtvZZqLTLycAQLRGQgA4O8UzIyUoPzmKU+mT8pzw/ZW0GdWZrQA D9n3UC55DgsDnZUKizTH1jqcSRp4ncv5M3IRWNuH5xxVV14x1oMBswb8+u27IbcS jbOedW49+tKFh68FmcYcV2ew8Y5neX7cR2veMb5cDdKuTRsVyfKnfk27+2DjBRso wDCaUBViU24BCNPW3XLwwk+TZS+5bYpzF+TvCHp1G2/Z7BQUGZzy3ea9wXKc/SKK K7uh7qqKuqoF5LKVWjcphQhWTSK9NO4bYhSbh86MwrnJYj4vNiQ2Sknp77YOb7bY iG9U0ZKafnWsQv88xOSNyLm7xo+MGrqT3KC1zvqdY9AJSbCZTdIL+A== =S+vc -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-06-07 21:55:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guys, Attached is a patch against Crypt::OpenPGP 1.00 which fixes a bug with decrypting non-compressed PGP 6.5.8 messages. Also, in a few moments I'll be uploading a fix to nymserv.pl which fixes some PGP 6.5.8 compatability problems. If some of you would be so kind as to create new nyms on hod.aarg.net using PGP 6.5.8 just to see how it works, I'd be very happy. For simplicity's sake, here's an easy reply block that doesn't require any headaches: :: Anon-To: your@address.here ** Pretty ingenious, eh? ;) - -- ;; Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> ;; ;; GPG Key ID: 2048R/8B4CBC9C <http://erik.arneson.org/> ;; ;; "Resistance to tyrants is obedience to God!" - Thomas Jefferson ;; -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iQEVAwUBPQErpttvZZqLTLycAQLZ0wgA2kNmG2GP8FZJOmx4NMpSu13m+YFGfnY1 WXgWv3oZERoAyBf+kcoP1SoRjFt9fiWcy7H4MBLyVzKbtX7Lwhy8Q9o+hWyXA9qX r1vOh44kOW8fxhEVHFIDu6ibkgI2X40uB7qFKzzNwHwKN3g6SZSdSCgIHSO4mscs N6jzFOofYdrXvLbm9Xpt5DXoBrDNaNBrYw09rhZZjQqa2JBdXghEv8s4OxG2Ez93 Lp9W3H14KPs5kFV+5DfDKCj8c00+qqtTzaQoGdO52oS67wQ0m1xd84BgsJgA2NXl ulQekoJ8LKYX0CYzgwyC/nLfOp8GH4LAteeMBK0bU0GkWVbQ9gsFQw== =SYmD -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-02-08 17:42:01
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Guys, I've just committed an important change. :) Nymserv was occasionally encrypting outgoing email to the wrong recipient. It shouldn't be doing this anymore. Also, the beginnings of the spamassassin stuff are in there. You can +spamfilter or -spamfilter in your configuration messages. It doesn't do anything, but you can still try. :) I haven't updated hod.aarg.net to use the new code yet, but I will sometime today. Please check over the diffs and see if you notice any glaring bugs or errors. - -- # Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> # # GPG Key ID: 1024D/43AD6AB8 <http://erik.arneson.org/> # # "Resistance to tyrants is obedience to God!" - Thomas Jefferson # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iEYEARECAAYFAjxkDd8ACgkQddRcHUOtarhoLQCfaGVpvl3XMZF4Og6fb1HakrA0 JccAmgLQvLU6NB/BmhpobN32q0gZSxs5 =INHc -----END PGP SIGNATURE----- |
|
From: Bill O'H. <wm...@re...> - 2002-01-31 00:27:05
|
On Wed, Jan 30, 2002 at 05:20:35PM -0500, Michael T. Shinn wrote: > Initially, we should look at supporting spamassassin before support > razor by itself. Spamassassin has rule sets (and it supports razor), so > it does a better job of dealing with the false positive problem than > razor by itself. I'd like to second this. I use Spamassassin as the spam filtering system for my users at my ISP, and it's amazingly effective. -Bill -- Bill O'Hanlon wm...@re... Professional Network Services, Inc. 612-379-3958 http://www.pro-ns.net |
|
From: Michael T. S. <mi...@sh...> - 2002-01-30 22:23:57
|
Erik Arneson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'm adding the Razor spam filtering stuff to nymserv right now, and I'm > wondering what the proper behavior should be? > > I figure we've got a few choices. The first choice is to let the > filtered mail just be dropped entirely. This is neat, but right now > Razor has some problems with its spam database being spoiled with > legitimate posts -- most notably recently have been the CERT and Bugtraq > messages being added to the Razor database. > > Another option might be to forward the message on to the user but > somehow specify that Razor tagged it as spam. However, this defeats the > purpose of getting rid of the spam in the first place, as it's still > using up remailer resources and causing the user to go through the > trouble of decrypting the received message after all. > > The option that would be the most difficult to implement would be to > store messages that were tagged by Razor and then send a summary to the > user with the "From" and "Subject" lines. If the user wants the > message, he'd have to reply with a special confirmation code. This > would be the safest, but it suffers from a number of problems, including > the problem of going through a lot of extra trouble for some potential > spam. > > If the Nymserv operator is willing to put in some time creating a good > whitelist for Razor, then maybe the first option would be the best. > > What do you guys think? Initially, we should look at supporting spamassassin before support razor by itself. Spamassassin has rule sets (and it supports razor), so it does a better job of dealing with the false positive problem than razor by itself. Regardless of which one we support first (spamassasin *wink* *wink* *nudge* *nudge*) I would say we need to support two options before we can offer any: 1. Bit bucket 2. Label the message as possible spam and send it on. Spamassassin does a nice job of marking up the message as to why its spam. It also allows for per user configuration of the rule sets, so an individual user can setup their rule sets. This allows a user to "train" their config to their unique situation, add white lists, etc. And eventually, switch to option 1. For the case of holding the messages and sending a summary, I recommend doing that last. Its an excellent feature, but it seems to me we need the first two options before we can have the third. Anyway, my two cents... in a hurry. :-) -- Michael T. Shinn PGPKey: 0x91C0781F GnuPG Key: BC626A27 |
|
From: Peter P. <pe...@pa...> - 2002-01-30 20:10:42
|
Hi Erik!
On Wed, 30 Jan 2002, Erik Arneson wrote:
> Config:
> From: atestuser
> Spam: drop (or mark)
> Options: +whatever -whoever +etc
how about:
| Options: +razor (enable or disable razor alltogether)
| Razor: drop|mark (only used when racor is set)
yours,
peter
--=20
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
|
|
From: Erik A. <er...@aa...> - 2002-01-30 19:44:34
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30 January 2002, Peter Palfrader <pe...@pa...> wrote: > Hi Erik! Howdy, Peter! > On Wed, 30 Jan 2002, Erik Arneson wrote: > > I'm adding the Razor spam filtering stuff to nymserv right now, and I'm > > wondering what the proper behavior should be? > > [1. drop] > [2. mark] > [3. store] > > Let the user decide between 1 and 2. For 2 just add an addition header > in the original mail (which the user will get after all the decryption > stuff). Something like "X-Spam: racor" or so. That way the user can > score the mails at his end if he wishes to. Ok, so I guess we should have two different flags.... razordrop and razormark. Sound good? It could optionally be an entirely separate header. Maybe something like this: Config: From: atestuser Spam: drop (or mark) Options: +whatever -whoever +etc Which of those seems easier to handle? - -- # Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> # # GPG Key ID: 1024D/43AD6AB8 <http://erik.arneson.org/> # # "Resistance to tyrants is obedience to God!" - Thomas Jefferson # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iEYEARECAAYFAjxYTRwACgkQddRcHUOtargEqQCfbCMCDEAIJGUBMcY9hd2Jr4+2 fTQAoJIamXXhP7q/J583vPOIL2dSwXk4 =CSZO -----END PGP SIGNATURE----- |
|
From: Peter P. <pe...@pa...> - 2002-01-30 19:40:21
|
Hi Erik!
On Wed, 30 Jan 2002, Erik Arneson wrote:
> I'm adding the Razor spam filtering stuff to nymserv right now, and I'm
> wondering what the proper behavior should be?
[1. drop]
[2. mark]
[3. store]
Let the user decide between 1 and 2. For 2 just add an addition header
in the original mail (which the user will get after all the decryption
stuff). Something like "X-Spam: racor" or so. That way the user can
score the mails at his end if he wishes to.
yours,
peter
--=20
PGP signed and encrypted | .''`. ** Debian GNU/Linux **
messages preferred. | : :' : The universal
| `. `' Operating System
http://www.palfrader.org/ | `- http://www.debian.org/
|
|
From: Erik A. <er...@aa...> - 2002-01-30 19:17:49
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm adding the Razor spam filtering stuff to nymserv right now, and I'm wondering what the proper behavior should be? I figure we've got a few choices. The first choice is to let the filtered mail just be dropped entirely. This is neat, but right now Razor has some problems with its spam database being spoiled with legitimate posts -- most notably recently have been the CERT and Bugtraq messages being added to the Razor database. Another option might be to forward the message on to the user but somehow specify that Razor tagged it as spam. However, this defeats the purpose of getting rid of the spam in the first place, as it's still using up remailer resources and causing the user to go through the trouble of decrypting the received message after all. The option that would be the most difficult to implement would be to store messages that were tagged by Razor and then send a summary to the user with the "From" and "Subject" lines. If the user wants the message, he'd have to reply with a special confirmation code. This would be the safest, but it suffers from a number of problems, including the problem of going through a lot of extra trouble for some potential spam. If the Nymserv operator is willing to put in some time creating a good whitelist for Razor, then maybe the first option would be the best. What do you guys think? - -- # Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> # # GPG Key ID: 1024D/43AD6AB8 <http://erik.arneson.org/> # # "Resistance to tyrants is obedience to God!" - Thomas Jefferson # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iEYEARECAAYFAjxYRtIACgkQddRcHUOtarhqWQCgg7SMYbeq1CP0Glo9MTBJRhxm m1kAniE/P4+Tkg/lglJIl2N3Bx1LBy4n =HpAI -----END PGP SIGNATURE----- |
|
From: Erik A. <er...@aa...> - 2002-01-30 16:51:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 30 January 2002, Michael T. Shinn <mi...@sh...> wrote: > Erik Arneson wrote: > > I was wondering when we should mention this project on, say, the > > mixmaster-devel list? We'd get some more folks over here to do some > > testing, and it might be good for us. > > > > What do you all think? > > The sooner the better. :-) All right, I'll post something today then. :) - -- # Erik Arneson <er...@aa...> AARG Net <http://www.aarg.net/> # # GPG Key ID: 1024D/43AD6AB8 <http://erik.arneson.org/> # # "Resistance to tyrants is obedience to God!" - Thomas Jefferson # -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.6 iEYEARECAAYFAjxYJJUACgkQddRcHUOtarjetACfR9IXhIXxC1PoGdEELybZrASU 7M8AoIe4dE7+beiUe8ZhzRfxbBfmSYmn =nTVO -----END PGP SIGNATURE----- |
|
From: Michael T. S. <mi...@sh...> - 2002-01-30 16:04:43
|
Erik Arneson wrote: > Guys, > > I was wondering when we should mention this project on, say, the > mixmaster-devel list? We'd get some more folks over here to do some > testing, and it might be good for us. > > What do you all think? The sooner the better. :-) -- Michael T. Shinn PGPKey: 0x91C0781F GnuPG Key: BC626A27 |
|
From: Erik A. <er...@aa...> - 2002-01-30 14:59:37
|
Guys, I was wondering when we should mention this project on, say, the mixmaster-devel list? We'd get some more folks over here to do some testing, and it might be good for us. What do you all think? -- > Erik Arneson <er...@aa...> JD, Ashland Lodge No. 23 < > GPG Key ID: 1024D/43AD6AB8 RAM, Siskiyou Chapter No. 21 < > <http://erik.arneson.org/> <http://www.aarg.net/mason> < |
