Displaying 20 results from an estimated 3000 matches similar to: "Bug] Sieve vacation :addresses match only,>, case-sensitive?"
2019 Sep 11
5
[Bug] Sieve vacation :addresses match only,> case-sensitive?
> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24
i would also plea for making it case-insensitive again! We were hit by this too,
and I never saw any mail system in which the local Part ist Case sensitive!
Sincerly,
Klaus Steinberger
--
Rechnerbetriebsgruppe / IT, Fakult?t f?r Physik
Klaus Steinberger
FAX: +49 89 28914280
Tel: +49 89 28914287
--------------
2019 Sep 11
0
[Bug] Sieve vacation :addresses match only,> case-sensitive?
On Wed, Sep 11, 2019 at 09:25:54PM +0200, Klaus Steinberger via dovecot wrote:
> > I want to have it case-insensitive again, like in Pigeonhole version 0.4.24
>
> i would also plea for making it case-insensitive again! We were hit by this too,
> and I never saw any mail system in which the local Part ist Case sensitive!
Isn't the user name in the original Unix mail system (and
2019 Sep 04
0
[Bug] Sieve vacation :addresses match only case-sensitive?
Am 02.09.19 um 15:05 schrieb Philipp Faeustlin via dovecot:
> The recipients in the vacation :addresses String list are matched
> case-sensitive.
>
> If the recipient gets a mail with wrong case, the message is discarded
> with:
> "discarding vacation response for implicitly delivered message; no known
> (envelope) recipient address found in message headers"
>
2019 Sep 04
0
[Bug] Sieve vacation :addresses match only case-sensitive?
> Le 4 sept. 2019 ? 19:37, Roger Klorese via dovecot <dovecot at dovecot.org> a ?crit :
>
>
>
> On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>>
> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24
>
2019 Sep 09
0
[Bug] Sieve vacation :addresses match only case-sensitive?
> It is not recommended to rely on local-part case, but it is indeed
> case-sensitive.
>
> And this is to avoid such issues that postfix supports address
> cleanup/canonicalisation before forwarding mails to dovecot.
>
> ----------
> RFC 5321:
>
> "Local-part ? ? = Dot-string / Quoted-string ; MAY be case-sensitive
> [?]
>
2019 Sep 11
0
Sieve vacation :addresses match only case-sensitive?
On 02/09/2019 15:05, Philipp Faeustlin via dovecot wrote:
> The recipients in the vacation :addresses String list are matched
> case-sensitive.
>
> If the recipient gets a mail with wrong case, the message is discarded
> with:
> "discarding vacation response for implicitly delivered message; no
> known (envelope) recipient address found in message headers"
>
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <
dovecot at dovecot.org>
> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24
> (5a7e9e62):
>
> In this version the additional addresses in vacation :addresses
> ["test at example.com"] are handled case-insensitive.
>
2019 Sep 09
1
[Bug] Sieve vacation :addresses match only case-sensitive?
> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote:
>
>> It is not recommended to rely on local-part case, but it is indeed
>> case-sensitive.
>> And this is to avoid such issues that postfix supports address
>> cleanup/canonicalisation before forwarding mails to dovecot.
>> ----------
>> RFC
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
>
> It is not recommended to rely on local-part case, but it is indeed
> case-sensitive.
>
> And this is to avoid such issues that postfix supports address
> cleanup/canonicalisation before forwarding mails to dovecot.
>
> ----------
> RFC 5321:
>
> "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive
> [?]
> While the above definition
2019 Sep 02
4
Sieve vacation :addresses match only case-sensitive?
The recipients in the vacation :addresses String list are matched
case-sensitive.
If the recipient gets a mail with wrong case, the message is discarded with:
"discarding vacation response for implicitly delivered message; no known
(envelope) recipient address found in message headers"
I think the matching should be case-insensitive.
Is this a bug or do I miss some option?
I'm
2007 Dec 18
1
Deliver, sendmail, virtual users, and catch-all addresses
I have spent a long time looking into this and can't find the answer
I'm looking for, so I'm asking here. I'm cutting the example down to
just the bare minimums. This is NOT my actual configuration, but is
sufficient for asking this question:
How can I use dovecot's deliver LDA to deliver to virtual users, but
then have unknown virtual users fall back to catch-all
2006 Jun 13
2
Locating an arbitrary fixture...
Is there a good way to get an arbitrary fixture from the generated
fixture function?
I need a way to get one of my fixtures, I don''t care which one. It
doesn''t need to be random and could always return the same fixture.
This is part of a support function for custom assertions and it doesn''t
know what class its working on, let alone what fixture names are
possible.
2010 Apr 01
0
[LLVMdev] AnalysisUsage: addRequired vs. addRequiredTransitive
On Fri Apr 02 00:37:03 +0200 2010, Trevor Harmon wrote:
> On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote:
> > Others, like MemoryDependenceAnalysis, are "lazy." MDA
> > specifically does NOT compute results in its runOnFunction(),
> > instead computing results on-demand when a user queries it. Because
> > MDA depends on AA, we must ensure that, as long as
2010 Nov 10
0
Problem with case statement and mb_chars in Ruby-1.9.2
RoR-3.0.1
I have this case statement:
case n.hll_normalize
when "common name"
@my_correspondent.correspondent_common_name = s
when "legal name"
. . .
else
raise ArgumentError, "#{n} attribute is not provided for."
end
hll_normalize is defined as:
def hll_normalise
strip.squeeze(" ").mb_chars.downcase
end
I
2007 Aug 15
0
mda and kmeans
Hello,
I am using the function mda of the mda library in order to discriminate
4 groups with 8 explanatory variables. I only have 66 observations.
I tested all possible combinations of those variable and run for each
the Mixture Discriminant Analysis.
For some iterations, I got an error message: "error in kmeans(xx,
start): initial centers are not distinct".
I understood that the
2006 Jan 09
3
Pagination :conditions not working - MySQL v. PostgreSQL, Rails abstraction v. embedded SQL
Hi everyone,
I have this code:
@person_pages, @people = paginate :person, :per_page => 20,
:conditions => [ "username LIKE ? OR first_name LIKE ? OR
last_name LIKE ? OR preferred_name LIKE ?",
"%" + params[:q].downcase + "%",
"%" + params[:q].downcase + "%",
2020 May 17
3
Problems with userdb and mail deliveribility
I briefly got some mails delivered, but not anymore.
Attached are dovecot-info.log, dovecot-debug.log,
dovecot.log, maillog, /etc/mail/passwd
smtpd.conf, vaddr, vusers, vdomains
Thanks for any help.
Chris Bennett
-------------- next part --------------
May 15 12:54:25 master: Error: service(config): pipe() failed: Too many open files
May 15 12:54:25 master: Error: service(auth): pipe() failed:
2009 Aug 28
0
string downcase or how to use downcase an hostname in puppet?
Hi there.
I am trying to fix hostnames in our Redhat distributions.
Some of our server has some hostname un uppercase, and I need to change them
into lowercase because people that use the server rather like lowercase
hostnames...
I did some basic work :
Template :
$ cat /var/puppet/templates/rh-network.erb
# WARNING this file is autogenered by puppet. Any change there will
# be
2014 Nov 26
1
mail_location maildir:~/Maildir Invalid user settings[SOLVED]
Hallo list,
I was having quite a hard time configuring dovecot on OpenBSD -current.
The problem was default Maildir setting in 10-mail.conf, namely:
mail_location maildir:~/Maildir
was unable to locate user's home directory.
As far as I can remember, it was the correct setting on
OpenBSD-current a week or two ago.
Once I figured out and changed it to
mail_location
2010 Apr 01
2
[LLVMdev] AnalysisUsage: addRequired vs. addRequiredTransitive
On Mar 31, 2010, at 3:13 PM, Owen Anderson wrote:
> Some analyses, like Andersen's AA, do all their computation in their
> runOnFunction(). Therefore, anything they depended on can be
> destroyed after the runOnFunction() returns.
What about AA itself? Would addRequired<AliasAnalysis> keep
AliasAnalysis alive (but allow AliasAnalysis's dependencies to die)?
>