RE: [qmailtoaster] address mapping problem?
Hi Again Unfortunately the user currently experiencing the problem has deleted the suspect emails so I am unable to check the header information. I've looked in the vpopmail database and to be completely honest it all looks in order. I do have one additional piece of information, some output from the smtp log: CHKUSER accepted rcpt: from sendingu...@sendingdomain.com:: remote mail.sendingdomain.com:unknown:172.17.100.1 rcpt james-l...@protecteddomain.net : found existing recipient james-l...@protecteddomain.net does not exist on my server! But as mentioned previously the user ja...@protecteddomain.net is receiving the mail. I did read something on google about email addresses with hyphens in having the hyphen and the following address portion stripped out? I don't know if im on the right track or not... Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk Complete IT and Telecommunications Solutions Navigate Solutions LLP is registered in England and Wales, company number OC313052 -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 07 April 2009 17:40 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] address mapping problem? There's not a whole lot to it IIRC, although it's not exactly normalized. Wait a second though. When you say things are mis-delivered, something just occurred to me. Have you checked the message headers of those alleged mis-deliveries? I've seen cases (spam mostly) where a message appears to be addressed to one person but is in fact delivered to another. That's because there are two different To: addresses in an email message, one one the envelope (which is what's used for delivery), and another on the contents (the message itself, which is what you normally see). These addresses aren't necessarily the same. By looking at the message header, you can see who the message is actually addressed/delivered to. I'd check this first to be sure that there's really a mis-delivery. Josh D. Dinsdale wrote: Thanks for the quick reply, i thought it must be something to do with the DB. Any idea what i might be looking for in there? Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk Complete IT and Telecommunications Solutions Navigate Solutions LLP is registered in England and Wales, company number OC313052 -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 07 April 2009 16:50 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] address mapping problem? Sounds to me like the vpopmail database might have something amiss. I'd have a look at the corresponding records there. phpmyadmin is a nice tool for browsing around (and more!) mysql databases. Josh D. Dinsdale wrote: Hi Guys Ive been having this issue on and off for a while now. Basically ,ive got a user setup for example ja...@ourdomain.com mailto:ja...@ourdomain.com, now for some reason someone is sending mail to (again an example) james.some...@ourdomain.com mailto:james.some...@ourdomain.com which is an account that doesn't exist, but for some reason instead of dropping the mail, its being delivered to the first guys email address ja...@ourdomain.com mailto:ja...@ourdomain.com. I've experienced this same scenario for other users. i.e. m...@ourdomain.com mailto:m...@ourdomain.com b...@ourdomain.com mailto:b...@ourdomain.com. It seems its matching the first part of the address and delivering it to the user with the closest address or something, its very strange. Any ideas anyone? Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk BLOCKED::mailto:josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk blocked::http://www.navigatesolutions.co.uk/ Complete IT and Telecommunications Solutions /Navigate Solutions LLP is registered in England and Wales, company number OC313052/ -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
Eric Shubert wrote: Why is it that empF is not included in the stock toaster? Seems like a nice feature to me. Because Erik froze development on the 1.3 branch almost 2 years ago to make time for the new version. I've been holding with this and concentrating on the 2.0 branch - once the 2.0 branch is at least semi-stable I plan to come back and freshen the 1.3 branch and may consider putting the patch in if it's one of those patches that requires no configuration to *not* use it (ie: you have to do something to turn it on). I'd also like to hear more people asking for it before I commit to adding it - I believe we've had 4 people ask for it in the last couple years. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
Jake Vickers wrote: Eric Shubert wrote: Why is it that empF is not included in the stock toaster? Seems like a nice feature to me. Because Erik froze development on the 1.3 branch almost 2 years ago to make time for the new version. I've been holding with this and concentrating on the 2.0 branch - once the 2.0 branch is at least semi-stable I plan to come back and freshen the 1.3 branch and may consider putting the patch in if it's one of those patches that requires no configuration to *not* use it (ie: you have to do something to turn it on). I'd also like to hear more people asking for it before I commit to adding it - I believe we've had 4 people ask for it in the last couple years. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com Jake, empF needs a file in /var/qmail/control named policy with contents (the policies) in order for it to be active. (You probably are aware of this.) I have tested to see if qmail works when the policy file is missing and /or empty. It works in both cases. So in order to turn it on, you need to have a policy set inside the file. I am not an expert on empF, but I do use it. I think if more people were aware of empF they would use it. To be honest, I had a difficult time finding it. It was worth the effort, it does exactly what I need it to do. Limit email addresses that users can send and receive email to/from. Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
Jake Vickers wrote: Dave Hallowell wrote: Glad to hear it worked. Now that you have the spec file patched, you can create a new patch for others so they do not have to go through the same process. Move the patched spec file to a new name, and then install the .src.rpm again. Then from the SOURCES dir run: diff -Naur qmail-toaster.spec modified-qmail-toaster.spec empF-1.3.16.patch That will give you a patch (empF-1.3.16.patch) that will apply cleanly to the new version of qmail-toaster. Post it back so others can obtain it, and update the wiki. You're now an official contributor! Jake, Please excuse my newbieness. I have created the patch file for empF as you described. I have tested my patch and it works on my system following the current wiki using my patch in step 4 versus the stated patch. What do you mean "Post it back"? Do you mean just copy and paste the contents of the patch here in an email or something else? Also, isn't this a patch just for those wanting empF on centos4 running qmail-toaster-1.03-1.3.16 (with the offending libraries). If so, do I just append my notes to the current wiki entry? I am a little hesitate since I have never done this before. I want to get this right. thanks, Depending on how you edited the patch, it should allow anyone who wants empF to use it. If you'd like you can send me the patch (compressed, zip, gzip, or bzip2) and I'll make sure that it applies cleanly and link it somewhere so that those reading the wiki can download it and use it. Jake , I will try to get this ready today and send to you. Thanks, Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] address mapping problem?
light goes on in Eric's head That is indeed 'normal' behavior. Any mail addressed to use...@domain.com is delivered to u...@domain.com. See man dot-qmail, EXTENSION ADDRESSES section for an explaination. Josh D. Dinsdale wrote: Hi Again Unfortunately the user currently experiencing the problem has deleted the suspect emails so I am unable to check the header information. I've looked in the vpopmail database and to be completely honest it all looks in order. I do have one additional piece of information, some output from the smtp log: CHKUSER accepted rcpt: from sendingu...@sendingdomain.com:: remote mail.sendingdomain.com:unknown:172.17.100.1 rcpt james-l...@protecteddomain.net : found existing recipient james-l...@protecteddomain.net does not exist on my server! But as mentioned previously the user ja...@protecteddomain.net is receiving the mail. I did read something on google about email addresses with hyphens in having the hyphen and the following address portion stripped out? I don't know if im on the right track or not... Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk Complete IT and Telecommunications Solutions Navigate Solutions LLP is registered in England and Wales, company number OC313052 -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 07 April 2009 17:40 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] address mapping problem? There's not a whole lot to it IIRC, although it's not exactly normalized. Wait a second though. When you say things are mis-delivered, something just occurred to me. Have you checked the message headers of those alleged mis-deliveries? I've seen cases (spam mostly) where a message appears to be addressed to one person but is in fact delivered to another. That's because there are two different To: addresses in an email message, one one the envelope (which is what's used for delivery), and another on the contents (the message itself, which is what you normally see). These addresses aren't necessarily the same. By looking at the message header, you can see who the message is actually addressed/delivered to. I'd check this first to be sure that there's really a mis-delivery. Josh D. Dinsdale wrote: Thanks for the quick reply, i thought it must be something to do with the DB. Any idea what i might be looking for in there? Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk Complete IT and Telecommunications Solutions Navigate Solutions LLP is registered in England and Wales, company number OC313052 -Original Message- From: news [mailto:n...@ger.gmane.org] On Behalf Of Eric Shubert Sent: 07 April 2009 16:50 To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster] address mapping problem? Sounds to me like the vpopmail database might have something amiss. I'd have a look at the corresponding records there. phpmyadmin is a nice tool for browsing around (and more!) mysql databases. Josh D. Dinsdale wrote: Hi Guys Ive been having this issue on and off for a while now. Basically ,ive got a user setup for example ja...@ourdomain.com mailto:ja...@ourdomain.com, now for some reason someone is sending mail to (again an example) james.some...@ourdomain.com mailto:james.some...@ourdomain.com which is an account that doesn't exist, but for some reason instead of dropping the mail, its being delivered to the first guys email address ja...@ourdomain.com mailto:ja...@ourdomain.com. I've experienced this same scenario for other users. i.e. m...@ourdomain.com mailto:m...@ourdomain.com b...@ourdomain.com mailto:b...@ourdomain.com. It seems its matching the first part of the address and delivering it to the user with the closest address or something, its very strange. Any ideas anyone? Best Regards Josh Dinsdale IT Engineer Navigate Solutions Innovation Centre St Cross Business Park Newport, IW PO30 5WB T: 01983 550360 E: josh.dinsd...@navigatesolutions.co.uk BLOCKED::mailto:josh.dinsd...@navigatesolutions.co.uk W: www.navigatesolutions.co.uk blocked::http://www.navigatesolutions.co.uk/ Complete IT and Telecommunications Solutions /Navigate Solutions LLP is registered in England and Wales, company number OC313052/ -- -Eric 'shubes' - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To
Re: [qmailtoaster] empF patch
Dave Hallowell wrote: Jake Vickers wrote: Dave Hallowell wrote: Glad to hear it worked. Now that you have the spec file patched, you can create a new patch for others so they do not have to go through the same process. Move the patched spec file to a new name, and then install the .src.rpm again. Then from the SOURCES dir run: diff -Naur qmail-toaster.spec modified-qmail-toaster.spec empF-1.3.16.patch That will give you a patch (empF-1.3.16.patch) that will apply cleanly to the new version of qmail-toaster. Post it back so others can obtain it, and update the wiki. You're now an official contributor! Jake, Please excuse my newbieness. I have created the patch file for empF as you described. I have tested my patch and it works on my system following the current wiki using my patch in step 4 versus the stated patch. What do you mean "Post it back"? Do you mean just copy and paste the contents of the patch here in an email or something else? Also, isn't this a patch just for those wanting empF on centos4 running qmail-toaster-1.03-1.3.16 (with the offending libraries). If so, do I just append my notes to the current wiki entry? I am a little hesitate since I have never done this before. I want to get this right. thanks, Depending on how you edited the patch, it should allow anyone who wants empF to use it. If you'd like you can send me the patch (compressed, zip, gzip, or bzip2) and I'll make sure that it applies cleanly and link it somewhere so that those reading the wiki can download it and use it. Jake , I will try to get this ready today and send to you. Thanks, Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com Jake, I have attached the patch. I followed the Installing EMPF patch on the qmail wiki. Just replace 1.3.15 with 1.3.16. I had an error when I ran step 6, rpm -Uvh --replacefiles --replacepkgs qmail-toaster*.rpm qmail-pop3d*.rpm. I had an additional failed dependency with openssl = 0.9.8. I had to redo my patch and edit the %default line requiring openssl since the lastest version of openssl for cnt4 is 0.9.7. I then recreated my patch. I still get a warning when I run step 6. I don't know what it means. It installs and qmail-toaster works. Maybe when you test it you can let me know what it means and what I need to do to fix it. This is the warning: "warning: package qmail-pop3d-toaster = 1.03-1.3.15 was already added, replacing with qmail-pop3d-toaster = 1.03-1.3.16". It all seems to be working fine. Dave 1.3.16.tar.bz2 Description: Binary data - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
2009/4/8 Dave Hallowell d...@acbsco.com: Dave Hallowell wrote: Jake Vickers wrote: Dave Hallowell wrote: Glad to hear it worked. Now that you have the spec file patched, you can create a new patch for others so they do not have to go through the same process. Move the patched spec file to a new name, and then install the .src.rpm again. Then from the SOURCES dir run: diff -Naur qmail-toaster.spec modified-qmail-toaster.spec empF-1.3.16.patch That will give you a patch (empF-1.3.16.patch) that will apply cleanly to the new version of qmail-toaster. Post it back so others can obtain it, and update the wiki. You're now an official contributor! Jake, Please excuse my newbieness. I have created the patch file for empF as you described. I have tested my patch and it works on my system following the current wiki using my patch in step 4 versus the stated patch. What do you mean Post it back? Do you mean just copy and paste the contents of the patch here in an email or something else? Also, isn't this a patch just for those wanting empF on centos4 running qmail-toaster-1.03-1.3.16 (with the offending libraries). If so, do I just append my notes to the current wiki entry? I am a little hesitate since I have never done this before. I want to get this right. thanks, Depending on how you edited the patch, it should allow anyone who wants empF to use it. If you'd like you can send me the patch (compressed, zip, gzip, or bzip2) and I'll make sure that it applies cleanly and link it somewhere so that those reading the wiki can download it and use it. Jake , I will try to get this ready today and send to you. Thanks, Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com Jake, I have attached the patch. I followed the Installing EMPF patch on the qmail wiki. Just replace 1.3.15 with 1.3.16. I had an error when I ran step 6, rpm -Uvh --replacefiles --replacepkgs qmail-toaster*.rpm qmail-pop3d*.rpm. I had an additional failed dependency with openssl = 0.9.8. I had to redo my patch and edit the %default line requiring openssl since the lastest version of openssl for cnt4 is 0.9.7. I then recreated my patch. I still get a warning when I run step 6. I don't know what it means. It installs and qmail-toaster works. Maybe when you test it you can let me know what it means and what I need to do to fix it. This is the warning: warning: package qmail-pop3d-toaster = 1.03-1.3.15 was already added, replacing with qmail-pop3d-toaster = 1.03-1.3.16. It all seems to be working fine. Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com Hi all, I miss the most of the comotion arround eMPF (work...) but I've to point out the following: The eMPF patch in itself should always apply error free in any netqmail based qmail. There are some issues with SRS, mainly because rules DO NOT take it in cosideration... (code change is required) If no rules are defined or policy file doesn't exist eMPF takes no action. Some defaults (string max size for instance) need to be changed considering the number of rules, server load and max memory available for qmail-smtpd (particulary in 64bits systems). Other then the above it should work just fine. I'll have a look at current qmt release and check for dependencies for all distros and change some defaults, and then post a final revise of it. -- AM agmsoft(at)gmail.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
A M wrote: Hi all, I miss the most of the comotion arround eMPF (work...) but I've to point out the following: The eMPF patch in itself should always apply error free in any netqmail based qmail. There are some issues with SRS, mainly because rules DO NOT take it in cosideration... (code change is required) If no rules are defined or policy file doesn't exist eMPF takes no action. Some defaults (string max size for instance) need to be changed considering the number of rules, server load and max memory available for qmail-smtpd (particulary in 64bits systems). Other then the above it should work just fine. I'll have a look at current qmt release and check for dependencies for all distros and change some defaults, and then post a final revise of it. How long have you been running the patch? I'm just loathe to add a patch that I really don't have time to trouble shoot at this point, especially if it has not been tested in length and make cause issues with other things. Once thing I've learned programming in Linux, PIC, and AVR, is that adding a new feature may seem like a good idea now but may cause you an issue later that was completely unforeseen. Thanks. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
Jake Vickers wrote: A M wrote: Hi all, I miss the most of the comotion arround eMPF (work...) but I've to point out the following: The eMPF patch in itself should always apply error free in any netqmail based qmail. There are some issues with SRS, mainly because rules DO NOT take it in cosideration... (code change is required) If no rules are defined or policy file doesn't exist eMPF takes no action. Some defaults (string max size for instance) need to be changed considering the number of rules, server load and max memory available for qmail-smtpd (particulary in 64bits systems). Other then the above it should work just fine. I'll have a look at current qmt release and check for dependencies for all distros and change some defaults, and then post a final revise of it. How long have you been running the patch? I'm just loathe to add a patch that I really don't have time to trouble shoot at this point, especially if it has not been tested in length and make cause issues with other things. Once thing I've learned programming in Linux, PIC, and AVR, is that adding a new feature may seem like a good idea now but may cause you an issue later that was completely unforeseen. Thanks. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com Jake, Are you asking me or A.M. these questions? Dave - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
On Wed, Apr 8, 2009 at 9:38 PM, Jake Vickers j...@qmailtoaster.com wrote: A M wrote: Hi all, I miss the most of the comotion arround eMPF (work...) but I've to point out the following: The eMPF patch in itself should always apply error free in any netqmail based qmail. There are some issues with SRS, mainly because rules DO NOT take it in cosideration... (code change is required) If no rules are defined or policy file doesn't exist eMPF takes no action. Some defaults (string max size for instance) need to be changed considering the number of rules, server load and max memory available for qmail-smtpd (particulary in 64bits systems). Other then the above it should work just fine. I'll have a look at current qmt release and check for dependencies for all distros and change some defaults, and then post a final revise of it. How long have you been running the patch? I'm just loathe to add a patch that I really don't have time to trouble shoot at this point, especially if it has not been tested in length and make cause issues with other things. Once thing I've learned programming in Linux, PIC, and AVR, is that adding a new feature may seem like a good idea now but may cause you an issue later that was completely unforeseen. Thanks. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group ( www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com I just want to say that under the current scenario of e-mail security the lack of a messaging policy framework puts qmailtoaster at a disadvantage. These days mail servers are expected to enforce policies restricting users from sending mail to all and sundry. I've been trying to get it to work for me but unfortunately it hasn't. I think it did not work because I tried it in spite of the error with the patch. I was a little desperate I guess. I want to be able to specify in the 'policy' users who can send mail only to specified domains and e-mail id's. Is this possible with a error free patch of the source and rebuild of qmail-toaster? Thank you Khan Md.Ashraf
Re: [qmailtoaster] empF patch
Dave Hallowell wrote: How long have you been running the patch? I'm just loathe to add a patch that I really don't have time to trouble shoot at this point, especially if it has not been tested in length and make cause issues with other things. Once thing I've learned programming in Linux, PIC, and AVR, is that adding a new feature may seem like a good idea now but may cause you an issue later that was completely unforeseen. Thanks. Jake, Are you asking me or A.M. these questions? Dave Either, or, both. Whoever can say how long they have been running the patch and what pitfalls they may have run into. I imagine you've only been running it a couple days, correct Dave? - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] empF patch
Hi Jake, that would be correct. I created the empf patch yesterday and placed into production yesterday. That was my very first attempt at creating the patch. It is by no means stable. I was simply following your suggestion to make it available to others. I understand and do not expect you to debug it. Maybe the best option is to wait for A.M. to create a patch and then reconsider putting it where others can get to it. In the meantime, its working for me. Since A.M. seems to monitor this list infrequently, maybe I will post something on the empf mailing list and see what type of response I get. Thanks for your help. If you have any suggestions, I would be glad to give it a whirl. Dave Jake Vickers wrote: Dave Hallowell wrote: How long have you been running the patch? I'm just loathe to add a patch that I really don't have time to trouble shoot at this point, especially if it has not been tested in length and make cause issues with other things. Once thing I've learned programming in Linux, PIC, and AVR, is that adding a new feature may seem like a good idea now but may cause you an issue later that was completely unforeseen. Thanks. Jake, Are you asking me or A.M. these questions? Dave Either, or, both. Whoever can say how long they have been running the patch and what pitfalls they may have run into. I imagine you've only been running it a couple days, correct Dave? - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] Auto Whitelist
I am getting messages about the auto whitelist yet I do not have that
feature enabled in my local.cf. How do I disable it and get this out of my
logs?
@400049dcf0ab20ea00a4 [9544] info: config: failed to parse line,
skipping, in (no file): use_auto_whitelist 1
@400049dcf0ab25aab14c [9545] info: config: failed to parse line,
skipping, in (no file): use_auto_whitelist 1
I cannot find where the line use_auto_whitelist 1 is.
Gilbert
local.cf file...
# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)
# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.
# Add MySQL User Support
user_scores_dsn DBI:mysql:spamassassin:127.0.0.1
user_scores_sql_password ***
user_scores_sql_username ***
user_scores_sql_custom_query SELECT preference, value FROM _TABLE_ WHERE
use
rname = _USERNAME_ OR username = '$GLOBAL' OR username =
CONCAT('%',_DOMAIN_) OR
DER BY username ASC
# Enable Bayes filtering and storage in MySQL
bayes_store_module Mail::SpamAssassin::BayesStore::MySQL
bayes_sql_dsn DBI:mysql:spamassassin:127.0.0.1
bayes_sql_username ***
bayes_sql_password ***
bayes_sql_override_username root
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 0
ok_locales all
skip_rbl_checks 0
required_score 4
report_safe 0
rewrite_header Subject ***SPAM***
use_pyzor 1
pyzor_timeout 15
pyzor_options --homedir /etc/mail/spamassassin/.pyzor
use_dcc 1
dcc_path /usr/local/bin/dccproc
use_razor2 1
razor_config /etc/mail/spamassassin/.razor/razor-agent.conf
-
Managed Qmailtoaster servers are now available
Visit http://qmailtoaster.com/QMTManaged.html to order yours today!
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Auto Whitelist
I figured out where I was having the problem with this. I had this set as a
$GLOBAL in my mysql table that is used to override my default spamassassin
rules.
Gilbert
- Original Message -
From: Gilbert T. Gutierrez, Jr. mailing-li...@phoenixinternet.net
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, April 08, 2009 11:50 AM
Subject: [qmailtoaster] Auto Whitelist
I am getting messages about the auto whitelist yet I do not have that
feature enabled in my local.cf. How do I disable it and get this out of my
logs?
@400049dcf0ab20ea00a4 [9544] info: config: failed to parse line,
skipping, in (no file): use_auto_whitelist 1
@400049dcf0ab25aab14c [9545] info: config: failed to parse line,
skipping, in (no file): use_auto_whitelist 1
I cannot find where the line use_auto_whitelist 1 is.
Gilbert
local.cf file...
# These values can be overridden by editing ~/.spamassassin/user_prefs.cf
# (see spamassassin(1) for details)
# These should be safe assumptions and allow for simple visual sifting
# without risking lost emails.
# Add MySQL User Support
user_scores_dsn DBI:mysql:spamassassin:127.0.0.1
user_scores_sql_password ***
user_scores_sql_username ***
user_scores_sql_custom_query SELECT preference, value FROM _TABLE_
WHERE use
rname = _USERNAME_ OR username = '$GLOBAL' OR username =
CONCAT('%',_DOMAIN_) OR
DER BY username ASC
# Enable Bayes filtering and storage in MySQL
bayes_store_module Mail::SpamAssassin::BayesStore::MySQL
bayes_sql_dsn DBI:mysql:spamassassin:127.0.0.1
bayes_sql_username ***
bayes_sql_password ***
bayes_sql_override_username root
use_bayes 1
use_bayes_rules 1
bayes_auto_learn 0
ok_locales all
skip_rbl_checks 0
required_score 4
report_safe 0
rewrite_header Subject ***SPAM***
use_pyzor 1
pyzor_timeout 15
pyzor_options --homedir /etc/mail/spamassassin/.pyzor
use_dcc 1
dcc_path /usr/local/bin/dccproc
use_razor2 1
razor_config /etc/mail/spamassassin/.razor/razor-agent.conf
-
Managed Qmailtoaster servers are now available
Visit http://qmailtoaster.com/QMTManaged.html to order yours today!
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Please visit qmailtoaster.com for the latest news, updates, and
packages.
To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com
-
Managed Qmailtoaster servers are now available
Visit http://qmailtoaster.com/QMTManaged.html to order yours today!
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] CLAM
It appears we have now moved to 95.1 Gilbert - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
[qmailtoaster] Sandbox Upgrade Fail
Greetings All, I've just attempted to run qtp-newmodel on a CentOS 5.3 box. All appeared to be going well until the build of 'spamassassin-toaster': On my console, I got: - Building spamassassin-toaster-3.2.5-1.3.15 ... Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. - And from the build-recent.log, I got: - Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(Archive::Tar) = 1.23 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(IO::Zlib) = 1.04 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 - Now I can build and install the missing perl modules separately, either by hand or via the CPAN system. But I seem to remember seeing something about CPAN built/installed modules creating a problem for the toaster. Is there a preferred approach to resolving this dependency error? TIA, --Duncan - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Temporarily Hand Off/Ignore All Email For One Forward?
Thanks for your reply, Jake. We figured out what the problem was. One our less clueful users had done two things to make a bit of a mess: 1) Set up a forward that was directed to both a remote address *and* back to the forward itself(!) and 2) Set up the same account as a 'catch-all' account. Once these two conditions were corrected, the flood of SPAM stopped, we cleaned out the queue and all is well again. Anway, thanks again for your help. --Duncan Jake Vickers wrote: Duncan Sterling wrote: Greetings All, In the past 24 hours, I've had to fend off somewhere north of 50,000 emails to one single forward in one of our vdomains. In this vdomain are 4 regular accounts, several of which forward to a forward in the same vdomain, which in turn directs mail to another SMTP server. Most of the SPAM coming in is addressed to this single forward. So, the questions is, other than the obvious move of disabling the forward until things quiet down, or smptforwarding the entire vdomain to the client's SMPT server, is it possible to selectively ignore/forward only the inbound emails addressed to the single troublesome forward in this vdomain? TIA, You could probably use badmailto and filter what you want that way. Just put the address you do not want to accept mail for in the file, if that's what you're asking. Otherwise I may be misinterpreting what you're trying to accomplish. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] CLAM
Gilbert T. Gutierrez, Jr. wrote: It appears we have now moved to 95.1 Gilbert Saw that on the list earlier today. I'll work on getting a package up in the next couple days. This version was only a bug fix version that did not involve anything that pertains to how QMT uses it, so it's not a critical update or security fix. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Sandbox Upgrade Fail
Duncan Sterling wrote: Greetings All, I've just attempted to run qtp-newmodel on a CentOS 5.3 box. All appeared to be going well until the build of 'spamassassin-toaster': On my console, I got: - Building spamassassin-toaster-3.2.5-1.3.15 ... Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. - And from the build-recent.log, I got: - Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(Archive::Tar) = 1.23 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(IO::Zlib) = 1.04 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 - Now I can build and install the missing perl modules separately, either by hand or via the CPAN system. But I seem to remember seeing something about CPAN built/installed modules creating a problem for the toaster. Is there a preferred approach to resolving this dependency error? What version of QTP are you running? There was a new version released a couple days ago that installs the perl packages using yum in a new way. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Mail archiving using taps
Can i use procmail for this purpose? means, can i write userwise rules in procmail? Thanks and Regards, S.Senthilvel, On Sun, Apr 5, 2009 at 6:11 AM, Jake Vickers j...@qmailtoaster.com wrote: senthil vel wrote: Thanks Jake.. Can you please show me a direction to write a script for this? Not really without actually doing it for you. You'd need to work some logic that forks a copy of all incoming mail for a user and copy it to another folder. Same with the outgoing. - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Sandbox Upgrade Fail
Jake Vickers wrote: Duncan Sterling wrote: Greetings All, I've just attempted to run qtp-newmodel on a CentOS 5.3 box. All appeared to be going well until the build of 'spamassassin-toaster': On my console, I got: - Building spamassassin-toaster-3.2.5-1.3.15 ... Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. - And from the build-recent.log, I got: - Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(Archive::Tar) = 1.23 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(IO::Zlib) = 1.04 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 - Now I can build and install the missing perl modules separately, either by hand or via the CPAN system. But I seem to remember seeing something about CPAN built/installed modules creating a problem for the toaster. Is there a preferred approach to resolving this dependency error? What version of QTP are you running? There was a new version released a couple days ago that installs the perl packages using yum in a new way. qmailtoaster-plus-0.2.14-1.3.18 --Duncan No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.285 / Virus Database: 270.11.47/2047 - Release Date: 04/08/09 05:53:00 - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
Re: [qmailtoaster] Sandbox Upgrade Fail
Jake Vickers wrote: Duncan Sterling wrote: Greetings All, I've just attempted to run qtp-newmodel on a CentOS 5.3 box. All appeared to be going well until the build of 'spamassassin-toaster': On my console, I got: - Building spamassassin-toaster-3.2.5-1.3.15 ... Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15 qtp-build-rpms - see /opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log Build failed, Exiting. - And from the build-recent.log, I got: - Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ... error: Failed dependencies: perl(Archive::Tar) = 1.23 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(IO::Zlib) = 1.04 is needed by spamassassin-toaster-3.2.5-1.3.15.i686 perl(LWP::UserAgent) is needed by spamassassin-toaster-3.2.5-1.3.15.i686 - Now I can build and install the missing perl modules separately, either by hand or via the CPAN system. But I seem to remember seeing something about CPAN built/installed modules creating a problem for the toaster. Is there a preferred approach to resolving this dependency error? What version of QTP are you running? There was a new version released a couple days ago that installs the perl packages using yum in a new way. I was definitely a version back. I'll try the new QTP newmodel and see if that resolves the perl dependencies issue. Thanks, --Duncan No virus found in this outgoing message. Checked by AVG - www.avg.com Version: 8.5.285 / Virus Database: 270.11.47/2047 - Release Date: 04/08/09 05:53:00 - Managed Qmailtoaster servers are now available Visit http://qmailtoaster.com/QMTManaged.html to order yours today! Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com For additional commands, e-mail: testing-h...@qmailtoaster.com
