Mailing List Archive: DBMail: users

LMTP in 3.1.x for sure buggy

Index | Next | Previous | View Threaded

h.reindl at thelounge

Jul 30, 2013, 10:40 AM

Post #1 of 10 (116 views)
Permalink

LMTP in 3.1.x for sure buggy

http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1

after sending a message to a RCPT expanded to 9 addresses by postfix
"delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1]
while sending end of data -- message may be sent more than once" starts
again until i restart dbmail-lmtpd

well, this was to teh internal list the "dbmail upgraded please take care"
message and so i fear i need to rebuild the older snapshot for Fedora 18
and downgrade again...........................

on thursday before we discovered the POP3 bug this happended twice, in both
cases a expanded message was the reason, but following mails was devlivered

this time i saw the problem persist :-(
________________________________________

after update dbmail and reboot the machine i also saw a message
from postfix that 127.0.0.1:24 refused the connection while a test
with telnet was successful, since this was the first boot after
a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK

________________________________________

Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from rh.thelounge.net[xx.0.0.99]
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (215 Recipient
<*****@thelounge.net> OK)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (221 mail.thelounge.net BYE)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)

Attachments:

signature.asc (0.26 KB)

harald.leithner at itronic

Jul 30, 2013, 10:59 AM

Post #2 of 10 (113 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

I send an E-Mail to Paul with some more debug informations from postfix, 2
of 3 Mails got delivered.

But I will do more test with this information. Maybe its possible to
deactivate pipelining in postfix.

Am 30.07.2013, 19:40 Uhr, schrieb Reindl Harald <h.reindl [at] thelounge>:

> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1
>
> after sending a message to a RCPT expanded to 9 addresses by postfix
> "delivery temporarily suspended: lost connection with
> 127.0.0.1[127.0.0.1]
> while sending end of data -- message may be sent more than once" starts
> again until i restart dbmail-lmtpd
>
> well, this was to teh internal list the "dbmail upgraded please take
> care"
> message and so i fear i need to rebuild the older snapshot for Fedora 18
> and downgrade again...........................
>
> on thursday before we discovered the POP3 bug this happended twice, in
> both
> cases a expanded message was the reason, but following mails was
> devlivered
>
> this time i saw the problem persist :-(
> ________________________________________
>
> after update dbmail and reboot the machine i also saw a message
> from postfix that 127.0.0.1:24 refused the connection while a test
> with telnet was successful, since this was the first boot after
> a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK
>
> ________________________________________
>
> Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from
> rh.thelounge.net[xx.0.0.99]
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> dsn=2.0.0, status=sent (215 Recipient
> <*****@thelounge.net> OK)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> dsn=2.0.0, status=sent (221 mail.thelounge.net BYE)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
> 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)
>
>
>
>
>

--
Harald Leithner

ITronic
Vogelweidplatz 12, 1150 Wien, Austria
Tel: +43-1-786 23 88
Fax: +43-1-98 52 077
Mobil: +43-699-123 78 4 78
Mail: leithner [at] itronic | itronic.at
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

harald.leithner at itronic

Jul 30, 2013, 11:07 AM

Post #3 of 10 (112 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

I traced a tcpdump and it looks like only the last email address of RCPT
where accepted with
215 Recipient <email [at] example> OK

after this there comes a
221 server BYE

but if I understand the lmtp protocol correct you have to send an ok for
each E-Mail or?

Am 30.07.2013, 19:59 Uhr, schrieb Harald Leithner
<harald.leithner [at] itronic>:

> I send an E-Mail to Paul with some more debug informations from postfix,
> 2 of 3 Mails got delivered.
>
> But I will do more test with this information. Maybe its possible to
> deactivate pipelining in postfix.
>
>
>
> Am 30.07.2013, 19:40 Uhr, schrieb Reindl Harald <h.reindl [at] thelounge>:
>
>> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1
>>
>> after sending a message to a RCPT expanded to 9 addresses by postfix
>> "delivery temporarily suspended: lost connection with
>> 127.0.0.1[127.0.0.1]
>> while sending end of data -- message may be sent more than once" starts
>> again until i restart dbmail-lmtpd
>>
>> well, this was to teh internal list the "dbmail upgraded please take
>> care"
>> message and so i fear i need to rebuild the older snapshot for Fedora 18
>> and downgrade again...........................
>>
>> on thursday before we discovered the POP3 bug this happended twice, in
>> both
>> cases a expanded message was the reason, but following mails was
>> devlivered
>>
>> this time i saw the problem persist :-(
>> ________________________________________
>>
>> after update dbmail and reboot the machine i also saw a message
>> from postfix that 127.0.0.1:24 refused the connection while a test
>> with telnet was successful, since this was the first boot after
>> a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK
>>
>> ________________________________________
>>
>> Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from
>> rh.thelounge.net[xx.0.0.99]
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> dsn=2.0.0, status=sent (215 Recipient
>> <*****@thelounge.net> OK)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> dsn=2.0.0, status=sent (221 mail.thelounge.net BYE)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>> 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)
>>
>>
>>
>>
>>
>
>

--
Harald Leithner

ITronic
Vogelweidplatz 12, 1150 Wien, Austria
Tel: +43-1-786 23 88
Fax: +43-1-98 52 077
Mobil: +43-699-123 78 4 78
Mail: leithner [at] itronic | itronic.at
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

h.reindl at thelounge

Jul 30, 2013, 11:12 AM

Post #4 of 10 (112 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

however, the real problem here was that any following message also
ended in "lost connection with 127.0.0.1[127.0.0.1] while sending end
of data" which means no new mail to any user until restart

so i rolled back to the 3.0.0 snapshot we have in use since more than
a year and the "dbmail-3.1.1-4" has only the reason that it is easier
to distribute than downgrades over a lot of machines

dbmail-3.1.1-4.fc18.20130730.rh.22b964b653ba149b63b9b6787aeac7803c2121e5.x86_64

Am 30.07.2013 20:07, schrieb Harald Leithner:
> I traced a tcpdump and it looks like only the last email address of RCPT where accepted with
> 215 Recipient <email [at] example> OK
>
> after this there comes a
> 221 server BYE
>
> but if I understand the lmtp protocol correct you have to send an ok for each E-Mail or?
>
>
> Am 30.07.2013, 19:59 Uhr, schrieb Harald Leithner <harald.leithner [at] itronic>:
>
>> I send an E-Mail to Paul with some more debug informations from postfix, 2 of 3 Mails got delivered.
>>
>> But I will do more test with this information. Maybe its possible to deactivate pipelining in postfix.
>>
>>
>>
>> Am 30.07.2013, 19:40 Uhr, schrieb Reindl Harald <h.reindl [at] thelounge>:
>>
>>> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1
>>>
>>> after sending a message to a RCPT expanded to 9 addresses by postfix
>>> "delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1]
>>> while sending end of data -- message may be sent more than once" starts
>>> again until i restart dbmail-lmtpd
>>>
>>> well, this was to teh internal list the "dbmail upgraded please take care"
>>> message and so i fear i need to rebuild the older snapshot for Fedora 18
>>> and downgrade again...........................
>>>
>>> on thursday before we discovered the POP3 bug this happended twice, in both
>>> cases a expanded message was the reason, but following mails was devlivered
>>>
>>> this time i saw the problem persist :-(
>>> ________________________________________
>>>
>>> after update dbmail and reboot the machine i also saw a message
>>> from postfix that 127.0.0.1:24 refused the connection while a test
>>> with telnet was successful, since this was the first boot after
>>> a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK
>>>
>>> ________________________________________
>>>
>>> Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from rh.thelounge.net[xx.0.0.99]
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (215 Recipient
>>> <*****@thelounge.net> OK)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (221
>>> mail.thelounge.net BYE)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)

Attachments:

signature.asc (0.26 KB)

harald.leithner at itronic

Jul 30, 2013, 11:17 AM

Post #5 of 10 (111 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

After comparing the output of 3.0.2 with 3.1.1 I found the problem.

3.1.1 doesn't replay with the correct count of
215 Recipient <email> OK

3.0.2 returns this response for each email adresse in RCPT part.

@Harald Reindl you could run 3.0.2 dbmail-lmtpd instead of 3.1.1 if you
have the binary^^

Am 30.07.2013, 20:07 Uhr, schrieb Harald Leithner
<harald.leithner [at] itronic>:

> I traced a tcpdump and it looks like only the last email address of RCPT
> where accepted with
> 215 Recipient <email [at] example> OK
>
> after this there comes a
> 221 server BYE
>
> but if I understand the lmtp protocol correct you have to send an ok for
> each E-Mail or?
>
>
> Am 30.07.2013, 19:59 Uhr, schrieb Harald Leithner
> <harald.leithner [at] itronic>:
>
>> I send an E-Mail to Paul with some more debug informations from
>> postfix, 2 of 3 Mails got delivered.
>>
>> But I will do more test with this information. Maybe its possible to
>> deactivate pipelining in postfix.
>>
>>
>>
>> Am 30.07.2013, 19:40 Uhr, schrieb Reindl Harald
>> <h.reindl [at] thelounge>:
>>
>>> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1
>>>
>>> after sending a message to a RCPT expanded to 9 addresses by postfix
>>> "delivery temporarily suspended: lost connection with
>>> 127.0.0.1[127.0.0.1]
>>> while sending end of data -- message may be sent more than once" starts
>>> again until i restart dbmail-lmtpd
>>>
>>> well, this was to teh internal list the "dbmail upgraded please take
>>> care"
>>> message and so i fear i need to rebuild the older snapshot for Fedora
>>> 18
>>> and downgrade again...........................
>>>
>>> on thursday before we discovered the POP3 bug this happended twice, in
>>> both
>>> cases a expanded message was the reason, but following mails was
>>> devlivered
>>>
>>> this time i saw the problem persist :-(
>>> ________________________________________
>>>
>>> after update dbmail and reboot the machine i also saw a message
>>> from postfix that 127.0.0.1:24 refused the connection while a test
>>> with telnet was successful, since this was the first boot after
>>> a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK
>>>
>>> ________________________________________
>>>
>>> Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from
>>> rh.thelounge.net[xx.0.0.99]
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> dsn=2.0.0, status=sent (215 Recipient
>>> <*****@thelounge.net> OK)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> dsn=2.0.0, status=sent (221 mail.thelounge.net BYE)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34:
>>> to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14,
>>> 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)
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>

--
Harald Leithner

ITronic
Vogelweidplatz 12, 1150 Wien, Austria
Tel: +43-1-786 23 88
Fax: +43-1-98 52 077
Mobil: +43-699-123 78 4 78
Mail: leithner [at] itronic | itronic.at
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

h.reindl at thelounge

Jul 30, 2013, 11:20 AM

Post #6 of 10 (111 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

Am 30.07.2013 20:17, schrieb Harald Leithner:
> After comparing the output of 3.0.2 with 3.1.1 I found the problem.
>
> 3.1.1 doesn't replay with the correct count of
> 215 Recipient <email> OK
>
> 3.0.2 returns this response for each email adresse in RCPT part.
>
> @Harald Reindl you could run 3.0.2 dbmail-lmtpd instead of 3.1.1 if you have the binary^^

sorry - there was a switch from fedora 17 to Fedora 18 between
after 19 dist-upgrades starting with yesterday until now i
am missing the concentration for such experiments

but *thank you* for most likely point in the right direction

> Am 30.07.2013, 20:07 Uhr, schrieb Harald Leithner <harald.leithner [at] itronic>:
>
>> I traced a tcpdump and it looks like only the last email address of RCPT where accepted with
>> 215 Recipient <email [at] example> OK
>>
>> after this there comes a
>> 221 server BYE
>>
>> but if I understand the lmtp protocol correct you have to send an ok for each E-Mail or?
>>
>>
>> Am 30.07.2013, 19:59 Uhr, schrieb Harald Leithner <harald.leithner [at] itronic>:
>>
>>> I send an E-Mail to Paul with some more debug informations from postfix, 2 of 3 Mails got delivered.
>>>
>>> But I will do more test with this information. Maybe its possible to deactivate pipelining in postfix.
>>>
>>>
>>>
>>> Am 30.07.2013, 19:40 Uhr, schrieb Reindl Harald <h.reindl [at] thelounge>:
>>>
>>>> http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1
>>>>
>>>> after sending a message to a RCPT expanded to 9 addresses by postfix
>>>> "delivery temporarily suspended: lost connection with 127.0.0.1[127.0.0.1]
>>>> while sending end of data -- message may be sent more than once" starts
>>>> again until i restart dbmail-lmtpd
>>>>
>>>> well, this was to teh internal list the "dbmail upgraded please take care"
>>>> message and so i fear i need to rebuild the older snapshot for Fedora 18
>>>> and downgrade again...........................
>>>>
>>>> on thursday before we discovered the POP3 bug this happended twice, in both
>>>> cases a expanded message was the reason, but following mails was devlivered
>>>>
>>>> this time i saw the problem persist :-(
>>>> ________________________________________
>>>>
>>>> after update dbmail and reboot the machine i also saw a message
>>>> from postfix that 127.0.0.1:24 refused the connection while a test
>>>> with telnet was successful, since this was the first boot after
>>>> a dist-upgrade i restarted dbmail-lmtpd and hoped it will be OK
>>>>
>>>> ________________________________________
>>>>
>>>> Jul 30 19:29:12 mail postfix/smtpd[25852]: disconnect from rh.thelounge.net[xx.0.0.99]
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (215 Recipient
>>>> <*****@thelounge.net> OK)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, dsn=2.0.0, status=sent (221
>>>> mail.thelounge.net BYE)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)
>>>> Jul 30 19:29:12 mail postfix/lmtp[757]: 3c4Prm3xJgz34: to=<*****@thelounge.net>, orig_to=<<*****@thelounge.net>,
>>>> relay=127.0.0.1[127.0.0.1]:24, delay=0.29, delays=0.03/0.11/0/0.14, 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)

Attachments:

signature.asc (0.26 KB)

paul at nfg

Jul 31, 2013, 1:09 AM

Post #7 of 10 (96 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

On 30-07-13 20:17, Harald Leithner wrote:
> After comparing the output of 3.0.2 with 3.1.1 I found the problem.
>
>
> 3.1.1 doesn't replay with the correct count of
> 215 Recipient <email> OK
>
> 3.0.2 returns this response for each email adresse in RCPT part.

Thanks a lot. That I can work with. I'll try to fix this today.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/info [at] nfg/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

paul at nfg

Jul 31, 2013, 1:25 AM

Post #8 of 10 (97 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

On 31-07-13 10:09, Paul J Stevens wrote:
> On 30-07-13 20:17, Harald Leithner wrote:
>> After comparing the output of 3.0.2 with 3.1.1 I found the problem.
>>
>>
>> 3.1.1 doesn't replay with the correct count of
>> 215 Recipient <email> OK
>>
>> 3.0.2 returns this response for each email adresse in RCPT part.
>
> Thanks a lot. That I can work with. I'll try to fix this today.

Fixed already.

--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, skype, linkedin

* Premium Hosting Services and Web Application Consultancy *

www.nfg.nl/info [at] nfg/+31.85.877.99.97
________________________________________________________________
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

h.reindl at thelounge

Jul 31, 2013, 1:39 AM

Post #9 of 10 (97 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

Am 31.07.2013 10:25, schrieb Paul J Stevens:
> On 31-07-13 10:09, Paul J Stevens wrote:
>> On 30-07-13 20:17, Harald Leithner wrote:
>>> After comparing the output of 3.0.2 with 3.1.1 I found the problem.
>>>
>>>
>>> 3.1.1 doesn't replay with the correct count of
>>> 215 Recipient <email> OK
>>>
>>> 3.0.2 returns this response for each email adresse in RCPT part.
>>
>> Thanks a lot. That I can work with. I'll try to fix this today.
>
> Fixed already

thank you very much!

confirmed - hopefully that was the last major problem for a longer
time forcing to downgrade - i'm getting too old for this :-)

best wishes from Vienna

Attachments:

signature.asc (0.26 KB)

harald.leithner at itronic

Jul 31, 2013, 1:43 AM

Post #10 of 10 (98 views)
Permalink

Re: LMTP in 3.1.x for sure buggy [In reply to]

Am 31.07.2013, 10:39 Uhr, schrieb Reindl Harald <h.reindl [at] thelounge>:

>
>
> Am 31.07.2013 10:25, schrieb Paul J Stevens:
>> On 31-07-13 10:09, Paul J Stevens wrote:
>>> On 30-07-13 20:17, Harald Leithner wrote:
>>>> After comparing the output of 3.0.2 with 3.1.1 I found the problem.
>>>>
>>>>
>>>> 3.1.1 doesn't replay with the correct count of
>>>> 215 Recipient <email> OK
>>>>
>>>> 3.0.2 returns this response for each email adresse in RCPT part.
>>>
>>> Thanks a lot. That I can work with. I'll try to fix this today.
>>
>> Fixed already
>
> thank you very much!
>
> confirmed - hopefully that was the last major problem for a longer
> time forcing to downgrade - i'm getting too old for this :-)
>
> best wishes from Vienna
>

same here, works perfect now ;-)

--
Harald Leithner

ITronic
Vogelweidplatz 12, 1150 Wien, Austria
Tel: +43-1-786 23 88
Fax: +43-1-98 52 077
Mobil: +43-699-123 78 4 78
Mail: leithner [at] itronic | itronic.at
_______________________________________________
DBmail mailing list
DBmail [at] dbmail
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads