[Kolab-devel] Wallace issue?

On Sunday, October 06, 2013 05:21:46 PM Thomas Spuhler wrote:
> On Friday, October 04, 2013 04:45:20 PM Thomas Spuhler wrote:
> > On Friday, October 04, 2013 09:07:40 AM Thomas Spuhler wrote:
> > > On Thursday, October 03, 2013 06:17:32 PM you wrote:
> > > >   When I last tried any of those patches, they did not work for me.  If I remember correctly
> > > >   the
> > > > 
> > > > reason was I am running 3.1 and they were made for 3.0. Has anyone else tried them on 3.1?
> > > > 
> > > > Brian
> > > > 
> > > > Sent from my ASUS Pad
> > > > 
> > > > Thomas Spuhler <[email protected]> wrote:
> > > > > On Thursday, October 03, 2013 09:18:05 PM James Mills wrote:
> > > > > 
> > > > > Oh good! It seems to work for me too!
> > > > > Not if I can get reports that this solves the "Wallce Issue"
> > > > > from other users we can finally put this Issue to bed :)
> > > > > 
> > > > > 
> > > > > cheers
> > > > > James
> > > > > 
> > > > > 
> > > > > 
> > > > > James Mills / prologic
> > > > > 
> > > > > E: [email protected]
> > > > > W: prologic.shortcircuit.net.au
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On Thu, Oct 3, 2013 at 9:00 PM, Antonio Straziota
> > > > > <[email protected]> wrote:
> > > > > 
> > > > > Hi James,
> > > > > seems that your patch has solved my problem.
> > > > > 
> > > > > 
> > > > > 
> > > > > Thanks for help.
> > > > > 
> > > > > Antonio.
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 2013/10/3 James Mills <[email protected]>
> > > > > 
> > > > > The last patch in Issue #1627 (which I wrote) works for me (tm)
> > > > > but I've seen reports of issues with this patch by other users.
> > > > > 
> > > > > 
> > > > > Give it a try and let me know?
> > > > > 
> > > > > 
> > > > > cheers
> > > > > James
> > > > > 
> > > > > 
> > > > > 
> > > > > James Mills / prologic
> > > > > 
> > > > > E: [email protected]
> > > > > W: prologic.shortcircuit.net.au
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > On Thu, Oct 3, 2013 at 1:43 AM, Antonio Straziota
> > > > > <[email protected]> wrote:
> > > > > 
> > > > > Hi all,
> > > > > I found some email in deferred status after the come in wallace:
> > > > > 
> > > > > 
> > > > > Oct  2 17:34:23 mail postfix/smtp[4028]: 42A0913ED:
> > > > > to=<[email protected]>,
> > > > > relay=127.0.0.1[127.0.0.1]:10026, delay=1172, delays=1172/0.02/0/0,
> > > > > dsn=4.4.2, status=deferred (lost
> > > > > connection with 127.0.0.1[127.0.0.1] while sending end of data --
> > > > > message may be sent more than
> > > > > once)
> > > > > 
> > > > > 
> > > > > Looking at the mailing list I found other people having the same problem.
> > > > > In details:
> > > > > https://issues.kolab.org/show_bug.cgi?id=1627
> > > > > 
> > > > > https://issues.kolab.org/show_bug.cgi?id=1884
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > 
> > > > > Seems that once a mail end in this state, the following ones stay in
> > > > > the same state: deferred.
> > > > > I have this problem only on external mail.
> > > > > Infact, the same mail (subject and text) from an internal mailbox
> > > > > doesn't have problem.
> > > > > 
> > > > > 
> > > > > Error log from wallace is:
> > > > > 
> > > > > 
> > > > > 2013-10-02 17:24:23,267 pykolab.wallace INFO Accepted connection
> > > > > error: uncaptured python exception, closing channel <smtpd.SMTPChannel
> > > > > connected 127.0.0.1:40769 at
> > > > > 0x1cc8c68> (<type 'exceptions.TypeError'>:must be string or buffer, not list
> > > > > [/usr/lib/python2.7/asyncore.py|read|83]
> > > > > [/usr/lib/python2.7/asyncore.py|handle_read_event|449]
> > > > > [/usr/lib/python2.7/asynchat.py|handle_read|158]
> > > > > [/usr/lib/python2.7/smtpd.py|found_terminator|181]
> > > > > [/usr/lib/python2.7/dist-packages/wallace/__init__.py|process_message|259]
> > > > > [/usr/lib/python2.7/email/message.py|set_charset|270]
> > > > > [/usr/lib/python2.7/email/charset.py|
> > > > > body_encode|393] [/usr/lib/python2.7/email/base64mime.py|encode|147])
> > > > > 2013-10-02 17:28:14,055 pykolab.wallace INFO Accepted connection
> > > > > 
> > > > > 
> > > > > I found also some patch on the first link, but I don't understand
> > > > > which of them should be applied and
> > > > > where.
> > > > > Can you give some tips?
> > > > > 
> > > > > 
> > > > > Thanks,
> > > > > Antonio.
> > > > > 
> > > > > 
> > > > > After applying the patch I get:
> > > > > 
> > > > > # systemctl status wallace
> > > > > wallace.service - Wallace Content Filter
> > > > > 
> > > > >           Loaded: loaded (/usr/lib/systemd/system/wallace.service; enabled)
> > > > > 
> > > > > Active: active (running) since Thu, 2013-10-03 09:49:36 MST; 10s ago
> > > > > Process: 26625 ExecStop=/bin/kill -TERM $MAINPID (code=exited,
> > > > > status=0/SUCCESS)
> > > > > Process: 26628 ExecStart=/usr/sbin/wallaced $FLAGS (code=exited,
> > > > > status=0/SUCCESS)
> > > > > 
> > > > >         Main PID: 26634 (wallaced)
> > > > >         
> > > > >           CGroup: name=systemd:/system/wallace.service
> > > > > 
> > > > > ├ 26634 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26747 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26748 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26749 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26750 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26751 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26753 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26754 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26755 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26756 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26757 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26758 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26759 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26760 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26761 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26762 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26763 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26765 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26766 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26767 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26768 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > ├ 26769 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > └ 26770 /usr/bin/python /usr/sbin/wallaced --fork -l warning
> > > > > 
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: File
> > > > > "/usr/lib64/python2.7/multiprocessing/queues.py", line 374, in get
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: racquire()
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: OSError: [Errno
> > > > > 2] No such file or directory
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: racquire()
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: OSError: [Errno
> > > > > 2] No such file or directory
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: racquire()
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: OSError: [Errno
> > > > > 2] No such file or directory
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: racquire()
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: OSError: [Errno
> > > > > 2] No such file or directory
> > > > > Oct 03 09:49:36 aargau.btspuhler.com wallaced[25756]: OSError: [Errno
> > > > > 2] No such file or directory
> > > > > Oct 03 09:49:36 aargau.btspuhler.com systemd[1]: Started Wallace
> > > > > Content Filter.
> > > > > 
> > > > > I am using pykolab-0.5.12
> > > 
> > > It didn't solve all of my problems. I still have about 20% of the messages from  dev-
> > > [email protected] getting stuck.
> > > 
> > > I see in the log file:
> > > wallaced[8359]: error: uncaptured python exception, closing channel <smtpd.SMTPChannel
> > > connected
> > > 127.0.0.1:44000 at 0x2486560> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't
> > > decode
> > > byte 0xe9 in position 3323: invalid continuation byte
> > > [/usr/lib64/python2.7/asyncore.py|read|83]
> > > [/usr/lib64/python2.7/asyncore.py|handle_read_event|449] [/usr/lib64/python2.7/asynchat.py|
> > > handle_read|158] [/usr/lib64/python2.7/smtpd.py|found_terminator|181]
> > > [/usr/lib/python2.7/site-
> > > packages/wallace/__init__.py|process_message|272]
> > > [/usr/lib64/python2.7/json/__init__.py|dumps|250]
> > > [/usr/lib64/python2.7/json/encoder.py|encode|209]
> > > [/usr/lib64/python2.7/json/encoder.py|_iterencode| 434]
> > > [/usr/lib64/python2.7/json/encoder.py|_iterencode_dict|390])
> > 
> > I hate to be the bearer of bad news.
> > I just applied your patch in Mageia Cauldron (development version). It has pykolab-0.5.14 and
> > all
> > the newest python package (using python-2.7).
> > I have setup two accounts and sent messages from one to the other.
> > Messages with normal ascii character go through, but if I add Umlauts (using the
> > US-International
> > keyboard mapping to create the umlauts) it get's stuck with the same errors as listed above.
> > 
> > There are other issues, but let's tackle this first.
> 
> Well, the good news is, (after a few days of running it)  the e-mails stuck don't block other e-
> mails that do not have the problem.

This tread has been very quiet. Has anybody made any progress of getting e-mails with Umlauts 
through Wallace?

I am going to cc the devel list. Maybe something happened I don't know.

-- 
Best regards
Thomas Spuhler

_______________________________________________
devel mailing list
[email protected]
https://lists.kolab.org/mailman/listinfo/devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEABECAAYFAlJe4iUACgkQjsMgV2ARTmNEpACfTgdO5seQE27D7x3gcqhL7CFZ
3tIAnibaxzabz+PDONTRO+538d/KEbVF
=M4Sg
-----END PGP SIGNATURE-----