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 PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Sent: Tuesday, February 24, 2004 9:47 AM To: [email protected] Subject: [Dbmail] CAP domain results in "no such user" mail bounce I noticed that when dbmail checks for a delivery point, if the domain name does not match one listed in the aliases table case for case, it will bounced the mail with "so such user". Has this comparison always been case sensitive? For example, if [EMAIL PROTECTED] is in the aliases table and then I get a mail address to [EMAIL PROTECTED], dbmail rejects it. Actually it will reject anything not spelled exactly as "example.com". This is the error message generated. dbmail/smtp[31935]: bounce.c,bounce: sending 'no such user' bounce for destination [EMAIL PROTECTED] Is this a postfix problem, PostgreSQL problem, or a dbmail problem? __________________________________ Do you Yahoo!? Yahoo! Mail SpamGuard - Read only the mail you want. http://antispam.yahoo.com/tools _______________________________________________ Dbmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
