Re: [Kolab-devel] wallace woes, kolab-3.0

Henning <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <[email protected]>
As a side-note: Inbound AND outbound mail got stuck, but not all.

Am 02.02.2014 11:35, schrieb Henning:
> Hi,
> 
> I ran into this problem too. I disabled wallace in master.cf an requeued
> stuck mail via
> 
> ~$ sudo postsuper -r ALL
> 
> to solve this. I have kolab 3.1 installed on Ubuntu. Would you have a
> look at it?
> 
> Henning
> 
> On Thursday, November 21, 2013 05:23:47 PM Thomas Spuhler wrote:
>> On Thursday, November 21, 2013 04:16:06 PM Geoff Nordli wrote:
>>> On 13-11-21 02:28 PM, Thomas Spuhler wrote:
>>>> On Thursday, November 21, 2013 11:26:35 AM Thomas Spuhler wrote:
>>>>> Does anybody know how to disable mail being routed through wallace?
>>>>> I have commented out everything I can find in relation to
> wallace, but still get this:
>>>>>
>>>>> (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 id=03681-05 -
> Temporary MTA failure on relaying,
>>>>> from
>>>>> MTA(smtp:[127.0.0.1]:10026): No resp. to data-dot (in reply to
> end of DATA command)
>>>>>
>>>>> I restarted postfix after making the changes in master.cf and
> resent the e-mail
>>>>> (yes, in this case, it's an outgoing e-mail.)
>>>>
>>>> I may got a reply to this, but it got stuck in wallace?
>>>
>>> Yes, it stays in there (I had the same probably you did a few days ago).
>>>
>>> Try this:
>>>
>>> run postqueue to get a list of the messages and their IDs:
>>>
>>> postqueue -p
>>>
>>> then try requeuing it with the:
>>>
>>> postsuper -r message_id
>>>
>>> Geoff
>>>
>>>
>>> _______________________________________________
>>> users mailing list
>>> users <at> lists.kolab.org
>>> https://lists.kolab.org/mailman/listinfo/users
>>
>> Thanks Geoff:
>> I tried this already.
>> The questions is actually, why does it still get into wallace?
> 
>> I just found an error log about it. I am going to add the dev list:
>>
>> Nov 21 17:45:12 aargau.btspuhler.com wallaced[18598]: error:
>> uncaptured python exception, closing
>> channel <smtpd.SMTPChannel connected 127.0.0.1:52259 at 0x1676368> >(<type
>> 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte 0x96
>> in position 3308: invalid start
>> 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|271]
>> [/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])
>>
>> --
>> Thomas Spuhler
> _______________________________________________
> devel mailing list
> [email protected]
> https://lists.kolab.org/mailman/listinfo/devel
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.