Pigeonhole, vacation being sent incorrectly

[Nick Edwards]

actually . you are, i missed it all the noise horde seems to generate,
precedence covers  pretty much all of that crap, i was glad I left
horde, seems its still as stuffed as ever

On 11/26/14, Nick Edwards <nick.z.edwards at gmail.com> wrote:
> jesus!
> learn to use  precedence
>
>
> On 11/26/14, Harry Mills <harry at opendium.com> wrote:
>> Hi,
>>
>> I have an issue with a vacation message in a sieve script. I can't see
>> an error in the script itself.
>>
>> Pigeonhole version: 0.4.2-32
>> Dovecot Version: 2.2.10
>>
>> The script was created by Ingo (part of the Horde suite), but I think
>> the script is fine. The problem is that when a message is sent to the
>> "everyone" group (and alias for every person in the organisation),
>> vacation messages are being sent back which I believe is an error.
>>
>> The script is:
>>
>>
>> ===============================================
>> # Sieve Filter
>> # Generated by Ingo (http://www.horde.org/apps/ingo/) (11/11/14,
>> 5:20:06 pm GMT)
>> require ["vacation", "regex", "fileinto"];
>> # Vacation
>> if allof ( not exists "list-help", not exists "list-unsubscribe", not
>> exists "list-subscribe", not exists "list-owner", not exists
>> "list-post", not exists "list-archive", not exists "list-id", not exists
>> "Mailing-List", not header :comparator "i;ascii-casemap" :is
>> "Precedence" ["list", "bulk", "junk"], not header :comparator
>> "i;ascii-casemap" :matches "To" "Multiple recipients of*" ) {
>>      if header :regex "Received" "^.*(2014) (\\(.*\\) )?..:..:..
>> (\\(.*\\) )?((\\+|\\-)[[:digit:]]{4}|.{1,5})( \\(.*\\))?$" {
>>      if header :regex "Received" "^.*(Nov) (\\(.*\\) )?.... (\\(.*\\)
>> )?..:..:.. (\\(.*\\) )?((\\+|\\-)[[:digit:]]{4}|.{1,5})( \\(.*\\))?$" {
>>      if header :regex "Received" "^.*(13|14|15|16|17|18) (\\(.*\\) )?...
>> (\\(.*\\) )?.... (\\(.*\\) )?..:..:.. (\\(.*\\)
>> )?((\\+|\\-)[[:digit:]]{4}|.{1,5})( \\(.*\\))?$" {
>>      vacation :days 7 :addresses "user2" :subject "Out of office"
>> "IMPORTANT MESSAGE^M
>> THE MESSAGE
>> ";
>> }
>> }
>> }
>> }
>> ===============================================
>>
>> The user "User2" sent a vacation message back to the sender
>> "user at example.com" in response to this message (headers only):
>>
>> ===============================================
>> Return-path: <User at example.com>
>> Envelope-to: everyone at example.com
>> Delivery-date: Thu, 13 Nov 2014 16:08:16 +0000
>> Received: from tunis.Exampledomain.local ([192.168.254.107] helo=Tunis)
>>          by mail.example.com with esmtp (Exim 4.72)
>>          (envelope-from <User at example.com>)
>>          id 1XowwM-0007Qw-Cj
>>          for everyone at example.com; Thu, 13 Nov 2014 16:08:10 +0000
>> From: "User" <User at example.com>
>> To: "Everyone at Example" <everyone at example.com>
>> Subject: Electrician
>> Date: Thu, 13 Nov 2014 16:08:10 -0000
>> Organization: Example Consultancy
>> Message-ID: <02e601cfff5c$051ec350$0f5c49f0$@example.com>
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>>          boundary="----=_NextPart_000_02E7_01CFFF5C.051FD4C0"
>> X-Mailer: Microsoft Outlook 14.0
>> Thread-Index: Ac//W17ujWbs6KgRRsOZFc7+qT45Tg==
>> Content-Language: en-gb
>> X-Spam-Note: SpamAssassin run bypassed - sent from local address
>>
>> This is a multipart message in MIME format.
>>
>> ===============================================
>>
>> I have checked RFC 5230 section 4.5 which states:
>>
>>     "Vacation" MUST NOT respond to a message unless the recipient user's
>>     email address is in a "To", "Cc", "Bcc", "Resent-To", "Resent-Cc", or
>>     "Resent-Bcc" line of the original message.
>>
>> I cannot see the address for "user2 at example.com" in any of those fields,
>> or indeed referenced anywhere in the email. Is this a bug, or am I
>> misunderstanding something?
>>
>> Harry
>> --
>> Harry Mills                                         Tel: 01749 812100
>> Managing Director                                   Mob: 07815 848818
>> Opendium Ltd.                                       www.opendium.com
>>
>