Just to say that this is also a problem for us. Our email addresses are case insensitive, and I can be mailed as [EMAIL PROTECTED] or [EMAIL PROTECTED] or any other combination. Users complain about having to put their mail address into the vacation facility at all - and are not at all happy about having to put in all likely combinations of upper and lower case.
In fact, even when the local part of addresses is case sensitive, I think it would be better to do a case insensitive match for purposes of deciding eligibility for a vacation message. After all, if the message is delivered (so the envelope recipient address is correct) and has a to/cc/bcc header that satisfies a case-insensitive match, under what circumstances could it be wrong to send a vacation message? If that is not agreed, perhaps there could be a configuration option for the vacation facility to do a case-insensitive match? John. At 14:43 14/01/02, Olaf Dreyer wrote: >Hello, > >i am still fighting with vacation. As far as i understand the source >code, and what i read in the archives, the envelope address and the >strings in the :addresses field are compared to To, Cc and Bcc fields. >If they match, a vacation message may be sent. >My sendmail configuration, which is derived from cyrusv2.mc, sets the >recipient to lower case, and leaves the To/Cc/Bcc fields as provided by >the sender. This behaviour is ok, as i want cyrus to store mails for >Olaf.Dreyer and olaf.dreyer or even olaf.Dreyer in the same inbox. >With sieve/vacation i really have to provide all possible variants? >I think this would make vacation too difficult to use. > >TIA >Olaf Dreyer
