On Monday 20 Aug 2012 14:55:41 Charlie Brady wrote:
> On Sun, 19 Aug 2012, Devin Carraway wrote:
> > This was reported as Debian bug#684571
(http://bugs.debian.org/684571):
> The patch does more than just excise the "comment". It also removes the
> auth information, for privacy/security reasons.
On Saturday 10 March 2007 10:12, Johan Almqvist wrote:
> On Mar 9, 2007, at 21:15, Vulpes Velox wrote:
> > I just noticed some on created a PAM plugin, but it is currently just
> > a wiki page currently. I was just planning of trying it out after
> As the author of the current authcheckpassword, I
On Monday 26 February 2007 21:40, RupS wrote:
> I'm somewhat disappointed by the fact nobody is responding anymore.
> We'd really like to proceed with using the prefork version, since
> forking is what's currently causing high loads on our mailservers.
> Can anybody reproduce the problems I have?
On Wednesday 21 February 2007 22:21, Brian Grossman wrote:
> My local branch is quite a bit out of sync with qpsmtpd's svn trunk,
> so before I put in the effort to port this to trunk, tell me, is there
> interest?
Definitely. Even if I don't end up using your exact config layout, having
the mul
On Wednesday 21 February 2007 14:09, Les Mikesell wrote:
> Nick Leverton wrote:
> > I'm not sure which part of RFC 2821 you're referring to when you talk
> > about "breaking SMTP" in the context of rDNS checking.
>
> 4.1.4
> "An SMTP server may
On Wednesday 21 February 2007 14:26, [EMAIL PROTECTED] wrote:
> On Wed, Feb 21, 2007, Jens Weibler <[EMAIL PROTECTED]> said:
> > My wish would be: I can configure inside the plugins-config which
> > plugins where used normally and which are used while relaying.
>
> i can see several ways to do this
On Tuesday 20 February 2007 18:59, Peter J. Holzer wrote:
> Can SME server use apt repositories? I've packaged most of my plugins
> (and a few others) into rpms and put them into an apt repository. If it
> can, you can put something like
>
> rpm http://www.hjp.at/apt redhat qpsmtpd
> rp
On Tuesday 20 February 2007 17:52, Michael Holzt wrote:
> > Aiming for a quiet life Michael. It's my own server and I don't
> > particularly mind if I break any rules discouraging scammers
> > and hackers.
>
> I'm sick of people like you breaking SMTP. I operate mail servers
> for 12 years and i've
On Wednesday 14 February 2007 18:54, RupS wrote:
> But I can reproduce it. When I try to connect to the server using telnet
> (or swaks, an email sent test util), 1 out of 10 connects time out.
> I see the same error in the logs. I never had this with the "normal"
> qpsmtpd which used tcpserver.
A
On Tuesday 13 February 2007 21:24, RupS wrote:
> Hi there,
>
> We recently switched to qpsmtpd-prefork because we noticed we could
> handle about twice as many connections.
> Since we're using prefork, we get a lot of these "Could not print" erros
> in the logs, looking like:
> Could not print [220
On Wednesday 07 February 2007 06:30, Hanno Hecker wrote:
> Yes, it's the wrong place for creating connections to a DB. Maybe you
> haven't seen it yet, this is from my (upcoming) plugin doc
> (http://ankh-morp.org/~vetinari/tmp/plugins.pdf -> chapter 2.1)
It looks pretty good, I've already learnt
On Friday 02 February 2007 07:02, Robert Spier wrote:
> Tabs are evil. Sure, they're valid, but lets avoid spreading them.
>
> If we're going to add TLS information to the header then lets do it in
> a way that's compatible with other mailers. (i.e. do what sendmail or
> postfix does)
Isn't TLS
On Saturday 06 January 2007 08:32, Robert Spier wrote:
> Doh, that was my intent.
>
> I went home sick from work today, so my brain must still be off.
>
> Anyway, I'll apply a slightly tweaked version of that tomorrow. (No
> reason to use a regex.)
Many thanks Robert, I'll try it out.
Nick
I think we discussed this before but I can't see it in the archives at the
moment.
Can qpsmtpd change its Received header from "with ESMTP" to "with ESMTPA"
when SMTP auth is in use please ? This will let SpamAssassin recognise
the auth header without any other changes.
I've attached a tested
On Sunday 05 November 2006 09:57, Devin Carraway wrote:
> Thanks, Nick. I've applied a variation on your patch. The bug you
> supplied didn't actually exist in the official qpsmtpd release; I assume
> you were working from one of the distribution variants or my own
> multi-plugin-dir patch.
Than
;m particularly uncertain about the recommended way to pass arguments.
Thankyou,
Nick Leverton
checkpassword
Description: Perl program
The existing Qpsmtpd.pm code tries to allow multiple plugin dirs, but it
fails if all the plugins aren't underneath the first directory named
in /etc/qpsmtpd/plugin_dirs.
The attached patch fixes this and will search for each plugin in each of
the directories named. This allows such things as
The attached patch allows you to give named addresses or domains a
different SPF policy from your system default. As my POD for the
change says,
You can override the default rejection policy for specified addresses
or domains using the whitelist_spf configuration file.
whitelist_spf
On Thu, Jul 28, 2005 at 08:19:13AM -0400, Bob Dodds wrote:
> I was planning to use it only for local recipient addresses
> which had already been looked up in ldap at rcpt, but
> somebody might use it to write their relays to disk if
> some temporary problem existed. They could have srs
> chars to
On Sun, Jul 24, 2005 at 05:15:54AM -0400, Bob Dodds wrote:
> mkdir ( ( $stub =~ /(\S+)/ ? $1 : '' ) , oct ( '0750' ) ) ;
>
> $file =~ /(\S+)/ ? ( $f = $1 and $f ) : ( return DECLINED and '' ) ;
>
> maybe /(\S+)/ because these file paths are based on
> email addresses. Other checks are done.
"f
On Tue, Jun 07, 2005 at 07:33:27PM -0400, Bob wrote:
> Do I need this? I'm getting six to nine dupes to the
> same recipient from a worm, and even though I
> can deny that worm at rcpt, I'd like to fix the hole,
> wherever it is, that is allowing duplicate recipients
> for one message.
>
> sub _un
On Sun, Mar 06, 2005 at 03:50:23AM -0500, Bob wrote:
> Check the MX for the domain in dns to see if the mta now
> connected is an authorized mta for the From: domain. If not,
Unfortunately this useful sounding check doesn't work. Many ISPs and
many big users have different incoming and outgoing
On Sat, Mar 05, 2005 at 07:06:39AM -0800, Matt Sergeant wrote:
> On 3 Mar 2005, at 05:04, Nick Leverton wrote:
>
> >No, all bounces always come from <>.
>
> Unfortunately this is wishful thinking.
Ok, all well formed bounces always come from <> :-) Or if not, then
On Thu, Mar 03, 2005 at 04:11:12PM +, Nick Leverton wrote:
> I think the count_unrecognised patch is buggy, I'll work on it and post
> another one.
Cancel that - it was still configured off on the test machine ! Sorry,
Nick
On Thu, Mar 03, 2005 at 07:30:33AM -0500, John Peacock wrote:
> Cool! I'll take a look at these when I get to work and apply them if they
> look reasonable. I'll be sure to credit you and iCritical.
I think the count_unrecognised patch is buggy, I'll work on it and post
another one.
Nick
On Thu, Mar 03, 2005 at 07:39:18AM -0500, Bob wrote:
> Does a REAL bounce, not an rfc-ignorant test, ever come
> from a null sender? Could I drop if sender is null, recipient
> not postmaster or abuse, at data hook, even if recipient is legit?
No, all bounces always come from <>.
1. > >>my $host
On Wed, Mar 02, 2005 at 11:47:21PM -0500, Bob wrote:
> #rcpt_ok
>
> my $host = lc $recipient->host;
> $host = $self->qp->config("me")
>
> What? $host="calling_all_elvis"? Am I not seeing my $host's scope
> or was same $host assigned a value, then assigned a different value?
Look at the context a
Here are my patches to (for the most part) tidy up the logging and
modernise some of the plugins. A couple of bugfixes fell out of the
tidyup for free ! :-) My manager asked only that the company be credited
for these, hence my posting from my work address.
I have endeavoured to use the log leve
On Wed, Mar 02, 2005 at 12:53:03PM -0500, John Peacock wrote:
> Has anyone already written a plugin to call either the Sophos sweep CLI
> or the Sophie daemon?
>
> I'm going to be evaulating AV packages over the next month or so, and
> I'd appreciate any recommendations that you can give. In pa
On Sun, Feb 27, 2005 at 10:47:51AM -0800, Robert Spier wrote:
> > Ask, can we get a release now? Pretty please?
>
> +1, just do it.
There's still a little work to do. Some plugins don't use the $self->log
method yet for instance, but still call warn() instead. Also some
still use Mail::Address
I don't know how to fix this one, cos I don't know the ins and outs of
perl UID handling. But qpsmtpd-forkserver doesn't drop its GID correctly:
2005-02-25 11:57:11.809180500 24306 Running as user smtpd, group root
This is perl, v5.6.1 built for i386-linux.
Nick
Qpsmtpd, like qmail-smtpd, doesn't insist on HELO having a parameter.
If a lazy tester (such as myself :)) just types HELO, then SMTP.pm
complains of an undefined reference when logging, and generates a Received
header which Spamassassin can't parse as it doesn't match their qpsmtpd RE.
The attach
On Tue, Feb 01, 2005 at 10:06:34AM -0500, John Peacock wrote:
>
> Second call! I went back and checked for other recent patches which
> hadn't been applied (and fixed the auth_vpopmail_sql code that I had
> just patched ;). I'm putting HEAD into production today myself, so I'm
> happy to star
On Mon, Dec 20, 2004 at 04:09:07PM -0800, Robert Spier wrote:
> > my ($space, $from) = ($from_parameter =~ m/^from:(\s*)(<[^>]*>)/i)[0];
> > $self->transaction->notes("extra_space_in_mail_from", $space ne
> > $self->transaction->"");
>
> I'd prefer to see something similar to the 'caut
Attached is a patch against recent CVS which alters the check_spamhelo
plugin to use connection->relay_client instead of the now-removed
transaction->relay_client.
Nick
--- plugins/check_spamhelo.orig Tue Nov 30 12:06:37 2004
+++ plugins/check_spamhelo Mon Dec 6 11:14:14 2004
@@ -26,7 +26,7
On Tue, Nov 30, 2004 at 09:27:53AM -0700, Bryan Scott wrote:
> I used to. Then a customer complained about not getting email from
> Amazon to his email forwarding address provided by Outblaze. Amazon
> publishes SPF records, so our server was rejecting the Outblaze machines
> when it tried to
Is anyone using the SPF plugin to actually deny mail when the published
SPF records say it is coming from an unauthorised source ? Do you find
any problems with false positives ?
BTW the plugin needs altering for the new $connection->relay_client()
flag. There is a patch attached against CVS ver
On Sat, Oct 23, 2004 at 09:02:40PM -0700, Robert Spier wrote:
> Grr. Looks like one of the viewcvs configuration options isn't
> working right. I've put a workaround in place.
Thankyou.
Nick
Webcvs seems poorly again. I go to http://cvs.perl.org/viewcvs/qpsmtpd/
and I get
An Exception Has Occurred
The root "qpsmtpd" is unknown. If you believe the value is correct, then
please double-check your configuration.
HTTP Response Status
404 Repository not foun
On Thu, Sep 02, 2004 at 10:30:05PM +0200, Michael Holzt wrote:
> > But RELAYCLIENT being set in the environment is an external requirement
> > (for some backends, at least qmail-queue).
>
> Why do you think it is needed for qmail-queue? I can't see that that's true.
Some qmail-queue replacement
CVS access at http://cvs.perl.org/viewcvs/qpsmtpd/ seems to be broken.
The URL just refreshes to http://cvs.perl.org/cvs-public/cvs-public/qpsmtpd/
nd thence to http://cvs.perl.org/cvs-public/cvs-public/cvs-public/qpsmtpd/
and so on continually.
Nick
--
"And we will be restoring neurotypi
On Mon, Jul 12, 2004 at 09:45:58AM -0400, George Chrisbacher wrote:
> Hi,
>
> The received header insterted by QPSMTPD isn't understood by SpamAssassin,
> and I'm wondering where to start. I'm no RFC expert, but isn't the IP
> address supposed to be in brackets? When I bracket it, SA has no prob
On Wed, May 26, 2004 at 09:53:26PM +0100, Matt Sergeant wrote:
>
> I really wish I could fix this. It's a shame nobody has time to debug
> the problem.
It only shows up on high volumes (or maybe, it shows up at small fixed
likelihood, which is small enough that only high volumes show it).
I'm no
On Mon, May 24, 2004 at 05:13:21PM -0400, John Peacock wrote:
> Nick Leverton wrote:
>
> >I'm running it on pperl with tcpserver, and I wouldn't recommend pperl.
>
> That's odd, since I am running the same way, yet I don't have problems
> (usually).
On Mon, May 24, 2004 at 12:35:14PM -0400, John Peacock wrote:
> I'm curious because I am already planning on making some changes to our
> architecture due to retiring a commercial MTA for qmail/vpopmail/courier,
> so I have to mess with everything anyways. I just want to get a feel for
> whethe
On Tue, May 18, 2004 at 02:11:22PM -0400, Andy Ruse wrote:
> connect_handler function looks like this:
>
> sub connect_handler {
>my ($self, $transaction, $recipient) = @_;
>my $remote_ip = $self->qp->connection->remote_ip;
>
...snips...
> If I start up qpsmtpd, and a message comes in fro
On Mon, Mar 22, 2004 at 06:03:12PM -0600, Roger wrote:
> I recently installed qpsmtpd and sorta got it to run. The problem is
> qpsmtpd would not recognise my smtproutes setup - which forwards all
Qpsmtpd doesn't use smtproutes, as someone else said. It purely
replaces qmail-smtpd; you still n
In article <[EMAIL PROTECTED]>,
Keith C. Ivey <[EMAIL PROTECTED]> wrote:
>
>Qmail doesn't distinguish between usernames on the basis of
>case. It lowercases everything and doesn't deliver to users
>with uppercase letters in their usernames:
>
>http://www.lifewithqmail.org/lwq.html#uppercase-user
I was just checking out qpsmtpd from CVS, to install on my Debian
box as a front end for my long-standing qmail system. I noticed that
config/plugins has been truncated by 33 lines at v1.10, and the comment
doesn't seem to relate why. Just asking for clarification, as I have a
working full config
The clamav filter needs to have a $transaction->body_resetpos call
before writing out its temporary file, in case it is not the first
plugin to read the message body. I've attached a patch which does this
and which also reads the location of clamscan from the config file
(e.g. clamav /usr/bin/cla
50 matches
Mail list logo
