From owner-ietf-mta-filters Sun Jun 8 18:00:11 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5910BAF022133 for ; Sun, 8 Jun 2003 18:00:11 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5910Bt1022132 for ietf-mta-filters-bks; Sun, 8 Jun 2003 18:00:11 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h59109AF022127 for ; Sun, 8 Jun 2003 18:00:10 -0700 (PDT) (envelope-from ned.freed@mrochek.com) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KWUXVZP0B400CUGD@mauve.mrochek.com> for ietf-mta-filters@imc.org; Sun, 08 Jun 2003 18:00:05 -0700 (PDT) Date: Wed, 28 May 2003 17:39:23 -0400 From: The IESG Subject: Protocol Action: Sieve -- Subaddress Extension to Proposed Standard To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board Message-id: <200305282139.RAA25350@ietf.org> Content-transfer-encoding: 7BIT Spam-test: False ; 1.1 / 4.5 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The IESG has approved the Internet-Draft 'Sieve -- Subaddress Extension' as a Proposed Standard. This has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact persons are Ned Freed and Ted Hardie. Technical Summary On email systems that allow for "subaddressing" or "detailed addressing" (eg, "ken+sieve@example.org"), it is sometimes desirable to make comparisons against these sub-parts of addresses. This draft defines an extension to the Sieve mail filtering language that allows users to compare against the user and detail parts of an address. Working Group Summary This document is an extension to the sieve mail filtering language defined in RFC 3028. There are already several implementations of this extension. Protocol Quality Ned Freed reviewed the specification for the IESG. RFC Editor note Please change the title of this document to "Sieve Email Filtering -- Subaddress Extension" to avoid confusion with other uses of the term "subaddressing" In the first paragraph of the introduction, the phrase "set of messages" needs to be changed to "set of mailboxes". From owner-ietf-mta-filters Thu Jun 12 06:51:27 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CDpRrb057751 for ; Thu, 12 Jun 2003 06:51:27 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5CDpR93057749 for ietf-mta-filters-bks; Thu, 12 Jun 2003 06:51:27 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from max.kde.org (max.kde.org [134.2.170.93]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CDpPrb057739 for ; Thu, 12 Jun 2003 06:51:25 -0700 (PDT) (envelope-from mutz@kde.org) Received: from dirichlet.Physik.Uni-Bielefeld.DE (dirichlet.Physik.Uni-Bielefeld.DE [129.70.125.234]) by max.kde.org (Postfix) with ESMTP id 07930B0488 for ; Thu, 12 Jun 2003 15:51:25 +0200 (CEST) From: Marc Mutz Organization: KDE To: ietf-mta-filters@imc.org Subject: vacation extension: Needs to say something about message generation. Date: Thu, 12 Jun 2003 15:31:08 +0200 User-Agent: KMail/1.5.9 X-PGP-Key: 0xBDBFE838 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_cCI6+76gU4UQGyW"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200306121531.08609@sendmail.mutz.com> Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --Boundary-02=_cCI6+76gU4UQGyW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi! IMO, the vacation draft needs to say that the vacation response=20 generation mechanism MUST take charsets and content-types into account=20 even if the :mime parameter is not given. Implementations SHOULD choose a fitting charset and recode the text=20 given in the script (in UTF-8) into the chosen charset and apply a=20 suitable CTE. At the very minimum, implementations should add Content-Type: text/plain; charset=3Dutf-8 Content-Transfer-Encoding: 8bit MIME-version: 1.0 to the header of the generated message. This might sound obvious, but we just encountered a vacation response=20 message that had no MIME headers whatsoever, but contained 8bit-encoded=20 UTF-8 text. Marc =2D-=20 Mutig warf sich die kleine =DCberwachungskamera zwischen T=E4ter und Opfer! --Rena Tangens / FoeBuD e.V. --Boundary-02=_cCI6+76gU4UQGyW Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+6ICc3oWD+L2/6DgRAjXgAKCAtPulipoo6fs6O0HJ04xfIc3qGQCgk2Ex xnXrDIhJxyr7u7pyftoKIUk= =QnrI -----END PGP SIGNATURE----- --Boundary-02=_cCI6+76gU4UQGyW-- From owner-ietf-mta-filters Thu Jun 12 09:11:28 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CGBSrb069549 for ; Thu, 12 Jun 2003 09:11:28 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5CGBSMZ069548 for ietf-mta-filters-bks; Thu, 12 Jun 2003 09:11:28 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CGBPrb069542 for ; Thu, 12 Jun 2003 09:11:26 -0700 (PDT) (envelope-from ned.freed@mrochek.com) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KWZYR4AVV400CUGD@mauve.mrochek.com> for ietf-mta-filters@imc.org; Thu, 12 Jun 2003 09:11:20 -0700 (PDT) Date: Thu, 12 Jun 2003 09:04:40 -0700 (PDT) From: ned.freed@mrochek.com Subject: Re: vacation extension: Needs to say something about message generation. In-reply-to: "Your message dated Thu, 12 Jun 2003 15:31:08 +0200" <200306121531.08609@sendmail.mutz.com> To: Marc Mutz Cc: ietf-mta-filters@imc.org Message-id: <01KX02R3AMXM00CUGD@mauve.mrochek.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=iso-8859-1 Content-transfer-encoding: 7BIT References: <200306121531.08609@sendmail.mutz.com> Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > IMO, the vacation draft needs to say that the vacation response > generation mechanism MUST take charsets and content-types into account > even if the :mime parameter is not given. > Implementations SHOULD choose a fitting charset and recode the text > given in the script (in UTF-8) into the chosen charset and apply a > suitable CTE. I have no problem with suggesting this, but I don't think it rises to the level of a SHOULD. I think we need to stop short of any sort of requirement (and SHOULD is a form of requirement) that stuff be recoded from UTF-8 into other charsets. Sending UTF-8 without any hint of recoding needs to be an acceptable option. > At the very minimum, implementations should add > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > MIME-version: 1.0 > to the header of the generated message. Reminding people that appropriate MIME labelling MUST be used for whatever charset is generated is a reasonable thing to do, of course. > This might sound obvious, but we just encountered a vacation response > message that had no MIME headers whatsoever, but contained 8bit-encoded > UTF-8 text. Sure. But we already have rules that say such messages are illegal, regardless of whether or not they are a vacation response. It is far from clear that anything we say will prevent this. Ned From owner-ietf-mta-filters Sat Jun 21 12:24:56 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5LJOurb093149 for ; Sat, 21 Jun 2003 12:24:56 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5LJOujd093148 for ietf-mta-filters-bks; Sat, 21 Jun 2003 12:24:56 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5LJOsrb093143 for ; Sat, 21 Jun 2003 12:24:54 -0700 (PDT) (envelope-from wysiwyh@web.de) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19Tnyp-0003J6-00 for ietf-mta-filters@imc.org; Sat, 21 Jun 2003 21:24:55 +0200 Received: from [80.129.159.249] (helo=NOTE) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19Tnyp-0001wh-00 for ietf-mta-filters@imc.org; Sat, 21 Jun 2003 21:24:55 +0200 Message-ID: <01ea01c3382a$faac17b0$dc01a8c0@NOTE> From: "hm" To: Subject: changing the address from a redirect of sieve Date: Sat, 21 Jun 2003 21:26:13 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E7_01C3383B.BDACCBF0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_01E7_01C3383B.BDACCBF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I like to know howto change the address when I redirect an email, of = course the sender email address is like cyrus@host; but I want to have = myname@specialhost Thanx ahead... ------=_NextPart_000_01E7_01C3383B.BDACCBF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
I like to know howto change the address = when I=20 redirect an email, of course the
sender email address is like cyrus@host; but I want to have myname@specialhost
 
Thanx=20 ahead...
------=_NextPart_000_01E7_01C3383B.BDACCBF0-- From owner-ietf-mta-filters Sun Jun 29 13:54:50 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5TKsoFK035559 for ; Sun, 29 Jun 2003 13:54:50 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5TKsoHH035558 for ietf-mta-filters-bks; Sun, 29 Jun 2003 13:54:50 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from smtp-out.comcast.net (smtp-out.comcast.net [24.153.64.116]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5TKsnFK035551 for ; Sun, 29 Jun 2003 13:54:49 -0700 (PDT) (envelope-from ted.garrett@tedgarrett.com) Received: from morpheus.tedgarrett.com (pcp04178202pcs.dalect01.va.comcast.net [68.86.240.127]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HH900INVGON9H@mtaout01.icomcast.net> for ietf-mta-filters@imc.org; Sun, 29 Jun 2003 16:53:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by morpheus.tedgarrett.com (Postfix) with ESMTP id 473741852170 for ; Sun, 29 Jun 2003 16:53:11 -0400 (EDT) Received: by morpheus.tedgarrett.com (Postfix, from userid 65534) id 0E1691851A61; Sun, 29 Jun 2003 16:53:10 -0400 (EDT) Received: from morpheus (localhost [127.0.0.1]) by morpheus.tedgarrett.com (Postfix) with SMTP id D036F1852170 for ; Sun, 29 Jun 2003 16:53:08 -0400 (EDT) Received: from 192.168.1.10 (SquirrelMail authenticated user teddygee) by Morpheus.tedgarrett.com with HTTP; Sun, 29 Jun 2003 16:53:08 -0400 (EDT) Date: Sun, 29 Jun 2003 16:53:08 -0400 (EDT) From: Ted Garrett Subject: Sieve suddenly missinterprets X-Spam-Status To: Sieve Mailing List Message-id: <33651.192.168.1.10.1056919988.squirrel@Morpheus.tedgarrett.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 User-Agent: SquirrelMail/1.4.0 X-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_10,PRIORITY_NO_NAME,USER_AGENT version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Virus-Scanned: by AMaViS snapshot-20020531 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: For the longest time, the first rule in my active sieve script was - if anyof (header :contains "X-Spam-Status" "Yes") { fileinto INBOX.Spam.Assassin; stop; } And this worked just fine. Suddenly about a week ago, sieve started pouring ALL of my mail into the spam assassin mailbox. In order to get it to work properly again, I had to delete the rule, save a new script, delete the original script, add rules to the new script, then add the old rule back into the new script (not as the first rule) and move it up from the bottom of the script to the top. I guess I'm looking for whether anyone else has seen anything this strange or not. Thanks! From owner-ietf-mta-filters Mon Jun 30 15:08:17 2003 Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5UM8HFK082309 for ; Mon, 30 Jun 2003 15:08:17 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5UM8HAJ082308 for ietf-mta-filters-bks; Mon, 30 Jun 2003 15:08:17 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from www.fastmail.fm (www.fastmail.fm [66.111.4.2] (may be forged)) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5UM8GFK082303 for ; Mon, 30 Jun 2003 15:08:16 -0700 (PDT) (envelope-from matthew@elvey.fastmail.fm) Received: from www.fastmail.fm (server1.internal [10.202.2.132]) by localhost.localdomain (Postfix) with ESMTP id 39AB72521E for ; Mon, 30 Jun 2003 18:08:15 -0400 (EDT) Received: from 127.0.0.1 ([127.0.0.1] helo=www.fastmail.fm) by messagingengine.com with SMTP; Mon, 30 Jun 2003 18:08:15 -0400 X-Epoch: 1057010895 X-Sasl-enc: TtATqd4/3A/PkOnvFW43Ww Received: from elvey.fastmail.fm (adsl-66-126-168-113.dsl.snfc21.pacbell.net [66.126.168.113]) by www.fastmail.fm (Postfix) with ESMTP id 8D6FF37F93 for ; Mon, 30 Jun 2003 18:08:13 -0400 (EDT) Message-ID: <3F00B4CD.5090903@elvey.fastmail.fm> Date: Mon, 30 Jun 2003 15:08:13 -0700 From: "Matthew Elvey (FM)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-mta-filters@imc.org Subject: Quizzic: Spam equivalent to EICAR test virus proposal. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Preamble: ======= Sending this to this list, as it relates directly to the charter (filtering), though it's not Sieve related, which has been the focus of the list for a while. I haven't posted this anywhere else yet, and figure this smallish group could provide some initial feedback to see if this idea has legs and should become an internet-draft, if I'm reinventing the wheel, or what. To start off with, a few I do/don't think this is needed (because ___) comments would be appreciated. I've wanted something like this to exist several times, myself. Rationale: ======= I think a standard equivalent to the EICAR test virus for spam is needed, and would make a useful RFC/'net standard. (The EICAR test provides a safe, easy way to test whether your anti-virus software is doing its job. If the antivirus software on your computer is working, it should detect it as the EICAR Test Virus. Of course, it's not a virus but instead a harmless 70 byte file that most or all antivirus software programs are supposed to detect for testing purposes only. See http://www.its.uiowa.edu/cs/helpdesk/virus/virusfaq/eicar.htm) For example, if I want to test that some kind of anti-spam system is working, it would be useful to be able to send a message and expect it to be treated as spam without sending something that a human would think was spam. It would be useful for testing and debugging spam-reporting and abuse-incident-handling systems. It could be used to detect the presence of a challenge-response system (unless the system didn't want to be detected) if a prescribed response was specified for such systems. List managers and list management software could use this info productively. It could be useful for populating a whitelist (just send a Quizzic email to everyone in your address book using a specified SMTP server that intercepts the email. If the users messes up, Quizzic will limit the damage.) Or I want to test a system in a way that hopefully won't bother anyone even if it malfunctions. Proposal: ====== I think a specific string in the subject would to the trick best, such as the first 9 characters of the subject must be "ADV:QZWK:" Subject: ADV:QZWK:followed by any text. N'importe quoi. Requiring a specific sender (e.g. spamtest@example.com) or sending domain anything@ADVQZWK.com would be alternatives. These would be useful for systems that don't look at the body of a message, such as domain-based or address-based blocklists. Or perhaps a single line in the (plain text)body with prescribed text : ADV:QZWK:Body This is a test email. Blah blah. All compliant antispam systems MUST consider it as spam. Perhaps more specific instructions could be given. Perhaps challenge-response systems would get more specific instructions: "ADV:QZWK:Challenge:" indicates that the message SHOULD/MUST be challenged by a RFC-compliant challenge-response system, even if the mail would normally be let through, if the body is compliant+. "ADV:QZWK:Grey:" indicates a system MUST file it in a [held mail/grey mail/probable spam/uncertain] category if the system supports such a category and the body is compliant+. "ADV:QZWK:NoChallenge:" indicates a challenge-response system MUST NOT challenge it and should/must file it in /dev/null. Compliant systems MUST send the strings captialized as specified, MUST recognize the strings if captialized as specified, and MAY perform case-insensitive matches. Abuse response systems SHOULD/MUST NOT treat abuse reports of messages reported that are in compliance with this document as abuse (unless they come in such volume that they are a DoS attack). All test spam messages sent must be at least minimally compliant with this spec. +There should to be limits to help avert abuse of these options. Perhaps the subject and body of the message should be limited to, say, 80 characters of (plain) text each, for these two options. Notes: ==== I chose ADV:QZWK: as a short sequence unlikely to be seen at random, ever. ADV: to take advantage of the existing convention that this indicates spam, and QZWK (pronounced Quizzic ?) as some of the least common letters in language. Hopefully they aren't common or missing from any commonly used foreign keyboards. As a domain, it isn't taken (don't be a jerk!). Anyway, this formatted more as a stream of consciousness, but please provide feedback. This RFC should be generalized to apply to any applicable system (SMS, IM, etc.) Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5UM8HFK082309 for ; Mon, 30 Jun 2003 15:08:17 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5UM8HAJ082308 for ietf-mta-filters-bks; Mon, 30 Jun 2003 15:08:17 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from www.fastmail.fm (www.fastmail.fm [66.111.4.2] (may be forged)) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5UM8GFK082303 for ; Mon, 30 Jun 2003 15:08:16 -0700 (PDT) (envelope-from matthew@elvey.fastmail.fm) Received: from www.fastmail.fm (server1.internal [10.202.2.132]) by localhost.localdomain (Postfix) with ESMTP id 39AB72521E for ; Mon, 30 Jun 2003 18:08:15 -0400 (EDT) Received: from 127.0.0.1 ([127.0.0.1] helo=www.fastmail.fm) by messagingengine.com with SMTP; Mon, 30 Jun 2003 18:08:15 -0400 X-Epoch: 1057010895 X-Sasl-enc: TtATqd4/3A/PkOnvFW43Ww Received: from elvey.fastmail.fm (adsl-66-126-168-113.dsl.snfc21.pacbell.net [66.126.168.113]) by www.fastmail.fm (Postfix) with ESMTP id 8D6FF37F93 for ; Mon, 30 Jun 2003 18:08:13 -0400 (EDT) Message-ID: <3F00B4CD.5090903@elvey.fastmail.fm> Date: Mon, 30 Jun 2003 15:08:13 -0700 From: "Matthew Elvey (FM)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030612 X-Accept-Language: en-us, en MIME-Version: 1.0 To: ietf-mta-filters@imc.org Subject: Quizzic: Spam equivalent to EICAR test virus proposal. Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: Preamble: ======= Sending this to this list, as it relates directly to the charter (filtering), though it's not Sieve related, which has been the focus of the list for a while. I haven't posted this anywhere else yet, and figure this smallish group could provide some initial feedback to see if this idea has legs and should become an internet-draft, if I'm reinventing the wheel, or what. To start off with, a few I do/don't think this is needed (because ___) comments would be appreciated. I've wanted something like this to exist several times, myself. Rationale: ======= I think a standard equivalent to the EICAR test virus for spam is needed, and would make a useful RFC/'net standard. (The EICAR test provides a safe, easy way to test whether your anti-virus software is doing its job. If the antivirus software on your computer is working, it should detect it as the EICAR Test Virus. Of course, it's not a virus but instead a harmless 70 byte file that most or all antivirus software programs are supposed to detect for testing purposes only. See http://www.its.uiowa.edu/cs/helpdesk/virus/virusfaq/eicar.htm) For example, if I want to test that some kind of anti-spam system is working, it would be useful to be able to send a message and expect it to be treated as spam without sending something that a human would think was spam. It would be useful for testing and debugging spam-reporting and abuse-incident-handling systems. It could be used to detect the presence of a challenge-response system (unless the system didn't want to be detected) if a prescribed response was specified for such systems. List managers and list management software could use this info productively. It could be useful for populating a whitelist (just send a Quizzic email to everyone in your address book using a specified SMTP server that intercepts the email. If the users messes up, Quizzic will limit the damage.) Or I want to test a system in a way that hopefully won't bother anyone even if it malfunctions. Proposal: ====== I think a specific string in the subject would to the trick best, such as the first 9 characters of the subject must be "ADV:QZWK:" Subject: ADV:QZWK:followed by any text. N'importe quoi. Requiring a specific sender (e.g. spamtest@example.com) or sending domain anything@ADVQZWK.com would be alternatives. These would be useful for systems that don't look at the body of a message, such as domain-based or address-based blocklists. Or perhaps a single line in the (plain text)body with prescribed text : ADV:QZWK:Body This is a test email. Blah blah. All compliant antispam systems MUST consider it as spam. Perhaps more specific instructions could be given. Perhaps challenge-response systems would get more specific instructions: "ADV:QZWK:Challenge:" indicates that the message SHOULD/MUST be challenged by a RFC-compliant challenge-response system, even if the mail would normally be let through, if the body is compliant+. "ADV:QZWK:Grey:" indicates a system MUST file it in a [held mail/grey mail/probable spam/uncertain] category if the system supports such a category and the body is compliant+. "ADV:QZWK:NoChallenge:" indicates a challenge-response system MUST NOT challenge it and should/must file it in /dev/null. Compliant systems MUST send the strings captialized as specified, MUST recognize the strings if captialized as specified, and MAY perform case-insensitive matches. Abuse response systems SHOULD/MUST NOT treat abuse reports of messages reported that are in compliance with this document as abuse (unless they come in such volume that they are a DoS attack). All test spam messages sent must be at least minimally compliant with this spec. +There should to be limits to help avert abuse of these options. Perhaps the subject and body of the message should be limited to, say, 80 characters of (plain) text each, for these two options. Notes: ==== I chose ADV:QZWK: as a short sequence unlikely to be seen at random, ever. ADV: to take advantage of the existing convention that this indicates spam, and QZWK (pronounced Quizzic ?) as some of the least common letters in language. Hopefully they aren't common or missing from any commonly used foreign keyboards. As a domain, it isn't taken (don't be a jerk!). Anyway, this formatted more as a stream of consciousness, but please provide feedback. This RFC should be generalized to apply to any applicable system (SMS, IM, etc.) Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5TKsoFK035559 for ; Sun, 29 Jun 2003 13:54:50 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5TKsoHH035558 for ietf-mta-filters-bks; Sun, 29 Jun 2003 13:54:50 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from smtp-out.comcast.net (smtp-out.comcast.net [24.153.64.116]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5TKsnFK035551 for ; Sun, 29 Jun 2003 13:54:49 -0700 (PDT) (envelope-from ted.garrett@tedgarrett.com) Received: from morpheus.tedgarrett.com (pcp04178202pcs.dalect01.va.comcast.net [68.86.240.127]) by mtaout01.icomcast.net (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003)) with ESMTP id <0HH900INVGON9H@mtaout01.icomcast.net> for ietf-mta-filters@imc.org; Sun, 29 Jun 2003 16:53:11 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by morpheus.tedgarrett.com (Postfix) with ESMTP id 473741852170 for ; Sun, 29 Jun 2003 16:53:11 -0400 (EDT) Received: by morpheus.tedgarrett.com (Postfix, from userid 65534) id 0E1691851A61; Sun, 29 Jun 2003 16:53:10 -0400 (EDT) Received: from morpheus (localhost [127.0.0.1]) by morpheus.tedgarrett.com (Postfix) with SMTP id D036F1852170 for ; Sun, 29 Jun 2003 16:53:08 -0400 (EDT) Received: from 192.168.1.10 (SquirrelMail authenticated user teddygee) by Morpheus.tedgarrett.com with HTTP; Sun, 29 Jun 2003 16:53:08 -0400 (EDT) Date: Sun, 29 Jun 2003 16:53:08 -0400 (EDT) From: Ted Garrett Subject: Sieve suddenly missinterprets X-Spam-Status To: Sieve Mailing List Message-id: <33651.192.168.1.10.1056919988.squirrel@Morpheus.tedgarrett.com> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 User-Agent: SquirrelMail/1.4.0 X-Spam-Status: No, hits=-5.0 required=5.0 tests=AWL,BAYES_10,PRIORITY_NO_NAME,USER_AGENT version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) X-Virus-Scanned: by AMaViS snapshot-20020531 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: For the longest time, the first rule in my active sieve script was - if anyof (header :contains "X-Spam-Status" "Yes") { fileinto INBOX.Spam.Assassin; stop; } And this worked just fine. Suddenly about a week ago, sieve started pouring ALL of my mail into the spam assassin mailbox. In order to get it to work properly again, I had to delete the rule, save a new script, delete the original script, add rules to the new script, then add the old rule back into the new script (not as the first rule) and move it up from the bottom of the script to the top. I guess I'm looking for whether anyone else has seen anything this strange or not. Thanks! Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5LJOurb093149 for ; Sat, 21 Jun 2003 12:24:56 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5LJOujd093148 for ietf-mta-filters-bks; Sat, 21 Jun 2003 12:24:56 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5LJOsrb093143 for ; Sat, 21 Jun 2003 12:24:54 -0700 (PDT) (envelope-from wysiwyh@web.de) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 19Tnyp-0003J6-00 for ietf-mta-filters@imc.org; Sat, 21 Jun 2003 21:24:55 +0200 Received: from [80.129.159.249] (helo=NOTE) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 19Tnyp-0001wh-00 for ietf-mta-filters@imc.org; Sat, 21 Jun 2003 21:24:55 +0200 Message-ID: <01ea01c3382a$faac17b0$dc01a8c0@NOTE> From: "hm" To: Subject: changing the address from a redirect of sieve Date: Sat, 21 Jun 2003 21:26:13 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01E7_01C3383B.BDACCBF0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: This is a multi-part message in MIME format. ------=_NextPart_000_01E7_01C3383B.BDACCBF0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I like to know howto change the address when I redirect an email, of = course the sender email address is like cyrus@host; but I want to have = myname@specialhost Thanx ahead... ------=_NextPart_000_01E7_01C3383B.BDACCBF0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
 
I like to know howto change the address = when I=20 redirect an email, of course the
sender email address is like cyrus@host; but I want to have myname@specialhost
 
Thanx=20 ahead...
------=_NextPart_000_01E7_01C3383B.BDACCBF0-- Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CGBSrb069549 for ; Thu, 12 Jun 2003 09:11:28 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5CGBSMZ069548 for ietf-mta-filters-bks; Thu, 12 Jun 2003 09:11:28 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CGBPrb069542 for ; Thu, 12 Jun 2003 09:11:26 -0700 (PDT) (envelope-from ned.freed@mrochek.com) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KWZYR4AVV400CUGD@mauve.mrochek.com> for ietf-mta-filters@imc.org; Thu, 12 Jun 2003 09:11:20 -0700 (PDT) Date: Thu, 12 Jun 2003 09:04:40 -0700 (PDT) From: ned.freed@mrochek.com Subject: Re: vacation extension: Needs to say something about message generation. In-reply-to: "Your message dated Thu, 12 Jun 2003 15:31:08 +0200" <200306121531.08609@sendmail.mutz.com> To: Marc Mutz Cc: ietf-mta-filters@imc.org Message-id: <01KX02R3AMXM00CUGD@mauve.mrochek.com> MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=iso-8859-1 Content-transfer-encoding: 7BIT References: <200306121531.08609@sendmail.mutz.com> Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: > IMO, the vacation draft needs to say that the vacation response > generation mechanism MUST take charsets and content-types into account > even if the :mime parameter is not given. > Implementations SHOULD choose a fitting charset and recode the text > given in the script (in UTF-8) into the chosen charset and apply a > suitable CTE. I have no problem with suggesting this, but I don't think it rises to the level of a SHOULD. I think we need to stop short of any sort of requirement (and SHOULD is a form of requirement) that stuff be recoded from UTF-8 into other charsets. Sending UTF-8 without any hint of recoding needs to be an acceptable option. > At the very minimum, implementations should add > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > MIME-version: 1.0 > to the header of the generated message. Reminding people that appropriate MIME labelling MUST be used for whatever charset is generated is a reasonable thing to do, of course. > This might sound obvious, but we just encountered a vacation response > message that had no MIME headers whatsoever, but contained 8bit-encoded > UTF-8 text. Sure. But we already have rules that say such messages are illegal, regardless of whether or not they are a vacation response. It is far from clear that anything we say will prevent this. Ned Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CDpRrb057751 for ; Thu, 12 Jun 2003 06:51:27 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5CDpR93057749 for ietf-mta-filters-bks; Thu, 12 Jun 2003 06:51:27 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from max.kde.org (max.kde.org [134.2.170.93]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5CDpPrb057739 for ; Thu, 12 Jun 2003 06:51:25 -0700 (PDT) (envelope-from mutz@kde.org) Received: from dirichlet.Physik.Uni-Bielefeld.DE (dirichlet.Physik.Uni-Bielefeld.DE [129.70.125.234]) by max.kde.org (Postfix) with ESMTP id 07930B0488 for ; Thu, 12 Jun 2003 15:51:25 +0200 (CEST) From: Marc Mutz Organization: KDE To: ietf-mta-filters@imc.org Subject: vacation extension: Needs to say something about message generation. Date: Thu, 12 Jun 2003 15:31:08 +0200 User-Agent: KMail/1.5.9 X-PGP-Key: 0xBDBFE838 MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_cCI6+76gU4UQGyW"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200306121531.08609@sendmail.mutz.com> Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --Boundary-02=_cCI6+76gU4UQGyW Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi! IMO, the vacation draft needs to say that the vacation response=20 generation mechanism MUST take charsets and content-types into account=20 even if the :mime parameter is not given. Implementations SHOULD choose a fitting charset and recode the text=20 given in the script (in UTF-8) into the chosen charset and apply a=20 suitable CTE. At the very minimum, implementations should add Content-Type: text/plain; charset=3Dutf-8 Content-Transfer-Encoding: 8bit MIME-version: 1.0 to the header of the generated message. This might sound obvious, but we just encountered a vacation response=20 message that had no MIME headers whatsoever, but contained 8bit-encoded=20 UTF-8 text. Marc =2D-=20 Mutig warf sich die kleine =DCberwachungskamera zwischen T=E4ter und Opfer! --Rena Tangens / FoeBuD e.V. --Boundary-02=_cCI6+76gU4UQGyW Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQA+6ICc3oWD+L2/6DgRAjXgAKCAtPulipoo6fs6O0HJ04xfIc3qGQCgk2Ex xnXrDIhJxyr7u7pyftoKIUk= =QnrI -----END PGP SIGNATURE----- --Boundary-02=_cCI6+76gU4UQGyW-- Received: from above.proper.com (localhost [127.0.0.1]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h5910BAF022133 for ; Sun, 8 Jun 2003 18:00:11 -0700 (PDT) (envelope-from owner-ietf-mta-filters@mail.imc.org) Received: (from majordom@localhost) by above.proper.com (8.12.9/8.12.9/Submit) id h5910Bt1022132 for ietf-mta-filters-bks; Sun, 8 Jun 2003 18:00:11 -0700 (PDT) X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f Received: from mauve.mrochek.com (mauve.mrochek.com [209.55.107.55]) by above.proper.com (8.12.9/8.12.8) with ESMTP id h59109AF022127 for ; Sun, 8 Jun 2003 18:00:10 -0700 (PDT) (envelope-from ned.freed@mrochek.com) Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01KWUXVZP0B400CUGD@mauve.mrochek.com> for ietf-mta-filters@imc.org; Sun, 08 Jun 2003 18:00:05 -0700 (PDT) Date: Wed, 28 May 2003 17:39:23 -0400 From: The IESG Subject: Protocol Action: Sieve -- Subaddress Extension to Proposed Standard To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board Message-id: <200305282139.RAA25350@ietf.org> Content-transfer-encoding: 7BIT Spam-test: False ; 1.1 / 4.5 Sender: owner-ietf-mta-filters@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: The IESG has approved the Internet-Draft 'Sieve -- Subaddress Extension' as a Proposed Standard. This has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact persons are Ned Freed and Ted Hardie. Technical Summary On email systems that allow for "subaddressing" or "detailed addressing" (eg, "ken+sieve@example.org"), it is sometimes desirable to make comparisons against these sub-parts of addresses. This draft defines an extension to the Sieve mail filtering language that allows users to compare against the user and detail parts of an address. Working Group Summary This document is an extension to the sieve mail filtering language defined in RFC 3028. There are already several implementations of this extension. Protocol Quality Ned Freed reviewed the specification for the IESG. RFC Editor note Please change the title of this document to "Sieve Email Filtering -- Subaddress Extension" to avoid confusion with other uses of the term "subaddressing" In the first paragraph of the introduction, the phrase "set of messages" needs to be changed to "set of mailboxes".