Hi,
Thanks for the help. I tried that but the SQL query isn't returning the correct
data.
mysql> select mail_host_map,mail_username,143 from access_maps where
mail_host_map='cami(a)24.com'
Empty set (0.51 sec)
mysql> desc access_maps;
+---------------+----------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+---------------+----------+------+-----+---------+-------+
| mail_username | char(60) | NO | PRI | | |
| mail_host_map | char(60) | NO | | | |
| loginid | char(32) | NO | MUL | NULL | |
+---------------+----------+------+-----+---------+-------+
3 rows in set (0.00 sec)
mysql> select * from access_maps where mail_username = "cami(a)24.com".com";
+---------------+-------------------------------------------------+----------------------------------+
| mail_username | mail_host_map | loginid |
+---------------+-------------------------------------------------+----------------------------------+
| cami(a)24.com | f2ef77fe86754109b347dd97a79444eb(a)152.111.194.93 |
f2ef77fe86754109b347dd97a79444eb |
+---------------+-------------------------------------------------+----------------------------------+
1 row in set (0.00 sec)
IMAP4_FLAGS="-l 143 -M /usr/lib64/libperditiondb_mysql.so.0.0.0 -m
152.111.194.116:3306:MAIL:access_maps:postfix:XXX:mail_host_map:mail_username:143
-d"
Any other ideas? Is there any way to debug what Perdition is doing when it receives data
from SQL?
Cami
From: uk(a)newstyledata.net
Sent:2010-08-13 17:13:16
To: perdition-users(a)vergenet.net
Cc:
Subject: Re: [PERDITION-USERS] upgrading from perdition-1.15 toperdition-1.18
Hi,
Seems you have the map_library_opt option in the wrong order, just
switch mail_username and mail_host_map and it should work again.
[:[:[:[:[:[:[:[:]]]]]]]]
greetings
JS
On 2010-08-13 16:21, cami(a)mweb.co.za wrote:
Hi All,
I've been trying to upgrade from perdition 1.15 to perdition 1.18
without any luck.
The behaviour is different with regards to MySQL data which are returned.
The query:
select mail_username,mail_host_map,143 from access_maps where
mail_username='cami(a)24.com'com';
+---------------+-------------------------------------------------+-----+
| mail_username | mail_host_map | 143 |
+---------------+-------------------------------------------------+-----+
| cami(a)24.com | f2ef77fe86754109b347dd97a79444eb(a)152.111.194.93 | 143 |
+---------------+-------------------------------------------------+-----+
In 1.15 "f2ef77fe86754109b347dd97a79444eb" is correctly returned as seen
here:
Aug 13 16:18:25 mailstore01 imapd: LOGIN: DEBUG: ip=[::ffff:127.0.0.1],
command=LOGIN
Aug 13 16:18:25 mailstore01 imapd: LOGIN: DEBUG: ip=[::ffff:127.0.0.1],
username=f2ef77fe86754109b347dd97a79444eb
Aug 13 16:18:25 mailstore01 imapd: LOGIN: DEBUG: ip=[::ffff:127.0.0.1],
password=XXXX
Aug 13 16:18:25 mailstore01 imapd: authdaemon: starting client module
Aug 13 16:18:25 mailstore01 imapd: authdaemon: ACCEPT, username
f2ef77fe86754109b347dd97a79444eb
Aug 13 16:18:25 mailstore01 imapd: LOGIN,
user=f2ef77fe86754109b347dd97a79444eb, ip=[::ffff:127.0.0.1], protocol=IMAP
(the imap server being used is Courier)
In 1.18 "cami(a)24.com" is being returned and passed onto Courier instead
of "f2ef77fe86754109b347dd97a79444eb"
Aug 13 15:07:15 mailstore01 imapd: LOGIN: DEBUG:
ip=[::ffff:152.111.194.109], command=LOGIN
Aug 13 15:07:15 mailstore01 imapd: LOGIN: DEBUG:
ip=[::ffff:152.111.194.109], username=cami(a)24.com
Aug 13 15:07:15 mailstore01 imapd: LOGIN: DEBUG:
ip=[::ffff:152.111.194.109], password=XXXX
Aug 13 15:07:15 mailstore01 imapd: authdaemon: starting client module
Aug 13 15:07:15 mailstore01 imapd: authdaemon: REJECT
Can anyone tell me how to revert back to the old behaviour to how to go
about trouble shooting this?
Regards,
Cami
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users
______________________________________________
Perdition-users mailing list
Perdition-users(a)vergenet.net
http://lists.vergenet.net/listinfo/perdition-users