Wallace and character encoding

[Bruckbauer, Markus]

hi

that's not ok for debian, if you Replace: -o 
content_filter=smtp-wallace:[127.0.0.1]:10026
With: -o content_filter=

i can't recieve Mail's
ERROR: Jun  4 17:38:24 ares postfix/smtp[25793]: D85F854838: 
to=<markus.bruckbauer at bm-it.at>, relay=127.0.0.1[127.0.0.1]:10024, 
delay=7.8, delays=4.2/0/0.07/3.4, dsn=4.5.0, status=deferred (host 
127.0.0.1[127.0.0.1] said: 451 4.5.0 id=08511-04 - Temporary MTA failure 
on relaying, From MTA() during fwd-connect (Negative greeting:  at (eval 
109) line 479.): id=08511-04 (in reply to end of DATA command))

Markus


Am 03.06.2013 23:15, schrieb Mat Cantin:
> I came across this problem too. Since I don't use any of the Wallace
> features I just disabled it in the master.cf config.
> 
> Replace: -o content_filter=smtp-wallace:[127.0.0.1]:10026
> With: -o content_filter=
> 
> No more mail getting stuck.
> 
> --
> Mat
> 
> 
> On 2013-05-30 5:23, Troy Carpenter wrote:
>> There are two active bugs that I know of.  The first one sounds
>> mostly like what you report:
>> https://issues.kolab.org/show_bug.cgi?id=1627
>> https://issues.kolab.org/show_bug.cgi?id=1884
>> 
>> I don't have an answer for you.  I've started checking my mailq on a
>> regular basis throughout the day.  In fact, this morning I had 79
>> messages stuck.  Right now the only way I've found to fix the problem
>> is to reboot my mail server.  Fortunately, that doesn't take very
>> long.
>> 
>> As for the email stuck in the wallace queue, someone earlier said
>> they had a python script to re-inject the emails stuck there, but I
>> didn't see the script.
>> 
>> On Thursday, May 30, 2013 09:54:17 AM Tobias Brunner wrote:
>>> Hi everyone,
>>> 
>>> I see that there are several problems reported regarding Wallace
>>> crashing because of character conversion problems. The bug hit me,
>>> too... Wallace stops accepting mails and they stay stuck in the
>>> Postfix
>>> queue. I'm not sure if this bug could be fixed already, is it? The
>>> version of Wallace installed on my Debian server is 0.5.12-1.
>>> 
>>> The error I get is:
>>> error: uncaptured python exception, closing channel
>>> <smtpd.SMTPChannel
>>> connected 127.0.0.1:56975 at 0x1e27488> (<type
>>> 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0xdf
>>> in
>>> position 4108: invalid continuation byte
>>> [/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|263]
>>> [/usr/lib/python2.7/json/__init__.py|dumps|238]
>>> [/usr/lib/python2.7/json/encoder.py|encode|202]
>>> [/usr/lib/python2.7/json/encoder.py|_iterencode|427]
>>> [/usr/lib/python2.7/json/encoder.py|_iterencode_dict|383])
>>> 
>>> After restarting Wallace, connections are accepted again and mails
>>> are
>>> delivered. But there are many mails stuck in
>>> '/var/spool/pykolab/wallace/resources/incoming'. How can I resend
>>> this
>>> mails?
>>> 
>>> Any idea what could be done to have Wallace stable again? I don't
>>> want
>>> to disable Wallace.
>>> 
>>> Thanks for any help!
>>> 
>>> Cheers,
>>> Tobias
>>> 
>>> _______________________________________________
>>> Kolab-users mailing list
>>> Kolab-users at kolab.org
>>> https://www.intevation.de/mailman/listinfo/kolab-users
>> 
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://www.intevation.de/mailman/listinfo/kolab-users
> 
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://www.intevation.de/mailman/listinfo/kolab-users