Fri, 10 Apr 2026 15:00:41 +0000 https://bugs.horde.org/ticket/2195 mail-filter.php not work Since a few days ago,the mail-filter.php didn't work anymore, if use non-ascii string in paramater list .eg, queue ,prioriy or state in my /etc/mail/aliases Here is my /etc/mail/aliases: track_comment: "| /usr/local/apache/horde.beta/whups/scripts/mail-filter.php --queue '????' --type '??' --priority '1. ?' --state '???'" Change all non-ascII string to ascII in aliases above and mail again then it was added to whups track system successfully,however there are so many question mark in that ticket's content ,if use Chinese in the mail. David Wed, 29 Jun 2005 08:50:03 +0000 https://bugs.horde.org/ticket/2195#t9429 How should that work? I don't see any reliable way to determine the charset that was used for the cli parameters. Wed, 29 Jun 2005 12:30:29 +0000 https://bugs.horde.org/ticket/2195#t9434 > How should that work? I don't see any reliable way to determine the > charset that was used for the cli parameters. Thanks for your quick reply, jan. My another whups (Nightly Snapshots 4/17) base on Horde3.0.4 works great on this issue and i didn't provide any charset information to cli as paramaters before. so i am curious why current mail-filter.php need to determine charset ? Perhaps use charset info in mail's header is a good solution. FYI,attached these file for your reference. 1.mail.eml ,what i send to mail-filter. 2.ticket_view.gif, the screenshot explain that mail's header was not decoded correctly in whups view . P.S : From Jul 1 to 19 ,i will have my vacation in India ,so please don't close this ticket if any feedback required . Best Regards. David Thu, 30 Jun 2005 02:31:27 +0000 https://bugs.horde.org/ticket/2195#t9445 Alright, we were talking about something different. I thought the queue, state etc. name that you specify as parameters for mail-filter.php don't work. Encoded message headers work fine for me here, and I committed a fix yesterday that made encoded bodies work too. Thu, 30 Jun 2005 07:21:11 +0000 https://bugs.horde.org/ticket/2195#t9448 > Alright, we were talking about something different. I thought the > queue, state etc. name that you specify as parameters for > mail-filter.php don't work. Yes,it realy don't work. I have to use queue,state and priority name in ascii format if i want to add ticket successfully by mail-filter.php. It didn't accept queue,state and priority name in non-asc format. and this is my first problem. > > Encoded message headers work fine for me here, and I committed a fix > yesterday that made encoded bodies work too. This is another problem,message's header not encoded correctly for me here. Thu, 30 Jun 2005 07:49:36 +0000 https://bugs.horde.org/ticket/2195#t9451 For debug mail-filter.php ,i just add var_dump($queues); to line 94 and run it with paramaters ,see screenshot http://210.241.49.67/~txg16/usage.gif The result, see http://210.241.49.67/~txg16/result.gif All the queues(some of name in chinese) display in whups UI,see http://210.241.49.67/~txg16/all-queues.gif compare between result.gif & all-queues.gif,i think that is why mail-filter.php not work,but i could not find how/where to hack it. David Wed, 27 Jul 2005 07:06:48 +0000 https://bugs.horde.org/ticket/2195#t10054 This won't change, we simply don't know the charset used if running a CLI, so we can't translate non-ascii queues correctly. It might make more sense to use queue/state/etc IDs instead. Wed, 27 Jul 2005 12:15:03 +0000 https://bugs.horde.org/ticket/2195#t10063 > This won't change, we simply don't know the charset used if running a > CLI, so we can't translate non-ascii queues correctly. > > It might make more sense to use queue/state/etc IDs instead. Hi,Jan Are you means using such usage below instead ? # ./mail-filter.php --queue 1 --type 2 --priority 3 --state 1 If true,that seems not worked for me, or can you make an example here ? thank you. David Thu, 28 Jul 2005 00:47:14 +0000 https://bugs.horde.org/ticket/2195#t10090 >> This won't change, we simply don't know the charset used if running a >> CLI, so we can't translate non-ascii queues correctly. >> >> It might make more sense to use queue/state/etc IDs instead. > Hi,Jan > Are you means using such usage below instead ? > # ./mail-filter.php --queue 1 --type 2 --priority 3 --state 1 Yes. > If true,that seems not worked for me, or can you make an example here > ? thank you. Of course it doesn't work, because the script expects the queue *names* at the moment. The script should be changed to expect IDs instead. Thu, 28 Jul 2005 07:46:10 +0000 https://bugs.horde.org/ticket/2195#t10093 >>> This won't change, we simply don't know the charset used if running a >>> CLI, so we can't translate non-ascii queues correctly. >>> >>> It might make more sense to use queue/state/etc IDs instead. >> Hi,Jan >> Are you means using such usage below instead ? >> # ./mail-filter.php --queue 1 --type 2 --priority 3 --state 1 > > Yes. > >> If true,that seems not worked for me, or can you make an example here >> ? thank you. > > Of course it doesn't work, because the script expects the queue > *names* at the moment. The script should be changed to expect IDs > instead. Will horde term patch it recently ? because this ticket mark to resolved. David Thu, 28 Jul 2005 08:51:05 +0000 https://bugs.horde.org/ticket/2195#t10098 No. But this doesn't belong anymore to this ticket. You can create a new enhancement ticket to change mail-filter.php's parameters, if you want. Thu, 28 Jul 2005 09:44:20 +0000 https://bugs.horde.org/ticket/2195#t10099