postfix email deferred and stuck message

[Geoff Nordli]

On 13-11-17 09:26 AM, Thomas Spuhler wrote:
> On Saturday, November 16, 2013 06:28:55 PM Geoff Nordli wrote:
>> On 13-11-15 01:23 PM, Geoff Nordli wrote:
>>> I am running Kolab Enterprise on Centos 6.4
>>>
>>> Postfix was unable to deliver email.  I had to restart the server in
>>> order to fix the problem.  I am not even sure where to look the next
>>> time this comes up.  Nothing was in amavisd, messages, maillog, kolab
>>> logs.  When I did a search, someone said restarting it fixed the
>>> problem, but that doesn't actually fix it.
>>>
>>> 00:39:05 ma-mail1 postfix/smtp[32355]: 6CB0D2B45A: to=<user at gnaa.net>,
>>> relay=127.0.0.1[127.0.0.1]:10026, delay=23913,
>>> delays=23613/0.02/300/0, dsn=4.4.2, status=deferred (conversation with
>>> 127.0.0.1[127.0.0.1] timed out while receiving the initial server
>>> greeting)
>>>
>>> Not sure if this is related, but I have an email stuck in the queue as
>>> well.
>>>
>>> F3468286AD  3491946 Tue Nov 12 09:38:50  user1 at domain.com
>>> (lost connection with 127.0.0.1[127.0.0.1] while sending end of data
>>> -- message may be sent more than once)
>>>
>>> and when I try to flush it.
>>>
>>> postqueue -f
>>> [root at mail1 rsyslog.d]# error: uncaptured python exception, closing
>>> channel <smtpd.SMTPChannel connected 127.0.0.1:36704 at 0x102cdd0>
>>> (<type 'exceptions.UnicodeDecodeError'>:'utf8' codec can't decode byte
>>> 0x92 in position 5975: invalid start byte
>>> [/usr/lib64/python2.6/asyncore.py|read|78]
>>> [/usr/lib64/python2.6/asyncore.py|handle_read_event|428]
>>> [/usr/lib64/python2.6/asynchat.py|handle_read|158]
>>> [/usr/lib64/python2.6/smtpd.py|found_terminator|184]
>>> [/usr/lib/python2.6/site-packages/wallace/__init__.py|process_message|263]
>>> [/usr/lib64/python2.6/json/__init__.py|dumps|237]
>>> [/usr/lib64/python2.6/json/encoder.py|encode|367]
>>> [/usr/lib64/python2.6/json/encoder.py|_iterencode|309]
>>> [/usr/lib64/python2.6/json/encoder.py|_iterencode_dict|275]
>>> [/usr/lib64/python2.6/json/encoder.py|_iterencode|294])
>>>
>>> Any ideas?
>>>
>>> thanks,
>>>
>>> Geoff
>> The messages got stuck again, restarting wallaced freed the messages,
>> but not sure how to fix it permanently.
>>
>> I am running:  pykolab-0.5.14-1.el6.kolab_3.0.noarch
>>
>> thanks,
>>
>> Geoff

>> You are not the only one with wallace problems.
>>
>> Does anybody know if 0.5.15 fix this problem.

For now, I just bypassed wallace  until it gets resolved.

 From what I can see, we don't really need it anyhow.

thanks,

Geoff