TED] Behalf
> Of Curtis Maurand
> Sent: Thursday, March 04, 2004 10:17 PM
> To: dbmail@dbmail.org
> Subject: RE: [Dbmail] CAP domain results in "no such user" mail bounce
>
>
>
> I'm not taking anything personally. I think that this is a good
> and important di
Well,. This test was done on mysql 3.23.49, so dono :)
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ilja Booij
Sent: Friday, March 05, 2004 7:56 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounc
[mailto:[EMAIL PROTECTED] On Behalf
Of Ilja Booij
Sent: Thursday, March 04, 2004 10:11 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
Hi
John Hansen wrote:
Ok,...
In mysql you only need an index on column. It does not need an index
on
never espoused those solutions since they have
> the same problems as yours does regarding the points I'm trying to address.
>
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> > Of Curtis Maurand
> > Sent: Thu
; John
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Ilja Booij
> Sent: Thursday, March 04, 2004 1:32 AM
> To: dbmail@dbmail.org
> Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
>
> Just
True. But totally irrelevent to the discussion. Making MySQL
> treat domain
> > names as case-sensitive doesn't help when domain names are
> case-insensitive.
> >
> > > -Original Message-
> > > From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED
Thursday, March 04, 2004 9:40 AM
> > To: dbmail@dbmail.org
> > Subject: RE: [Dbmail] CAP domain results in "no such user" mail bounce
> >
> >
> >
> > if you want MySQL to be case sensitive:
> >
> > create table tablename (
> > name
March 04, 2004 9:40 AM
> To: dbmail@dbmail.org
> Subject: RE: [Dbmail] CAP domain results in "no such user" mail bounce
>
>
>
> if you want MySQL to be case sensitive:
>
> create table tablename (
> name varchar(120) binary,
> ...,
> );
>
> C
e the
> insert/update came from.
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf
> > Of Ilja Booij
> > Sent: Wednesday, March 03, 2004 9:58 AM
> > To: dbmail@dbmail.org
> > Subject: Re: [Dbmail] CAP domain results in &quo
o: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
Just when I was ready to commit the changes, I found out that MySQL
cannot have an index like:
INDEX (lower(alias)), because it cannot have expressions in an index..
So, the whole plan is a no-
gt; To: dbmail@dbmail.org
> Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
>
>
> The solution I can think of now is the following:
>
> make sure all aliases (or at least their domain part) go into the
> database in lowercase. Whenever we check
work,. But dono how to do that in
mysql.
Regards,
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ilja Booij
Sent: Thursday, March 04, 2004 1:32 AM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
gt;>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>>> Behalf Of Ilja Booij
>>> Sent: Wednesday, March 03, 2004 11:30 PM
>>> To: dbmail@dbmail.org
>>> Subject: Re: [Dbmail] CAP domain results in "no such user" mail
>>> bounce
>
That cast method is not valid in postgresql however
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Magnus Sundberg
Sent: Thursday, March 04, 2004 12:17 AM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bo
so work with characters other than A-Z?
> >
> > Ilja
> >
> >
> >>>
> >>> -Original Message-----
> >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf
> >>> Of Ilja Booij
> >>> Sent: Wednesday, March 0
An option could be added to dbmail-maintenance to fix any uppercase aliases.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Ilja Booij
Sent: Wednesday, March 03, 2004 6:58 AM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such
On Wednesday 03 March 2004 09:32 am, Ilja Booij wrote:
> Just when I was ready to commit the changes, I found out that MySQL
> cannot have an index like:
>
> INDEX (lower(alias)), because it cannot have expressions in an index..
>
> So, the whole plan is a no-go. Unless we can come up with some oth
On Wednesday 03 March 2004 09:57 am, Ilja Booij wrote:
> The solution I can think of now is the following:
>
> make sure all aliases (or at least their domain part) go into the
> database in lowercase. Whenever we check a domain alias, we first
> convert the domain string to lowercase. We can then
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
well, after some more reading, I guess it's a bit different:
IMAP RFC3501 takes no position on case sensitivity in mailbox names. So,
we can support either case sensitive or case insensitive mailbox
names. Currently
x27;ism, you should put code in the software to do the
> >>comparison, not in the SQL, mysql is not case sensitive,. So on mysql
> >>dbmail would not conform to the RFC in this case.
> >>
> >>... John
> >>
> >>-Original Message-
&g
Behalf
Of Ilja Booij
Sent: Wednesday, March 03, 2004 11:30 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
well, after some more reading, I guess it's a bit different:
IMAP RFC3501 takes no position on case sensitivity in mailbox na
ick.
... John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ilja Booij
Sent: Wednesday, March 03, 2004 8:47 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
We can't use ILIKE, as it
Ilja Booij wrote:
well, after some more reading, I guess it's a bit different:
IMAP RFC3501 takes no position on case sensitivity in mailbox names. So,
we can support either case sensitive or case insensitive mailbox names.
Currently, mailboxes are case sensitive when using PostgreSQL, and cas
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Ilja Booij
> Sent: Wednesday, March 03, 2004 10:05 PM
> To: dbmail@dbmail.org
> Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
>
> In DBMail
("value%")
>
> should do the trick.
>
> ... John
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Ilja Booij
> Sent: Wednesday, March 03, 2004 8:47 PM
> To: dbmail@dbmail.org
> Subject: Re: [Dbmail] CAP domain
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ilja Booij
Sent: Wednesday, March 03, 2004 11:30 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
well, after some more reading, I guess it's a bit different
Ilja Booij
Sent: Wednesday, March 03, 2004 11:30 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
well, after some more reading, I guess it's a bit different:
IMAP RFC3501 takes no position on case sensitivity in mailbox names. So,
e-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Ilja Booij
Sent: Wednesday, March 03, 2004 8:47 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
We can't use ILIKE, as it's not supported by MySQL. It'
Behalf
Of Ilja Booij
Sent: Wednesday, March 03, 2004 10:05 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
In DBMail 1.2.3 the queries were all defined in the backend driver. In
DBMail 2.0, the backend driver has become much smaller a
CTED] On Behalf
Of Ilja Booij
Sent: Wednesday, March 03, 2004 8:47 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
We can't use ILIKE, as it's not supported by MySQL. It's also not a part
of SQL92, is it? I'll look for a wa
] On Behalf
Of Ilja Booij
Sent: Wednesday, March 03, 2004 8:47 PM
To: dbmail@dbmail.org
Subject: Re: [Dbmail] CAP domain results in "no such user" mail bounce
We can't use ILIKE, as it's not supported by MySQL. It's also not a part
of SQL92, is it? I'll look for a way around
We can't use ILIKE, as it's not supported by MySQL. It's also not a part
of SQL92, is it? I'll look for a way around this.
Ilja
John Hansen wrote:
Probably a bug from being ported to postgres, as mysql is not case
sensitive, but postgresql is.
As such, all comparisons in where clauses should
Probably a bug from being ported to postgres, as mysql is not case
sensitive, but postgresql is.
As such, all comparisons in where clauses should be cast using lower()
on both sides of the comparison sign. Or in the case of LIKE, use ILIKE.
Regards,
John
-Original Message-
From: [EMAIL
33 matches
Mail list logo
