Displaying 3 results from an estimated 3 matches for "uesr1".
Did you mean:
esr1
2020 Jul 20
2
To field was not correct indexed by FTS
...at example.com <user3 at example.com> , user4 desu <user4 at example.com>
Any hint?
--
TACHIBANA Masashi QUALITIA CO., LTD.
mailto:tachibana at qualitia.co.jp
??????????
https://www.qualitia.co.jp/
-------------- next part --------------
An embedded message was scrubbed...
From: uesr1 <user1 at example.com>
Subject: aaabbbccc123
Date: no date
Size: 346
URL: <https://dovecot.org/pipermail/dovecot/attachments/20200720/2759288f/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: uesr1 <user1 at example.com>
Subject: aa...
2020 Jul 20
0
To field was not correct indexed by FTS
...en);
194 message_address_write(str, addr);
195
196 i_debug("@@@@@ after address parse:%s",str_data(str));
Mail addresses were deleted when passed message_address_parse().
So this debug logs came like following:
Debug: @@@@@ befor address parse:uesr1 <user1 at example.com>
Debug: @@@@@ after address parse:uesr1 <user1 at example.com>
Debug: @@@@@ data:uesr1 <user1 at example.com>
Debug: @@@@@ befor address parse:Yamada Taro <yamada at example.com>,user2 at example.com <user2 at example.com>, user3 at example.com &l...
2020 Jul 20
2
To field was not correct indexed by FTS
...e_address_write(str, addr);
> 195
> 196 i_debug("@@@@@ after address parse:%s",str_data(str));
>
> Mail addresses were deleted when passed message_address_parse().
> So this debug logs came like following:
>
> Debug: @@@@@ befor address parse:uesr1 <user1 at example.com>
> Debug: @@@@@ after address parse:uesr1 <user1 at example.com>
> Debug: @@@@@ data:uesr1 <user1 at example.com>
> Debug: @@@@@ befor address parse:Yamada Taro <yamada at example.com>,user2 at example.com <user2 at example.com>, user3 at...