perl.qpsmtpd...Re: Interesting article on async-ness by Guy Hulbert- June 27, 2008 On Fri, 2008-27-06 at 20:28 -0400, Matt Sergeant wrote:> http:oubiwann.blogspot.com200806so-you-want-your-code-to-be-asynchonous.html> > It&39;s about Python, but the same stuff generally applies to working with > qpsmtpd-async.blech ... twisted docs are much better-- --ghhttp://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8114.html Interesting article on async-ness by Matt Sergeant- June 27, 2008 http:oubiwann.blogspot.com200806so-you-want-your-code-to-be-asynchonous.htmlIt&39;s about Python, but the same stuff generally applies to working with qpsmtpd-async.http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8113.html Re: questions re: async, perperl, new release by Matt Sergeant- June 27, 2008 On Fri, 27 Jun 2008 15:19:27 +0200, Dale Gallagher wrote:> 2008627 Matt Sergeant <mattsergeant.org>:>>> qpsmtpd-forkserver is our closest equivalent. I don&39;t know if>>> anyone&39;s been running it under pperl or PersistentPerl for a while.>> >> Actually qpsmtpd-prefork is closer.> > Ok, great, thanks. Is qpsmtpd-async not faster Which one would you> guys recommend Performance is a priority.It depends how much concurrency you do. qpsmtpd-async..http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8112.html Re: questions re: async, perperl, new release by Dale Gallagher- June 27, 2008 2008627 Matt Sergeant <mattsergeant.org>:>> qpsmtpd-forkserver is our closest equivalent. I don&39;t know if>> anyone&39;s been running it under pperl or PersistentPerl for a while.>> Actually qpsmtpd-prefork is closer.Ok, great, thanks. Is qpsmtpd-async not faster Which one would youguys recommend Performance is a priority.>> The subversion version is quite stable; indeed it&39;s almost certainly>> better than the last release.>> There&39;s a message..http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8111.html Re: questions re: async, perperl, new release by Matt Sergeant- June 27, 2008 On Fri, 27 Jun 2008 04:17:55 -0700, Ask Bjørn Hansen wrote:> >> Has anyone run qpsmtpd under PersistentPerl (a.k.a SpeedyCGI). There>> is a mention of pperl, but I&39;ve never used it.> > qpsmtpd-forkserver is our closest equivalent. I don&39;t know if > anyone&39;s been running it under pperl or PersistentPerl for a while.Actually qpsmtpd-prefork is closer.>> I noticed a mention of a new release on 4 June. Any news on that Is>> the CVS version stable.http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8110.html Re: questions re: async, perperl, new release by Ask Bjrn Hansen- June 27, 2008 On Jun 27, 2008, at 3:43, Dale Gallagher wrote:> What exactly is the async version of qpsmtpdIt&39;s an event based version based on Danga::Socket (the same module perlbal for example is built on).> Has anyone run qpsmtpd under PersistentPerl (a.k.a SpeedyCGI). There> is a mention of pperl, but I&39;ve never used it.qpsmtpd-forkserver is our closest equivalent. I don&39;t know if anyone&39;s been running it under pperl or PersistentPerl for a while.> I noticed a mention of a new..http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8109.html questions re: async, perperl, new release by Dale Gallagher- June 27, 2008 Hi thereI&39;m about to try qpsmtpd (as a replacement for qmail-smtpd) and wouldappreciate answers to some questions I have:What exactly is the async version of qpsmtpdHas anyone run qpsmtpd under PersistentPerl (a.k.a SpeedyCGI). Thereis a mention of pperl, but I&39;ve never used it.I noticed a mention of a new release on 4 June. Any news on that Isthe CVS version stable enough for productionThanksDalehttp://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8108.html Re: require_resolvable_fromhost bug by Matt Sergeant- June 12, 2008 Heh, I was going through this code a week or so ago and thought this looked odd...I&39;ll apply the patch.On Thu, 12 Jun 2008 14:53:22 +0200, Jose Luis Martinez wrote:> Hi,> > We&39;re using the require_resolvable_fromhost plugin, and have seen > that there is a bug in it. MAIL FROM commands with legitimate > domains where getting rejected as not resolvable.> > The bug has been tracked down to domains that have zone files with > unresolvable MX records.> >...http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8107.html Re: require_resolvable_fromhost bug by Jan Vlkers- June 12, 2008 Jose Luis Martinez schrieb:..ok. persuaded ;-)Janhttp://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8106.html Re: require_resolvable_fromhost bug by Jose Luis Martinez- June 12, 2008 Jan Völkers escribió:> Jose Luis Martinez schrieb:> >> I consider this a bug, as leaving fake MX records is a known antispam >> technique, and after all, the domain is resolvable if you have at least > > The known antispam technique is not having unresolvable MXs, it is > having _unreachable_ MXs. Really different, i think> From http:wiki.apache.orgspamassassinOtherTricks"The fake records can either be undefined or can point to dead IP addresses...http://www.nntp.perl.org/group/perl.qpsmtpd/2008/06/msg8105.html |