-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.
Hm... I doesn't find anything.
On 1/19/06, Davide Libenzi davidel@xmailserver.org wrote:
On Thu, 19 Jan 2006, Thomas Bresson wrote:
I'm sorry. I not used to people replying inside the original mail. Sorry.
Here's my netstat made with root:
Active Internet connections (servers and
Hi everyone -
Running XMail 1.22 my users have been reporting that No server found
errors are coming back in duplicate. The mails all come in after The
maximum number of delivery attempts has been reached and the user
receives a separate email for each failed delivery attempt, rather than
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
On Fri, 20 Jan 2006, Thomas Bresson wrote:
Hm... I doesn't find anything.
Here $MAIL_ROOT is the path where XMail gets installed. If it is
/var/MailRoot run:
# find /var/MailRoot/spool -type f | grep slog
If it doesn't find anything, try:
# find /var/MailRoot/spool | grep slog
- Davide
On Fri, 20 Jan 2006, Jeff Buehler wrote:
Hi everyone -
Running XMail 1.22 my users have been reporting that No server found
errors are coming back in duplicate. The mails all come in after The
maximum number of delivery attempts has been reached and the user
receives a separate email for
Ah ... I was unaware of that setting. It's commented out, which
according to the documentation would seem to suggest that the errors
aren't (or shouldn't be) coming from XMail at all. However, the headers
indicate (to me, anyway!) that they are - here is an abbreviated example:
From:
By the way, I had no indications of this happening using 1.21 or
earlier. This does not mean that it didn't for certain, but I am pretty
certain that it would have come up (I was running 1.21 and maybe 1.20
from the time they were made available until the newer versions with
this
