[xmail] Filter error -97
Hiya! Well, we attempted to replace our mailserver this weekend but had to revert back to the older one due to a filter issue that didn't make much sense to me. Original setup: RH8 XMail 1.22 f-prot (using a modified clamav filter) SA 3.0.2 (using bsa_filter which is a version of Don's sa_filter that was modified by Beau Cox) Everything runs fine on this config. I built a new Suse 10 box, installed xMail 1.22 on it then moved over my /var/MailRoot folder from the old box. This box is running SA 3.0.4 instead of 3.0.2 and I now receive filter errors on the bsa_filter. It also doesn't appear that xMail starts up all 20 of its threads. pstree -p only shows a single xMail entry (but it does show the 5 spamd threads). All I could find on the 'net had to do with possible timeout erros (apparently this is what the -97 means). spamd is running but it almost seems like SA isn't answering when it's called by the filter. Any thoughts off the top of your heads? I can't easily test it as we didnt' have a replacement server (we just yanked the original drive and put this a new one in for the install so we could easily fall back in case of a failure such as this). For grins I was going to bump up the SA version on the RH box to 3.0.4 to see if it caused the same problems but figured I'd post a quick question first. TIA -- later, Dale mailto:[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: Unable to compile Xmail on NetBSD 3.0
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]
[xmail] RCPT TO smtp filter.
Davide, How difficult would it be to add filters that are triggered for each RCPT TO, similar to smtp pre-data filters? Does functionality like this already exist in Xmail? It would be helpful in the case of greylist and blacklist filters to add more granularity than all or nothing when filtering mail with multiple rcpts. It would also be useful for custom relay domains, where the mailbox list resides outside of Xmail. - 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: RCPT TO smtp filter.
I think smtp filters are currently triggered once for all rcpt, not for each rcpt ! If actual smtp filters are triggering per rcpt, it could be a great option here too to have per 'allrcpt' It should be a option on per filter (like !eax in smtp pre-data) to have more granularity So it could be a good think to add options like 'allrcpt' or 'perrcpt' at any filters level in xmail (smtp pre, post, in, ou, ...) with default value depending of current xmail defaults (to be compatible with previous filters) Francis -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] la part de John Kielkopf Envoyé : lundi 6 mars 2006 18:25 À : xmail@xmailserver.org Objet : [xmail] RCPT TO smtp filter. Davide, How difficult would it be to add filters that are triggered for each RCPT TO, similar to smtp pre-data filters? Does functionality like this already exist in Xmail? It would be helpful in the case of greylist and blacklist filters to add more granularity than all or nothing when filtering mail with multiple rcpts. It would also be useful for custom relay domains, where the mailbox list resides outside of Xmail. - 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]
