For 2.0 that's not necessary. There's a valid configure script you can
use in the tree.
For 2.1 I use 'autoreconf -f -i'.
Tommi Lätti wrote:
>
> On 23 Jun 2005, at 17:08, Ville Ahonen wrote:
>
>> Paul, rev 1814 fixed the problem for me.
>
>
> Ah please excuse my stupidity but how do you build
On 23 Jun 2005, at 17:08, Ville Ahonen wrote:
Paul, rev 1814 fixed the problem for me.
Ah please excuse my stupidity but how do you build the tools since
the snapshots are without any buildtools etc? Autoreconf doesn't help
either...
--
br,
Tommi
Paul, rev 1814 fixed the problem for me.
Regs,
Ville
Paul J Stevens wrote:
Ming-Wei Shih wrote:
I had the same problem and went back to 2.0.4, here is the lmtp log
(trace=5), due to this I lost 1 day
of mails
Sorry about that Ming-Wei. I fixed this bug in trunk, but forgot to
apply
Ming-Wei Shih wrote:
> I had the same problem and went back to 2.0.4, here is the lmtp log
> (trace=5), due to this I lost 1 day
> of mails
Sorry about that Ming-Wei. I fixed this bug in trunk, but forgot to
apply the same to 2.0.
Ville, afaik it was not revision 1797, but 1800 that caused this
I had the same problem and went back to 2.0.4, here is the lmtp log
(trace=5), due to this I lost 1 day
of mails
Ming-Wei
Ville Ahonen wrote:
Sorry, I don't know exactly what debugging info you want, but I can tell you
that the error started between revisions 1796 and 1797. In other words, 179
Sorry, I don't know exactly what debugging info you want, but I can tell you
that the error started between revisions 1796 and 1797. In other words, 1797
bounces all my incoming mail, while 1796 works like a charm (the change has
occurred in the file dbmsgbuf.c). If you need more exact debug-data p
I guess, Paul (as always and as anybody else) would write that you'd
better post the debug info here.
The more - the better =))
Today I updated my server to the current head of the 2.0 branch. Until
now my server (last updated on 3 June) was functioning fine. After the
update, all my incoming
Today I updated my server to the current head of the 2.0 branch. Until
now my server (last updated on 3 June) was functioning fine. After the
update, all my incoming mails were being bounced with the following
message in the log:
Jun 22 10:59:29 [postfix/lmtp] 26DDC64CF1: to=<[EMAIL PROTECTED]
