[xmail] Re: Unable to compile Xmail on NetBSD 3.0
-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.
David
-BEGIN PGP SIGNATURE-
Version: PGP 7.0.4 -- QDPGP 2.65
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBQ9CpIa2RmIodDo7KEQLF9gCcDjZOI9dhOha33aB/X5WFPgiauR8AoOTT
CaPG0LY1Rbz4pQaqPz0yaBdX
=u7HK
-END PGP SIGNATURE-
-
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]
[xmail] Re: XMail on Ubuntu
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 established) Proto Recv-Q Send-Q Local Address Foreign Address =20 State PID/Program name tcp0 0 0.0.0.0:37840.0.0.0:* =20 LISTEN 8231/ventrilo_srv tcp0 0 0.0.0.0:33060.0.0.0:* =20 LISTEN 7556/mysqld tcp0 0 0.0.0.0:139 0.0.0.0:* =20 LISTEN 7768/smbd tcp0 0 0.0.0.0:59000.0.0.0:* =20 LISTEN 8108/vino-server tcp0 0 0.0.0.0:1 0.0.0.0:* =20 LISTEN 7837/perl tcp0 0 0.0.0.0:21 0.0.0.0:* =20 LISTEN 7805/vsftpd tcp0 0 0.0.0.0:31280.0.0.0:* =20 LISTEN 9450/(squid) tcp0 0 0.0.0.0:445 0.0.0.0:* =20 LISTEN 7768/smbd tcp0 0 192.168.1.3:3784217.157.129.119:23154 =20 ESTABLISHED8231/ventrilo_srv tcp6 0 0 :::80 :::* =20 LISTEN 7973/apache2 tcp6 0 0 :::22 :::* =20 LISTEN 7783/sshd tcp6 0296 :::192.168.1.3:22 :::85.235.17.:40260 ESTABLISHED31631/sshd: cs [pri Looks clean. Now try to get one slog file from inside the spool: # find $MAIL_ROOT -type f | grep slog Pick one and post it online. - Davide - 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] - 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]
[xmail] Error messages returned to sender replicated
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 one email containing all of the failures (which is the expected behavior, right?). Right now I have XMail set to try 10 times, so there seem to be 10 emails that are sent to notify the sender of the failure. It was set to 40, and in that case the user was receiving 40 (or so) emails. I have not verified that the number of returns is always exactly the same as the retry setting, but it is at least somewhat close. Has anyone seen this behavior? I am trying to verify if it is only my Exchange users that have this problem - XMail is running on FreeBSD, but a number of Exchange users send through it as shown: Exchange - ASSP (anti-spam proxy) -XMail - Internet - the problem definitely happens with this flow or Email client - ASSP - XMail - Internet - the problem has not been verified yet with this flow Thanks, Jeff - 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]
[xmail] Re: Unable to compile Xmail on NetBSD 3.0
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.
- Davide
-
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]
[xmail] Re: XMail on Ubuntu
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 - 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]
[xmail] Re: Error messages returned to sender replicated
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 each failed delivery attempt, rather than one email containing all of the failures (which is the expected behavior, right?). Right now I have XMail set to try 10 times, so there seem to be 10 emails that are sent to notify the sender of the failure. It was set to 40, and in that case the user was receiving 40 (or so) emails. I have not verified that the number of returns is always exactly the same as the retry setting, but it is at least somewhat close. How's your NotifyTryPattern set inside the server.tab? - Davide - 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]
[xmail] Re: Error messages returned to sender replicated
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: buehlertech.net PostMaster [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 6:31 AM To: Jens Jensen Subject: Error sending message [1137452256244.135361536.4d65.banshee.buehlertech.net] from [buehlertech.net] [00] XMail bounce: [EMAIL PROTECTED];Error=[The maximum number of delivery attempts has been reached] Jeff Davide Libenzi wrote: 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 each failed delivery attempt, rather than one email containing all of the failures (which is the expected behavior, right?). Right now I have XMail set to try 10 times, so there seem to be 10 emails that are sent to notify the sender of the failure. It was set to 40, and in that case the user was receiving 40 (or so) emails. I have not verified that the number of returns is always exactly the same as the retry setting, but it is at least somewhat close. How's your NotifyTryPattern set inside the server.tab? - Davide - 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] - 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]
[xmail] Re: Error messages returned to sender replicated
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 configuration - exchange - assp - xmail - internet). It is possible that I may have made some seemingly insignificant change to any of the players involved, though, most suspect being ASSP. I have verified that I (seem) get only one failure message back to the sender when the configuration does not involve exchange, that being email client - assp - xmail - internet. Unless I am misreading the documentation, I think this is also not the right behavior since NotifyTryPattern is set to the default, but I prefer it to a whole bunch of messages! Here is an example of the header for that: [00] XMail bounce: [EMAIL PROTECTED];Error=[The maximum number of delivery attempts has been reached] [01] Error sending message [1137796073865.135234560.61c.banshee.buehlertech.net] from [buehlertech.net]. ID:S75D07 Mail From: [EMAIL PROTECTED] Rcpt To: [EMAIL PROTECTED] Server:bogusdomain.com [bogusdomain.com] [02] The reason of the delivery failure was: The maximum number of delivery attempts has been reached Thanks again for any thoughts or ideas... Jeff Jeff Buehler wrote: 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: buehlertech.net PostMaster [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 6:31 AM To: Jens Jensen Subject: Error sending message [1137452256244.135361536.4d65.banshee.buehlertech.net] from [buehlertech.net] [00] XMail bounce: [EMAIL PROTECTED];Error=[The maximum number of delivery attempts has been reached] Jeff Davide Libenzi wrote: 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 each failed delivery attempt, rather than one email containing all of the failures (which is the expected behavior, right?). Right now I have XMail set to try 10 times, so there seem to be 10 emails that are sent to notify the sender of the failure. It was set to 40, and in that case the user was receiving 40 (or so) emails. I have not verified that the number of returns is always exactly the same as the retry setting, but it is at least somewhat close. How's your NotifyTryPattern set inside the server.tab? - Davide - 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] - 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] - 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]
