Sebastian Lechte wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yeiy,
i'd like to set the timeout the server waits for
ident-replys to a value
much lower, eg. 5 seconds. can that be done?
Only if you modify the code yourself, and accept the
responsibility for breaking st
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yeiy,
> > i'd like to set the timeout the server waits for
> ident-replys to a value
> > much lower, eg. 5 seconds. can that be done?
>
> Only if you modify the code yourself, and accept the
> responsibility for breaking stuff.
i thought so. but wou
Thus spake Sam Varshavchik on Thu, Jul 01, 2004 at 06:45:39PM CDT
> Lindsay Haisley writes:
>
> >Outside of changing the spec'd gid of the mailman user in /etc/passwd, is
> >there any way to instruct courier to use an alternate gid when delivering
> >mail to a specific account? I would think that
I'm going to look into it and set up a test account and get back, but my
preliminary tests indicate that the gid in the authentication db is being
ignored, although the delivery directory is being honored. I have
DEFAULTDELIVERY="| /usr/bin/maildrop"
set in /etc/courier/courierd, so it may be a
I think I'm misunderstanding something about Courier's perlfilter. I
copied over the perlfitlter-example file and replaced the 'filterdata'
code with this:
--
my $x = 3;
sub filterdata {
return "500 Value: $x";
}
--
But
Lindsay Haisley writes:
Outside of changing the spec'd gid of the mailman user in /etc/passwd, is
there any way to instruct courier to use an alternate gid when delivering
mail to a specific account? I would think that the gid spec'd in the
authentication database should do this, but apparently it
Sebastian Lechte writes:
hi everyone,
around the 10th of june there was a question regarding the ident-requests
courier makes to better identify the client who sends mail through it.
i like this behaviour, however i received a complaint today, mail delivery
would need at least 30 seconds to complet
Eduardo Roldan writes:
More interesting articles (this is about SPF & SenderID):
http://www.circleid.com/article/634_0_1_0_C/
The article makes me question Sam: What do you think about these
frameworks? Will be implemented in courier someday or be relayed to
other authors (pythonfilter|perfilter co
Lloyd Zusman [EMAIL PROTECTED] wrote:
> By the way ... I presume that your patch would enable Courier to write
> the "SPF-Received:" header into the messages that it doesn't reject
> ... correct?
I'm not 100% sure about this yet, but I guess it would best be made an
option, like all of the SPF sup
Chris Petersen [EMAIL PROTECTED] wrote:
> Of course, it'll be just in time for the release of this new thing that
> the SPF guys and microsoft are planning. And as far as I know, it won't
> be backwards compatible with SPF,
Eduardo Roldan [EMAIL PROTECTED] wrote:
> The article talks about compati
On Thu, 1 Jul 2004, Julian Mehnle wrote:
> Dan Yost [EMAIL PROTECTED] wrote:
> > Once again, yes, we have told the company that their email is wrong, RFC
> > non-compliant, evil, horrible, stupid, silly and all the rest. I'll
> > just about bet anybody $5,000 that they won't change it *one bit*,
Dennis Sacks [EMAIL PROTECTED] wrote:
> Brainstorming here: so if there is an SPF record, you can verify the
> validity of the 'sending' server and accept or reject accordingly. If
> not, why not fall back on greylisting?
> (http://projects.puremagic.com/greylisting/index.html)
You shouldn't blind
Dan Yost [EMAIL PROTECTED] wrote:
> Once again, yes, we have told the company that their email is wrong, RFC
> non-compliant, evil, horrible, stupid, silly and all the rest. I'll
> just about bet anybody $5,000 that they won't change it *one bit*,
> because it works for *everybody* else except us.
Hi all,
We're running an old, old Courier (courier-0.40.2-1).
I *sure* thought I'd seen the answer to this question, but searching my
own archives as well as the web-based one has stymied me, so I will
venture to ask.
from=<[EMAIL PROTECTED]>: 517 Syntax error.
in the log file. I know that thi
"Julian Mehnle" <[EMAIL PROTECTED]> writes:
> [ ... ]
>
> Thus I'm also currently working on a patch to Courier that properly
> integrates SPF support into Courier. I hope Sam will consider adopting it
> into the official Courier distribution when it is finished.
I applaud you for doing this! I
I'm using mailman as a list server with courier as my MTA. The mailman user
is in /etc/passwd as belonging to primary group 'mailman'. Mailman does
security based on group ID and must be compiled with --with-mail-gid set to
the group of the mail user. This is set to 'courier' which works for mos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi everyone,
around the 10th of june there was a question regarding the ident-requests
courier makes to better identify the client who sends mail through it.
i like this behaviour, however i received a complaint today, mail delivery
would need at le
On Thu, 2004-07-01 at 14:05, Chris Petersen wrote:
> Of course, it'll be just in time for the release of this new thing that
> the SPF guys and microsoft are planning. And as far as I know, it won't
> be backwards compatible with SPF, and as much as we may dislike it, no
> microsoft endorsemen
SPF isn't meant to be applied to message headers ("From:", "Sender:",
whatever), but to the envelope sender address that's specified by the
sender through the "MAIL FROM" command during the SMTP dialog.
That is irrelevant when it comes to web solutions. PHP, etc. only give
you a "from" field, and
Julian Mehnle wrote:
Chris Petersen [[EMAIL PROTECTED]] wrote:
There is already an SPF module for pythonfilter.
Unfortunately, I had to disable it because so many web services out
there insist on sending things like invites and referrals "from" my
address rather than "from" them a
Chris Petersen [EMAIL PROTECTED] wrote:
> There is already an SPF module for pythonfilter.
>
> Unfortunately, I had to disable it because so many web services out
> there insist on sending things like invites and referrals "from" my
> address rather than "from" them and "reply-to" to me. SPF will
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Eduardo Roldan
> Sent: Thursday, July 01, 2004 4:38 PM
> To: [EMAIL PROTECTED]
> Subject: [courier-users] An Interview with the Lead Developer of SPF
>
> More interesting articles (this is about
The article makes me question Sam: What do you think about these
frameworks? Will be implemented in courier someday or be relayed to
other authors (pythonfilter|perfilter comes to my mind)
There is already an SPF module for pythonfilter.
Unfortunately, I had to disable it because so many web servic
More interesting articles (this is about SPF & SenderID):
http://www.circleid.com/article/634_0_1_0_C/
The article makes me question Sam: What do you think about these
frameworks? Will be implemented in courier someday or be relayed to
other authors (pythonfilter|perfilter comes to my mind)
--
Brian Feeny wrote:
Also, not sure if it matters, but my filesystem is coming from an NFS
server.
The NFS server was not running fam, but i turned it on and still get
the same error.
I had problems running the testsuite on NFS. Once I compiled on a
non-nfs filesystem the problem went away.
HTH,
25 matches
Mail list logo
