devgioiatech at gmail.com
Thu Oct 3 13:00:50 CEST 2013
seems that your patch has solved my problem.
Thanks for help.
2013/10/3 James Mills <prologic a shortcircuit.net.au>
> 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?
> James Mills / prologic
> E: prologic a shortcircuit.net.au
> W: prologic.shortcircuit.net.au
> On Thu, Oct 3, 2013 at 1:43 AM, Antonio Straziota <devgioiatech a gmail.com>wrote:
>> Hi all,
>> I found some email in deferred status after the come in wallace:
>> Oct 2 17:34:23 mail postfix/smtp: 42A0913ED: to=<
>> antonio.straziota a example.com>, 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:
>> 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
>> 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?
>> users mailing list
>> users a lists.kolab.org
> users mailing list
> users a lists.kolab.org
-------------- parte successiva --------------
Un allegato HTML ? stato rimosso...
More information about the users