hallo, -------------------------------------------------- From: "Julien Valroff" <[email protected]> Sent: Thursday, July 30, 2009 7:04 PM To: "Steve" <[email protected]> Cc: <[email protected]> Subject: Re: [Dspam-user] Dspam errors.
> Hi all, > > Le jeudi 30 juillet 2009 à 16:20 +0200, Steve a écrit : >> -------- Original-Nachricht -------- >> > Datum: Thu, 30 Jul 2009 15:37:58 +0200 >> > Von: albinootje <[email protected]> >> > An: [email protected] >> > Betreff: Re: [Dspam-user] Dspam errors. >> >> > Steve wrote: >> > >> > >> Followed this howto : >> > >> >> > http://www.kirya.net/articles/setting-up-dspam-as-a-filter-for-postfix-on-debian-etch/ >> > >> except that i skipped the aliases part for now >> > ---cut--- >> > > You need to give us much more info then just that. Start by posting >> > > your >> > dspam.conf and master.cf and main.cf. >> > >> > I had followed the above mentioned howto exactly concerning those >> > files. >> > >> > But now I've also changed : >> > smtp inet n - - - - smtpd >> > into : >> > smtp inet n - - - - smtpd >> > -o content_filter=lmtp:unix:/var/run/dspam.sock >> > in /etc/postfix/master.cf >> > >> Aha. I see. >> >> >> > and made a script that checks logfiles for the "251 died" errors, and >> > no >> > errors since then! >> > >> The pipe command used with the FILTER command is very prone to break >> when you deliver messages to it which have some special characters. >> The SMTP or LMTP method to send mails to DSPAM for inspection is much, >> much, much more solid. > > That's clear, but when using relay mode with Postfix, using FILTER is > the only solution I am aware of to avoid scanning outgoing (relayed) > email. Any possible alternatives are welcome, that was a question I > wanted to ask shortly ;) why not use transport.map e.g.: example.com lmtp:[127.0.0.1:24] //send to dspam * smtp: //use mx-record or use virtual transport: virtual_transport = lmtp:127.0.0.1:24 virtual_mailbox_domains = example.com are this working alternatives? yes which is the best? I use virtual transport this time. It work, but need spam@ and ham@ in dspam-database :( > >> >> > >> Should I try the newest dspam beta version instead ? >> > >> >> > > I would go for 3.9.0 alpha/beta, if you can. It's much more stable >> > > then >> > the ancient 3.6.8 release found in Debian. >> > >> > Thanks! >> > >> If I am not wrong then Julian is having the DSPAM package for Debian >> available under this URL: http://packages.kirya.net/ >> Give 3.9.0 ALPHA/BETA a try. You will not regret it. Since you are >> anyway planing to change the tokenizer I would suggest you to use the >> following settings in your dspam.conf: > > Be aware that these packages are higly experimental (though tested with > my setup, hence if you have followed my "howto", they should also behave > correctly for you, provided you apply the necesseray MySQL changes - > read carefully the UPGRADE file or wait for a few days that the packages > get updated). > I'll give it a try too. > Cheers, > Julien > Sebastian > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Dspam-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspam-user > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
