Re: [courier-users] DNSBL exclusion

2007-07-03 Thread Alessandro Vesely
mouss wrote: > Alessandro Vesely wrote: >> mouss wrote: >> >>> 3- never block your own users with methods designed for "inbound" mail. >>> This includes DNSBLs, spamassassin rules, ... etc. >> >> One exception is when you have methods that can determine that mail >> is being sent by automated m

Re: [courier-users] More on OpenBSD 4.1

2007-07-03 Thread Sam Varshavchik
Steve Shockley writes: When building on OpenBSD 4.1, I get the following: gmake[4]: Leaving directory `/usr/ports/mystuff/mail/courier/w-courier-0.56.0/build-i386/courier/module.dsn' [ … ] I'm not sure what's the problem with some of these. It's complaining about perfectly valid code. I

[courier-users] Max size of a .courier file

2007-07-03 Thread Enrique Verdes
Hi all, I have a mail address with a .courier file in its Maildir with a list of addresses to forward. This file have 51 lines, with one address per line. This addres couldn't receive mail untill I deleted some of the addresses in the list. So, my question is, what is the maximum size of a .cou

Re: [courier-users] Max size of a .courier file

2007-07-03 Thread Sam Varshavchik
Enrique Verdes writes: Hi all, I have a mail address with a .courier file in its Maildir with a list of addresses to forward. This file have 51 lines, with one address per line. This addres couldn't receive mail untill I deleted some of the addresses in the list. So, my question is, what is t

Re: [courier-users] More on OpenBSD 4.1

2007-07-03 Thread Sam Varshavchik
Heh, my first try got mangled. Time to squish a bug… Steve Shockley writes: When building on OpenBSD 4.1, I get the following: gmake[4]: Leaving directory `/usr/ports/mystuff/mail/courier/w-courier-0.56.0/build-i386/courier/module.dsn' [ … ] I'm not sure what's the problem with some of th

Re: [courier-users] More on OpenBSD 4.1

2007-07-03 Thread Steve Shockley
Sam Varshavchik wrote: > I'm not sure what's the problem with some of these. It's complaining > about perfectly valid code. > > I'm going to have to guess here. Try applying this patch: Perfect, it builds successfully now. Thanks. ---