2008/6/19 Peter Burden <[EMAIL PROTECTED]>:
>
>
> There's a new version of sigfilter available (version 1.1)
at http://web.ptwol.net/sigfilter
Documentation is bit better, code is a bit tidier and it now works with
sqwebmail.
---
Bernd Wurst writes:
Hi.
We have configured courier to only allow encrypted connections.
To achieve this, we have set
##NAME: IMAP_TLS_REQUIRED:1
#
# Set IMAP_TLS_REQUIRED to 1 if you REQUIRE STARTTLS for everyone.
# (this option advertises the LOGINDISABLED IMAP capability, until STARTTLS
#
Hi.
On Tuesday 22 July 2008, Sam Varshavchik wrote:
> > IMAP_TLS_REQUIRED=1
> > [...]
> > What's up with this setting? Did the option name change in any way?
> No, but if you had TLS_STARTTLS_PROTOCOL set, remove the setting and leave
> it at the default.
No, this string is not present in my conf
Jesse Molina wrote:
> Hello
>
> I think I have found something wrong with either Courier MTA being
> unnecessarily militant/protective or a Newegg.com cgi mailer is doing
> something wrong.
>
> To start with, I don't think this is my personal configuration. I
> don't have any (known) policies th
I have few questions on making Pythonfilter /greylist work with
Courier. I am a newbie in both areas:
I was on Macro Balmer's web site to learn about / download python
greylisting with Courier. The
web site refers to courier-pythonfilter-0.9 then pythonfilter-
greylist. Then I found pythonfil
Steve Poe a écrit :
> I have few questions on making Pythonfilter /greylist work with
> Courier. I am a newbie in both areas:
>
> I was on Macro Balmer's web site to learn about / download python
> greylisting with Courier. The
> web site refers to courier-pythonfilter-0.9 then pythonfilter-
>
Steve Poe wrote:
>
> I was on Macro Balmer's web site to learn about / download python
> greylisting with Courier. The
> web site refers to courier-pythonfilter-0.9 then pythonfilter-
> greylist. Then I found pythonfilter-1.3 which
> has a greylist python script. Since I am new at this, I am co
I have working spamassasin, but can not get it to process courier mail.
Eg: when I feed spamassasin a test mesage via the command line, it
returns some output. But when i recieve mail via smtp, there is not
spamassassin header. Spam still reigns.
Here is what i did trying to follow tips from spama
Jan Müller a écrit :
> I have working spamassasin, but can not get it to process courier mail.
>
> Eg: when I feed spamassasin a test mesage via the command line, it
> returns some output. But when i recieve mail via smtp, there is not
> spamassassin header. Spam still reigns.
> Here is what i did
Thanks for the feedback everyone.
We're using Courier 0.53. Any gotchas in using pythonfilter 1.3?
pythonfilter seems to be full of many features. If we wanted just the
greylist option. I am assuming we just uncomment the greylist section in
the pythonfilter-modules.conf?
Can we enable/disable t
Thanks for the advice. The bofh file was the first place I looked, and
the only thing I have configured is a couple of spamtraps.
Which means, this message is hitting the defaults, if that is in case
the trouble.
Bowie Bailey wrote:
>
> I have seen this problem before. It used to be part
Steve Poe wrote:
> We're using Courier 0.53. Any gotchas in using pythonfilter 1.3?
I don't think so, but I'd still recommend trying to keep that up to date.
> pythonfilter seems to be full of many features. If we wanted just the
> greylist option. I am assuming we just uncomment the greylist sec
I updated to Courier 0.60.0 yesterday, and I noticed a couple of things
afterward:
1) esmtpd and esmtpd.dist contain a line that reads:
# [EMAIL PROTECTED]@
Is this left over from the 2001 "SSL simplification project"?
2) The TLS_TRUSTCERTS setting isn't present in esmtpd-ssl or imapd-ssl,
thou
Can we change the order/priority that these modules run for outbound and
inbound?
Do we need to uncomment the sections on both the pythonfilter-
modules.conf
and pythonfilter.conf for the modules we want to run or only
pythonfilter-modules.conf?
Thanks.
Steve
On Jul 22, 2008, at 12:26 PM, G
I tried to download the whitelist shown in the README file, for the
whitelist_block,
but it did not download. does anyone have an example of what would go
into the nogreylisting file?
So, what can we expect with the greylist program if I buy an airline
ticket. According to the the greylist
m
Bernd Wurst writes:
Hi.
On Tuesday 22 July 2008, Sam Varshavchik wrote:
> IMAP_TLS_REQUIRED=1
> [...]
> What's up with this setting? Did the option name change in any way?
No, but if you had TLS_STARTTLS_PROTOCOL set, remove the setting and leave
it at the default.
No, this string is not pre
Steve Poe wrote:
> Can we change the order/priority that these modules run for outbound and
> inbound?
Currently, no. There is only one policy.
> Do we need to uncomment the sections on both the pythonfilter-
> modules.conf and pythonfilter.conf for the modules we want to run or
> only pythonfi
Gordon Messmer writes:
I updated to Courier 0.60.0 yesterday, and I noticed a couple of things
afterward:
1) esmtpd and esmtpd.dist contain a line that reads:
# [EMAIL PROTECTED]@
Is this left over from the 2001 "SSL simplification project"?
Yes, this needs to be removed, superceded by TLS_T
Steve Poe wrote:
> I tried to download the whitelist shown in the README file, for the
> whitelist_block, but it did not download. does anyone have an
> example of what would go into the nogreylisting file?
I kind of expected that to go away at some point. :(
This is pretty close, but you'll ne
I understand I can add a file to the /etc/courier/smtpaccess folder
with appropriate allow/block rules file (which I am still trying to
figure
out. Can I do this by email address as well in addition to IP address?
Thanks.
Steve
--
Steve Poe wrote:
> I understand I can add a file to the /etc/courier/smtpaccess folder
> with appropriate allow/block rules file (which I am still trying to
> figure out. Can I do this by email address as well in addition to IP
> address?
Not with any of the included modules. You might be inter
Steve Poe writes:
I understand I can add a file to the /etc/courier/smtpaccess folder
with appropriate allow/block rules file (which I am still trying to
figure
out. Can I do this by email address as well in addition to IP address?
No.
You do realize that anyone can send you an email with
Very good idea. I was definitely short-sighted on this.
Where does the sender/recipient pairs get stored so I can built an
appropriate
whitelist?
Thanks.
Steve
On Jul 22, 2008, at 4:03 PM, Gordon Messmer wrote:
> Steve Poe wrote:
>> I understand I can add a file to the /etc/courier/smtpacce
Most of the users I support have their own contact/email
list via Thunderbird or Outlook?
Does Courier support the option of a server-contact list
that users can add to? With sales people and administrative
people, it common that they need to contact/email the same
people.
Steve
Steve Poe writes:
Most of the users I support have their own contact/email
list via Thunderbird or Outlook?
Does Courier support the option of a server-contact list
that users can add to? With sales people and administrative
people, it common that they need to contact/email the same
people.
T
Setting BOFHHEADERLIMIT to something unreasonably large did not fix
this. Otherwise, my bofh file is empty.
Also, I don't see any way to change that max 5000 bytes per line
limitation, assuming that's still hard coded/default.
Jesse Molina wrote:
> Thanks for the advice. The bofh file was
Hi Sam.
On Wednesday 23 July 2008, Sam Varshavchik wrote:
> It's in the imapd-ssl file.
What does this file have to do with the non-SSL-imapd? I thought this file
would only be parsed for the imapd-ssl, which is generally independant from
non-SSL imapd.
But, however, this setting isn't present
Hi,
I'm probably just being too blind, but I've been searching docs and
the web for a few days now without success, so I thought I might try
asking here:
How can I disable cram-md5 for POP3 logins? Or - better - how can I
tell Courier to announce that it only accepts plain and login?
I'm running
28 matches
Mail list logo
