[xmail] Re: Filter error -97
On 06.03.2006 14:56, Dale Qualls wrote: 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? Maybe XMail debug mode will tell you something more? - 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: Filter error -97
Hiya! Nope, I used that but didn't see diddly. I am going to look at the var/log/mail log when I can though, that should show me if the spamassassin daemon is responding, I didn't think to do that at the time. I'm thinking that the -97 may be a timeout but I'm not positive. I already have QT 600 on the command line. Thanks Sonke! -- later, Dale mailto:[EMAIL PROTECTED] Tuesday, March 7, 2006, 2:53:19 AM, you wrote: On 06.03.2006 14:56, Dale Qualls wrote: 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? Maybe XMail debug mode will tell you something more? - 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: RCPT TO smtp filter.
Yes, they are currently triggered once for all, hence my request ;) I was trying to figure out of there's any way to handle it with external auth, but couldn't come up with anything. To make it somewhat compatible with current SMTP filters, it could just keep appending the new address to the message file. Your script would just need to know the last address is the new one, although adding a mail from and rcpt to macro might be just as easy, and less overhead for the filter to deal with. A helpful additional macro in either case would be an error count, to track the number of bad addresses the MTA has tried so far. I don't know if you could do it in a post data filter, since there's no option but to send a single rejection at that point. But after each RCPT TO, you could opt. to accept or reject that address for any given reason, where Xmail currently only does so based on mailbox size, or if the mailbox exists, etc. CLEMENT Francis wrote: 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]
[xmail] Re: RCPT TO smtp filter.
Personally, I'd like to see the ability to call external filters at each stage of the process (connect, HELO/EHLO, MAIL FROM, RCPT TO (once for each recipient), DATA, and post-DATA). Ideally, these would be triggered once the command is accepted and parsed, but before the SMTP result code is returned to the remote server I'm actually planning to modify a local copy of the Xmail source to let me do this - but with my poor C++ skills, I'm not planning on making the mods public. But it would be really nice if this were an actual feature, rather than something I had to do locally...:) John Kielkopf wrote: Yes, they are currently triggered once for all, hence my request ;) I was trying to figure out of there's any way to handle it with external auth, but couldn't come up with anything. To make it somewhat compatible with current SMTP filters, it could just keep appending the new address to the message file. Your script would just need to know the last address is the new one, although adding a mail from and rcpt to macro might be just as easy, and less overhead for the filter to deal with. A helpful additional macro in either case would be an error count, to track the number of bad addresses the MTA has tried so far. I don't know if you could do it in a post data filter, since there's no option but to send a single rejection at that point. But after each RCPT TO, you could opt. to accept or reject that address for any given reason, where Xmail currently only does so based on mailbox size, or if the mailbox exists, etc. CLEMENT Francis wrote: 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]
[xmail] Re: Filter error -97
On Mon, 6 Mar 2006, Dale Qualls wrote: 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. The error -97 is ERR_FORK. It means you there are too many running processes, or the system was unable to exec your filter. Did you specify the full path to the filter binary? - 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: Unable to compile Xmail on NetBSD 3.0
On Mon, 6 Mar 2006, David Lord wrote: 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. Sorry, I have a very short memory ;) What was the problem with this? Did you post build errors? - 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: Filter error -97
Hi, [EMAIL PROTECTED] schrieb am Tuesday, March 07, 2006 4:53 PM: The error -97 is ERR_FORK. It means you there are too many running processes, or the system was unable to exec your filter. -97 can also happen if the specified filter segfaults. I know from my own experience. :D -- Regards, Alexander Hagenah http://xmail.topconcepts.net - 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: Filter error -97
On Tue, 7 Mar 2006, Alexander Hagenah wrote: [EMAIL PROTECTED] schrieb am Tuesday, March 07, 2006 4:53 PM: The error -97 is ERR_FORK. It means you there are too many running processes, or the system was unable to exec your filter. -97 can also happen if the specified filter segfaults. I know from my own experience. :D Yes, that too. - 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: RCPT TO smtp filter.
On Mon, 6 Mar 2006, John Kielkopf wrote: 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. I'll look into this. Just don't ask me to call out filter for every input char next time! :) - 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: Filter error -97
Hiya! Yes. Actually, I installed xmail then copied my backup over the top of the fresh install so that all of my pathing and executables would be in the exact same place (/var/MailRoot). Dang. -- later, Dale mailto:[EMAIL PROTECTED] Tuesday, March 7, 2006, 9:53:05 AM, you wrote: On Mon, 6 Mar 2006, Dale Qualls wrote: 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. The error -97 is ERR_FORK. It means you there are too many running processes, or the system was unable to exec your filter. Did you specify the full path to the filter binary? - 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: Unable to compile Xmail on NetBSD 3.0
On 7 Mar 2006, at 7:54, Davide Libenzi wrote: On Mon, 6 Mar 2006, David Lord wrote: 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. Sorry, I have a very short memory ;) What was the problem with this? Did you post build errors? Well it was quite a while back (Jan 17). g++ -O2 -I. -D__UNIX__ -D__BSD__ -D__NETBSD__ -D_REENTRANT=1 -D_THREAD_SAFE=1 -DHAS_SYSMACHINE -c SysDep.cpp In file included from SysDep.cpp:40: SysDepBSD.cpp: In function `int SysGetDiskSpace(const char*, SYS_INT64*, SYS_INT64*)': SysDepBSD.cpp:2429: error: aggregate `statfs SFS' has incomplete type and cannot be defined SysDepBSD.cpp:2431: error: invalid use of undefined type `struct statfs' SysDepBSD.cpp:2429: error: forward declaration of `struct statfs' gmake: *** [SysDep.o] Error 1 It didn't get very far. I can post full output 4.5k but that was first error encountered. I've not had any other unexplained problem during setting up this server. xmail-1.21 compiled ok on the k6-400 with NetBSD 2.0 (gcc 2.95) but on trying again after update to NetBSD 3.0 (gcc 3.3.3) and failure of xmail-1.22 to compile I found that wouldn't compile either and gave same error. That would suggest I try again with gcc 2.95 which I'll try after working out how I can safely install it without messing up existing setup. 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] Re: RCPT TO smtp filter.
Davide Libenzi wrote: Just don't ask me to call out filter for every input char next time! :) Damn, and I was just going to ask for that! ;) -John - 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] Using XMail with php
Hello Folks- I'm running XMail and Apache2 on a SuSE 9.2 box. Both servers have been up and running normally for months. I'm creating a web page that uses the php mail() function to send the data from a form. The php scripts work as expected except for the mail() function which fails. My question: If I run XMail in debug mode will I see an entry for any attempt to access the sendmail module, or will I only see an error if the connection is successful but the data is formatted wrong? I would expect that any attempt to connect would be displayed, but for some reason I'm not seeing anything at all. I've even tried connecting directly using: $fd = popen(/usr/sbin/sendmail,w); fputs($fd, .. Nothing. Yet I can log on and send mail from the command line using mail without problems. Any tips on getting the php mail() function to work with XMail? I'm running low on ideas here. 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: Using XMail with php
We have clients that use the mail() command, but I would not recommend it. You should use the PHPMailer class instead of the native mail() command. Many of the popular PHP applications already do this. http://phpmailer.sourceforge.net/ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeffrey Laramie Sent: Tuesday, March 07, 2006 10:05 PM To: xmail@xmailserver.org Subject: [xmail] Using XMail with php Hello Folks- I'm running XMail and Apache2 on a SuSE 9.2 box. Both servers have been up and running normally for months. I'm creating a web page that uses the php mail() function to send the data from a form. The php scripts work as expected except for the mail() function which fails. My question: If I run XMail in debug mode will I see an entry for any attempt to access the sendmail module, or will I only see an error if the connection is successful but the data is formatted wrong? I would expect that any attempt to connect would be displayed, but for some reason I'm not seeing anything at all. I've even tried connecting directly using: $fd = popen(/usr/sbin/sendmail,w); fputs($fd, .. Nothing. Yet I can log on and send mail from the command line using mail without problems. Any tips on getting the php mail() function to work with XMail? I'm running low on ideas here. 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] - 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]
