On 20 Jan 2006, at 17:42, Davide Libenzi wrote:
>
> On Fri, 20 Jan 2006, David Lord wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > On 17 Jan 2006, at 11:41, Davide Libenzi wrote:
> >
> >> Can you try this?
> >>
> >> $ find /usr/include -type f -exec grep -H statfs {} \;
> >
> > Hi again
> >
> > I'm still no further forward with solution as to why I can't get a
> > clean compile of 1.21 or 1.22 on NetBSD 3.0. Although I've not yet
> > done a reinstall from scratch I've extracted all distribution files
> > and above command pointed to that usr/include is exactly same as
> > before.
> >
> > I've traced where I went wrong on subsequent postinstall and deleted
> > some critical files (recovered from backup) and after reducing
> > maximum sizes and number of mails parameters got around the error -
> > 213 (this pc has only 64 MB ram vs 128 MB on system being replaced.
> >
> > XMail still seems to be working ok for local mail and a short period
> > with pop3 collection for lan directed through this pc.
> >
> > I've a domain that gets so little genuine mail I'll direct that
> > through this box and setup some of pcs on lan to send through it.
> >
> > Only real problem I've seen is that /etc/daily crontab creates
> > daily.out with 'To: root' and uses 'sendmail -t' to extract
> > recipients which isn't accepted by XMails sendmail. I've just
> > changed that and similar crontabs to use real sendmail.
>
> Honestly I have no idea. I'd restart with a clean system install, and
> build up from there. When things gets really screwed and wierd, that's
> usually the best way.
Update on my problem with xmail-1.22 failing to compile on NetBSD
3.0/i386.
Still no luck with this. It would be nice to hear from someone that
is using xmailserver with NetBSD 3.0/i386.
I'd been trying to compile on a k6-400 pc that was first installed
with NetBSD 2.02 then updated eventually to NetBSD 3.0.
I now have a desktop p4-2600 with NetBSD 3.0 default full install and
attempt to compile xmail 1.22 gives exact same error and failure as
before.
Meanwhile the k6x400 with the source hacked (almost certainly
incorrectly - I'm no programmer) such that it does compile has now
been up 47 days but has only been very lightly loaded with test
emails. It will be a bit of a hassle but I'm going to switch domain
that is most spammed/with least genuine email to go through that.
David
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]