Re: courier-mta + amavisd-new + spamassassin
On Wednesday 24 November 2004 00:39, Horst Bursik wrote: On Tue, 23 Nov 2004 13:20:14 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: I have placed them at http://www.sentinel.dk/files/ Thanks to you i found the problem: The following lines from amavisd.conf are verry important and are commented out by default: $mailfrom_notify_admin = [EMAIL PROTECTED]; $mailfrom_notify_recip = [EMAIL PROTECTED]; Thats the only think, that was/is missing in your howto. I'll make sure to emphasize these two settings next time I update my recipe. Thanks. Is amavis in your setup able to add additional header fields? Come to think of it, I think you're right. I believe amavisd-new is not able to rewrite the header. Anyway, I just throw away any mail that is infected. I don't notice sender and recipient, or anybody else. I did a little research and its by design, that courier does not allow any email modification (header rewriting or what ever) until the message leaves the mta. Modifing can only be accomplished by the mda witch normaly means maildrop filter configuration. Anyway i realy have to thank you for your help! No problem. I'm glad I could help. -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
Hi Horst, On Monday 22 November 2004 21:39, Horst Bursik wrote: Hi, Frederik, I tested it with your 'recipe' but unfortunately it won't work. Amavis is not able to rewrite the emails because SEND via PIPE returns always: 550 5.1.1 Recipient unknown. But the recipient is of course working if I turn amavis of or if it didn't find anything. Could it be that the email address defined in $mailfrom_notify_admin or $mailfrom_notify_recip is incorrect? Is it possible, that you send me your amavisd.conf and/or your amavisd-new binary for comparing? I have placed them at http://www.sentinel.dk/files/ I followed your recipe step by step and checked it about 10 times but somewhere with the filtering there must be a mistake or something missing. On Sun, 21 Nov 2004 23:00:16 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: I haven't noticed any limitations in my particular setup, but on the other hand, I may not be using features that you may want to use. Is amavis in your setup able to add additional header fields? Come to think of it, I think you're right. I believe amavisd-new is not able to rewrite the header. Anyway, I just throw away any mail that is infected. I don't notice sender and recipient, or anybody else. -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
On Monday 22 November 2004 22:04, Horst Bursik wrote: Some Add-ons Information: I just turned the debugging output to the highest level and found the problem (although i was not able to solve it yet). Amavis says the following in its log: ---snip--- Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) SEND via PIPE: - [EMAIL PROTECTED] Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) mail_via_pipe running command: /usr/sbin/sendmail -f -- [EMAIL PROTECTED] Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) one_response_for_all : REJECTs, '550 5.1.1 Recipient unknown, id=2618-1' ---snip--- so it looks like courier is not passing the sender to amavis. Does anybody have an idea where i can point the problem? Is [EMAIL PROTECTED] actually a valid mail address that your mail server will accept mails for? -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
On Tue, 23 Nov 2004 13:30:07 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: Is [EMAIL PROTECTED] actually a valid mail address that your mail server will accept mails for? Yes it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
On Tue, 23 Nov 2004 13:20:14 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: I have placed them at http://www.sentinel.dk/files/ Thanks to you i found the problem: The following lines from amavisd.conf are verry important and are commented out by default: $mailfrom_notify_admin = [EMAIL PROTECTED]; $mailfrom_notify_recip = [EMAIL PROTECTED]; Thats the only think, that was/is missing in your howto. Is amavis in your setup able to add additional header fields? Come to think of it, I think you're right. I believe amavisd-new is not able to rewrite the header. Anyway, I just throw away any mail that is infected. I don't notice sender and recipient, or anybody else. I did a little research and its by design, that courier does not allow any email modification (header rewriting or what ever) until the message leaves the mta. Modifing can only be accomplished by the mda witch normaly means maildrop filter configuration. Anyway i realy have to thank you for your help! Ciao, Horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
Hi, Frederik, I tested it with your 'recipe' but unfortunately it won't work. Amavis is not able to rewrite the emails because SEND via PIPE returns always: 550 5.1.1 Recipient unknown. But the recipient is of course working if I turn amavis of or if it didn't find anything. Is it possible, that you send me your amavisd.conf and/or your amavisd-new binary for comparing? I followed your recipe step by step and checked it about 10 times but somewhere with the filtering there must be a mistake or something missing. On Sun, 21 Nov 2004 23:00:16 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: I haven't noticed any limitations in my particular setup, but on the other hand, I may not be using features that you may want to use. Is amavis in your setup able to add additional header fields? Thanks for your help, Horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
Some Add-ons Information: I just turned the debugging output to the highest level and found the problem (although i was not able to solve it yet). Amavis says the following in its log: ---snip--- Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) SEND via PIPE: - [EMAIL PROTECTED] Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) mail_via_pipe running command: /usr/sbin/sendmail -f -- [EMAIL PROTECTED] Nov 22 21:58:21 voyager amavisd-new[2618]: (2618-1) one_response_for_all : REJECTs, '550 5.1.1 Recipient unknown, id=2618-1' ---snip--- so it looks like courier is not passing the sender to amavis. Does anybody have an idea where i can point the problem? Cheers, Horst On Mon, 22 Nov 2004 22:00:18 +0100, Horst Bursik [EMAIL PROTECTED] wrote: Hi, Frederik, I tested it with your 'recipe' but unfortunately it won't work. Amavis is not able to rewrite the emails because SEND via PIPE returns always: 550 5.1.1 Recipient unknown. But the recipient is of course working if I turn amavis of or if it didn't find anything. Is it possible, that you send me your amavisd.conf and/or your amavisd-new binary for comparing? I followed your recipe step by step and checked it about 10 times but somewhere with the filtering there must be a mistake or something missing. On Sun, 21 Nov 2004 23:00:16 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: I haven't noticed any limitations in my particular setup, but on the other hand, I may not be using features that you may want to use. Is amavis in your setup able to add additional header fields? Thanks for your help, Horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
On Sun, 21 Nov 2004 00:10:10 +0100, Mark Maas [EMAIL PROTECTED] wrote: Hi Mark, central point. But take a look at LDAP. With LDAP you can do the same things and also do future things from this one database. Creating a single-sign-on environment for your users. I considered moving the user information to a MySQL or LDAP Server but I'm searching for a setup which I can implement at some customers and I think some of them would see it as overkill if I for example setup an ldap/sql server for only 5 users. Do you know a tool like phpMyAdmin for LDAP? Because some customers can be convinced with graphical tools ;-) The courier MTA was made by them to indeed fulfill the demand for everything from one distribution point. And although it eases the integration, you get the idea there not using standards for it. Yes, that's right. And although I like courier, I must admit, that the configuration is very unlikely like every other mta I ever configured. Hehe, it took me a while before switching from Sendmail as well. Exim is a breaze compared to Sendmail. And a LOT better in security! The Security issues with sendmail where also my motivation to switch because if found courier is designed very secure. It seems that you know courier as well as exim - is the security compareable? Maildrop and .forward files (exim's own filtering language real easy to understand compared to procmail), and procmail. Users can use any of these. Web interfaces make creating rules easy for users. That sounds sexy! As a side effect when users want to report spam to me, they send it to a special spam email adress. This email then gets fed in to there spamassassin database. Thereby strengthening spamassassin for the next similar spam that comes along. This is done with procmail recipies. And this even more! You offered to send me your exim configuration. If this offer still stands I would like to accept it? Cheers, Horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
Hi Frederik, Thank you very much for your notes - I'll give them a try in the next days and let you know if I find something that may be not in your notes. On Sun, 21 Nov 2004 03:10:10 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: mention. Maybe you can use some of it, maybe you can't. The patch I refer to is a slightly edited version of the courier patch that is included in the amavisd-new Debian package. I had to slighty adjust the pacth here and there - otherwise it would not apply cleanly (maybe this has changed since I did my install?). Do you still have the adjusted patch or is http://sentinel.dk/linux/debian/patches/amavisd-new-courier-debian.patch already the modified version? Did amavisd-new in your setup work with full features? Or are there some limitations? Cheers, Horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
On Sunday 21 November 2004 21:45, Horst Bursik wrote: Hi Frederik, Thank you very much for your notes - I'll give them a try in the next days and let you know if I find something that may be not in your notes. On Sun, 21 Nov 2004 03:10:10 +0100, Frederik Dannemare [EMAIL PROTECTED] wrote: mention. Maybe you can use some of it, maybe you can't. The patch I refer to is a slightly edited version of the courier patch that is included in the amavisd-new Debian package. I had to slighty adjust the pacth here and there - otherwise it would not apply cleanly (maybe this has changed since I did my install?). Do you still have the adjusted patch or is http://sentinel.dk/linux/debian/patches/amavisd-new-courier-debian.pa tch already the modified version? Yes, http://sentinel.dk/linux/debian/patches/amavisd-new-courier-debian.patch is my modified version of the original courier patch. My modified patch will apply cleanly to the amavisd-new sources in Debian, whereas the original patch (named amavisd-new-courier.patch) does not apply cleanly, simply because the Debian package maintainers of amavisd-new have made small changes to the amavisd-new sources (which the original courier patch, of course, does not know about). Did amavisd-new in your setup work with full features? Or are there some limitations? I haven't noticed any limitations in my particular setup, but on the other hand, I may not be using features that you may want to use. -- Frederik Dannemare | mailto:[EMAIL PROTECTED] http://qa.debian.org/developer.php?login=Frederik+Dannemare http://frederik.dannemare.net | http://www.linuxworlddomination.dk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
courier-mta + amavisd-new + spamassassin
hi, Does anybody have experiences with courier-mta + amavisd-new + spamassassin? Amavisd-new works great with postfix and sendmail but the last time i tried to use amavisd-new in combination with courier it was nearly impossible. With a lot of hacks in the amavis-code i accomplished what i wanted but it's far away from a clean setup and most important: i could only use parts of the full amavis functionality. This was half a year ago and hopefully there had been some improvements in either amavis or courier, or someone with more perl-experience than I found a solution? I couldn't find anything useful in the web so I'm trying it here. If anyone can give me some tips i would be very grateful. tia, horst -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: courier-mta + amavisd-new + spamassassin
Hi Horst! I saw I did not include debian-users in my previous email. sorry about that... Horst Bursik wrote: Hi Mark, Thanks a lot for your answer! I'm using courier because the courier-packages includes everything from one source. I have the user information stored in couriers userdb an every component of courier (mta for smtpauth, pop3d, imapd) authenticates against this db. This is important for me because I don't want to manage the users in more than one db. I tried once to use postfix instead of courier which ended up in a clean setup with amavis working fine but to get smtpauth working I had to build second userdb. Yeah, indeed it is a sweet setup if everything can be done from one central point. But take a look at LDAP. With LDAP you can do the same things and also do future things from this one database. Creating a single-sign-on environment for your users. Postfix, Sendmail and Exim can read from ldap as well. Courier does imap and pop best. Exim does SMTP transport the best. And all that comes with it. The courier MTA was made by them to indeed fulfill the demand for everything from one distribution point. And although it eases the integration, you get the idea there not using standards for it. As long as everyone uses standards, integration becomes standard as well.. And Exim is as standard compliant as they come. I just had a deep look on the exim website and it's absolutely worth considering exim! I must admit, that I didn't have a look at exim so far. I always replaced it with courier without looking how exim works and what it can. *shame on me* ;-) Hehe, it took me a while before switching from Sendmail as well. Exim is a breaze compared to Sendmail. And a LOT better in security! How is your setup exactly working? If i understand you correct you have: exim as mta Yes. maildrop as mda? Maildrop and .forward files (exim's own filtering language real easy to understand compared to procmail), and procmail. Users can use any of these. Web interfaces make creating rules easy for users. As a side effect when users want to report spam to me, they send it to a special spam email adress. This email then gets fed in to there spamassassin database. Thereby strengthening spamassassin for the next similar spam that comes along. This is done with procmail recipies. courier-imap as pop3/imap daemon True. amavisd-new + f-prot + spamassassin for content filtering Yep, and also clamav antivirus. I use two scanners! Right? Are you using SMTP AUTH and if so, where does your exim gets the user information from? Does it have it's own userdb or is it possible to use couriers userdb? Or have you stored both in a MySQL database? SMTP auth via plain but also ssl, and tls. Users/passwords come from LDAP. Tnx again for your help! No thanks! Cheers, Horst Later, Mark begin:vcard fn:Mark Maas n:Maas;Mark adr;dom:;;;Amsterdam email;internet:[EMAIL PROTECTED] title:Systems Admin note;quoted-printable:-BEGIN PGP PUBLIC KEY BLOCK-=0D=0A= Version: GnuPG v1.2.4 (GNU/Linux)=0D=0A= =0D=0A= mQGiBEF/9pMRBADvHSlIl47a4t7phWb0zzHHlZDDJmBfdzKq6bBDofinF16u6Wig=0D=0A= C67aFPVu2eTDB7yhpVskL4e4eUpS8acS1NWfaBbbVFZv+JUXW1szD1rjmdH7XI0w=0D=0A= XxEHvO/TbyOK6UiIauVDDO2hdiTFas8xl5rUkJC7dyEJqYiVbXmgoszu4wCg37xP=0D=0A= l4Jkap0dD0o3a4XuJ7c4C+0EAJSEmDu91BMvVNwUl7rFbnfOT1S/hOGUaXuUY7fn=0D=0A= em0WoTFxVISKJH6r6nquSr+Dn8jljJM8Oe/4XIAgRpQ4kIupnoHHhSFd6P0W2InV=0D=0A= Zrm/t2AnhV66+dxpjz+2mJvuEssG31AzAGPFfweRnBenQvThKD1SpEd+Au3rO+0H=0D=0A= 4qZrA/9Hb1DiqcQO3vjtyWA4DdsPd92H121l491Vaqdy+6IRTDo6oDvqI3EfZshC=0D=0A= DIwNJUbXt0EjN1Xa44+gIaSFmgpJcG1M0w22XH47tbs0CQ7yQ3KyBA9VbdozchtS=0D=0A= HLz6WPVKNaDBAzFFOAYvWkR9h1IAQOc4UycHQDia60BhxSkRILYeTWFyayBN=0D=0A= YWFzIDxtYXJrQG1lbmVtLm1pbmUubnU+iFsEExECABsFAkF/9pMGCwkIBwMCAxUC=0D=0A= AwMWAgECHgECF4AACgkQ8SFyUHWnEvOObQCdEGDR7oR//IVVAynpWrpFuc5Xt0gA=0D=0A= oKzSyqPzoDXekHqBm/4BHwThpJhKuQENBEF/9p8QBACOazsQm/Fb9bBmQnxJ906W=0D=0A= NSPYn9Q1a8YdqqpJC2J0ezDioJOi2+629jeNrmQsCGYGWPsvQzQhaQ2u2IS3s5OX=0D=0A= M8HWOuNKtZyqUL+sf8Gr+PFmXxAFykXmfP299lI8LhqGJTZPHU7SQhtC+i1vmp3C=0D=0A= kTABetoHfafUSVyuMXg53wADBQQAhYjdoMmzMDyD+v8s4/9iMJWaP7pMtEWZsD2n=0D=0A= XWtbGLuazNn0xDc7kp5nAfwBlOeYVEPIEUYsYxbYLZ6HxOtvA8VihXV2hViB/13X=0D=0A= cYCT7Uo1TH/ON/CHyJ+lv0IqJmYprb+VEO+BMcweGs2/Ky0ubkwP9kGyXT+FJKqT=0D=0A= BEjl7UiIRgQYEQIABgUCQX/2nwAKCRDxIXJQdacS84/RAJ4yvx+rHKvink2f7a08=0D=0A= n5KyrxUNGgCePtpx7JBDLp2S+jmk5ua336yL6sY=3D=0D=0A= =3D7X3V=0D=0A= -END PGP PUBLIC KEY BLOCK-=0D=0A= x-mozilla-html:FALSE version:2.1 end:vcard
Re: courier-mta + amavisd-new + spamassassin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Horst! I saw I did not include debian-users in my previous email. sorry about that... Horst Bursik wrote: | | Hi Mark, | | Thanks a lot for your answer! | | I'm using courier because the courier-packages includes everything from | one source. I have the user information stored in couriers userdb an | every component of courier (mta for smtpauth, pop3d, imapd) | authenticates against this db. This is important for me because I don't | want to manage the users in more than one db. I tried once to use | postfix instead of courier which ended up in a clean setup with amavis | working fine but to get smtpauth working I had to build second userdb. | Yeah, indeed it is a sweet setup if everything can be done from one central point. But take a look at LDAP. With LDAP you can do the same things and also do future things from this one database. Creating a single-sign-on environment for your users. Postfix, Sendmail and Exim can read from ldap as well. Courier does imap and pop best. Exim does SMTP transport the best. And all that comes with it. The courier MTA was made by them to indeed fulfill the demand for everything from one distribution point. And although it eases the integration, you get the idea there not using standards for it. As long as everyone uses standards, integration becomes standard as well.. And Exim is as standard compliant as they come. | I just had a deep look on the exim website and it's absolutely worth | considering exim! I must admit, that I didn't have a look at exim so | far. I always replaced it with courier without looking how exim works | and what it can. *shame on me* ;-) | Hehe, it took me a while before switching from Sendmail as well. Exim is a breaze compared to Sendmail. And a LOT better in security! | | How is your setup exactly working? If i understand you correct you have: | | exim as mta Yes. | maildrop as mda? Maildrop and .forward files (exim's own filtering language real easy to understand compared to procmail), and procmail. Users can use any of these. Web interfaces make creating rules easy for users. As a side effect when users want to report spam to me, they send it to a special spam email adress. This email then gets fed in to there spamassassin database. Thereby strengthening spamassassin for the next similar spam that comes along. This is done with procmail recipies. | courier-imap as pop3/imap daemon True. | amavisd-new + f-prot + spamassassin for content filtering Yep, and also clamav antivirus. I use two scanners! | | Right? | | Are you using SMTP AUTH and if so, where does your exim gets the user | information from? Does it have it's own userdb or is it possible to use | couriers userdb? Or have you stored both in a MySQL database? SMTP auth via plain but also ssl, and tls. Users/passwords come from ~ LDAP. | | Tnx again for your help! | No thanks! | Cheers, | Horst | Later, Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBn84t8SFyUHWnEvMRAt/xAKCMsbmWhYn02WIA0WZyAa7sRjBV3QCg2Cfg DAQx88pA57qM6EB9kjiFbPk= =XJDC -END PGP SIGNATURE- begin:vcard fn:Mark Maas n:Maas;Mark adr;dom:;;;Amsterdam email;internet:[EMAIL PROTECTED] title:Systems Admin note;quoted-printable:-BEGIN PGP PUBLIC KEY BLOCK-=0D=0A= Version: GnuPG v1.2.4 (GNU/Linux)=0D=0A= =0D=0A= mQGiBEF/9pMRBADvHSlIl47a4t7phWb0zzHHlZDDJmBfdzKq6bBDofinF16u6Wig=0D=0A= C67aFPVu2eTDB7yhpVskL4e4eUpS8acS1NWfaBbbVFZv+JUXW1szD1rjmdH7XI0w=0D=0A= XxEHvO/TbyOK6UiIauVDDO2hdiTFas8xl5rUkJC7dyEJqYiVbXmgoszu4wCg37xP=0D=0A= l4Jkap0dD0o3a4XuJ7c4C+0EAJSEmDu91BMvVNwUl7rFbnfOT1S/hOGUaXuUY7fn=0D=0A= em0WoTFxVISKJH6r6nquSr+Dn8jljJM8Oe/4XIAgRpQ4kIupnoHHhSFd6P0W2InV=0D=0A= Zrm/t2AnhV66+dxpjz+2mJvuEssG31AzAGPFfweRnBenQvThKD1SpEd+Au3rO+0H=0D=0A= 4qZrA/9Hb1DiqcQO3vjtyWA4DdsPd92H121l491Vaqdy+6IRTDo6oDvqI3EfZshC=0D=0A= DIwNJUbXt0EjN1Xa44+gIaSFmgpJcG1M0w22XH47tbs0CQ7yQ3KyBA9VbdozchtS=0D=0A= HLz6WPVKNaDBAzFFOAYvWkR9h1IAQOc4UycHQDia60BhxSkRILYeTWFyayBN=0D=0A= YWFzIDxtYXJrQG1lbmVtLm1pbmUubnU+iFsEExECABsFAkF/9pMGCwkIBwMCAxUC=0D=0A= AwMWAgECHgECF4AACgkQ8SFyUHWnEvOObQCdEGDR7oR//IVVAynpWrpFuc5Xt0gA=0D=0A= oKzSyqPzoDXekHqBm/4BHwThpJhKuQENBEF/9p8QBACOazsQm/Fb9bBmQnxJ906W=0D=0A= NSPYn9Q1a8YdqqpJC2J0ezDioJOi2+629jeNrmQsCGYGWPsvQzQhaQ2u2IS3s5OX=0D=0A= M8HWOuNKtZyqUL+sf8Gr+PFmXxAFykXmfP299lI8LhqGJTZPHU7SQhtC+i1vmp3C=0D=0A= kTABetoHfafUSVyuMXg53wADBQQAhYjdoMmzMDyD+v8s4/9iMJWaP7pMtEWZsD2n=0D=0A= XWtbGLuazNn0xDc7kp5nAfwBlOeYVEPIEUYsYxbYLZ6HxOtvA8VihXV2hViB/13X=0D=0A= cYCT7Uo1TH/ON/CHyJ+lv0IqJmYprb+VEO+BMcweGs2/Ky0ubkwP9kGyXT+FJKqT=0D=0A= BEjl7UiIRgQYEQIABgUCQX/2nwAKCRDxIXJQdacS84/RAJ4yvx+rHKvink2f7a08=0D=0A= n5KyrxUNGgCePtpx7JBDLp2S+jmk5ua336yL6sY=3D=0D=0A= =3D7X3V=0D=0A= -END PGP PUBLIC KEY BLOCK-=0D=0A= x-mozilla-html:FALSE version:2.1 end:vcard
Re: courier-mta + amavisd-new + spamassassin
On Saturday 20 November 2004 14:56, Horst Bursik wrote:
hi,
Does anybody have experiences with courier-mta + amavisd-new +
spamassassin?
Amavisd-new works great with postfix and sendmail but the last time i
tried to use amavisd-new in combination with courier it was nearly
impossible. With a lot of hacks in the amavis-code i accomplished
what i wanted but it's far away from a clean setup and most
important: i could only use parts of the full amavis functionality.
This was half a year ago and hopefully there had been some
improvements in either amavis or courier, or someone with more
perl-experience than I found a solution?
I couldn't find anything useful in the web so I'm trying it here. If
anyone can give me some tips i would be very grateful.
tia,
horst
I made some notes for myself last time I installed the combo you
mention. Maybe you can use some of it, maybe you can't. The patch I
refer to is a slightly edited version of the courier patch that is
included in the amavisd-new Debian package. I had to slighty adjust the
pacth here and there - otherwise it would not apply cleanly (maybe this
has changed since I did my install?).
I hope to have gotten everything written down, but I haven't yet
followed/verified my written down instructions myself yet, so there may
in fact be bits of pieces missing in this 'recipe'. Anyhow, here goes:
# Install amavisd-new with all dependencies
sudo apt-get install amavisd-new
update-rc.d -f amavis remove
update-rc.d amavis defaults 21 21
# Now fetch sources, courier patch, and rebuild
sudo apt-get source amavisd-new
sudo apt-get build-dep amavisd-new
chown -R frederik:frederik amavisd-new* (as root)
cd amavisd-new-20030616p10
cp debian/etc/amavisd.conf .
wget \
http://sentinel.dk/linux/debian/patches/amavisd-new-courier-debian.patch
cat amavisd-new-courier-debian.patch | patch -p0
cp amavisd.conf debian/etc/amavisd.conf
dpkg-buildpackage -rfakeroot -us -uc
# Install new patched package to replace the unpatched one
sudo dpkg -i amavisd-new_20030616p10-3_all.deb
## Configuration notes
# Run amavisd-new via manual start/stop (and not via courierfilter).
# In amavisd.conf:
$mydomain = 'sentinel.dk';
$daemon_user = 'amavis';
$daemon_group = 'daemon';
$pid_file = /var/run/amavis/amavisd.pid;
$lock_file = /var/run/amavis/amavisd.lock;
$forward_method = undef;
$notify_method = 'pipe:flags=q argv=/usr/sbin/sendmail -f \
${sender} -- ${recipient}';
$unix_socketname = /var/lib/courier/allfilters/amavisd;
$unix_socket_protocol = 'courier';
# Set various file ownership and permissions.
touch /var/log/amavis.log
chown amavis:daemon /var/log/amavis.log
chmod 640 /var/log/amavis.log
chown -R amavis:daemon /var/lib/amavis
find /var/lib/amavis -type d -exec chmod 750 {} \;
find /var/lib/amavis -type f -exec chmod 640 {} \;
# Activate amavisd-new as a filter through courierfilter/filterctl.
ln -sf /usr/sbin/amavisd-new /usr/lib/courier/filters/amavisd
chmod 755 /var/lib/courier/allfilters
# Ensure that /etc/courier/enablefiltering exists and contains esmtp.
# This is default for Debian installations, btw.
# Restart amavisd-new
/etc/init.d/amavis restart
# If clamav is not already member of secondary groups daemon and
# amavis, add it manually and restart clamav for changes to take effect.
adduser clamav daemon
adduser clamav amavis
/etc/init.d/clamav-daemon restart
SpamAssassin notes at:
http://www.sentinel.dk/cookbook/?SpamAssassin_with_Courier
B/R,
--
Frederik Dannemare | mailto:[EMAIL PROTECTED]
http://qa.debian.org/developer.php?login=Frederik+Dannemare
http://frederik.dannemare.net | http://www.linuxworlddomination.dk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
