On 01/13/2011 06:55 AM, Nicholas Lee wrote:
Is there a plugin that will check rcpt addresses against a back end smtp
server?
Ideally via some sort of smtproutes lookup.
Where are your addresses stored? What I have done in the past is to
check directly against the user database with a custom
Filippo Carletti wrote:
The symptoms are:
1. spam mail is not recognized as spam, no tests match (X-Spam-Status:
No, hits= required= tests=)
2. spamd logs:
warn: spamd: timeout: (300 second timeout while trying to SYMBOLS)
at /usr/bin/spamd line 2016, line 19.
3. qpsmtpd logs have a 5 minute
Chris Lewis wrote:
> With both port 25 and 587 you connect to in plaintext, and can "upshift"
> to SSL via STARTTLS command (if the server is configured for it).
>
> With port 465, the whole connection is in SSL.
>
> Apparently the port 465 variant is deprecated in favor of 587/STARTTLS.
Yeah, I
Kjetil Kjernsmo wrote:
> So, what I actually want is just to encrypt the password. The email will
> go unencrypted over the rest of the network anyway (unless I
> PGP-encrypt it), so SSL seems like an unnecessary hassle and overhead
> that I'd like to avoid. LOGIN and PLAIN are both freetext, ri
Steve Kemp wrote:
This sequence can repeat multiple times though
I cannot seem to find why the RSET is being issued
by the client side. At each step my plugins are
returning the correct responses (e.g. "250 QUEUED"
after the DATA phase). Of course the MS-Exchange
admin believes their ser
Guy Hulbert wrote:
If not, then why not require that they all use the same one as
qpsmtpd ... license wars are a total waste of time.
I agree completely; it's why I mentioned it. If a plugin has been
developed and distributed independently, it may have a license which
conflicts with qpsmtpd.
Robert Spier wrote:
> If a plugin is stable, well documented, generally useful, maybe
> tested?,
And has an appropriate license?
John
Dale Gallagher wrote:
> I'm struggling to get qpsmtpd up and running with a chained cert from
> DigiCert. It's a WildCard SSL Cert, but I doubt that should make a
> difference. Currently there are no problems when using my self-signed
> certs!
Other than the first time a client uses it, they must
Shamly wrote:
>
> Hi All,
>
> During the last few days we have been experiencing a hang in the
> qpsmtp forkserver. Below is a sample of the list of running tasks for
> "qp". This keeps on growing to 20 - 30 PIDs (./qpsmtpd-forkserver
> [192.168.155.20 : Unknown) and the whole thing hangs. We u
Matthias Pfeifer wrote:
> My problem is, NO outlook (outlook and outlook express) user
> can authenticate and i get alway a relaying denied in the logfile.
> It's weird, because other Email programms i've tested works fine
> (Pegeasus, Thunderbird, uebimiau webail, sylpheed, bat ..) with the
> same
Peter J. Holzer wrote:
> I always found the rcpt_ok plugin in trunk/plugins rather useless for
> two reasons:
>
> 1) it can only check for the recipient domain, not the local part. So it
>cannot reject mails to non-existent recipients. Accepting a mail and
>later sending a DSN is IMHO not
Jan Völkers wrote:
> I'd like to communicate encrypted, but when i configure tls, qpsmtp
> stops working with the line "trying to get config for tls_ciphers" in
> the last logline.
That may be the last log line, but it is highly unlikely that it is the last
thing executed. If you turn up the logg
[EMAIL PROTECTED] wrote:
> My concern with killing all of the connections is that I have some
> internal processes that (I think) will occasionally corrupt log and data
> files when this happens.
You may want to reconsider your design, then. If you are trying to aggregate
multiple log streams int
[EMAIL PROTECTED] wrote:
> Is there a way to not accept any more connections, let the current
> connections finish, and then restart qpsmtpd? Something has to be better
> than my current heavy hammer approach.
I use 'svc -t' instead of HUP, because it will kill all of the connections
associated wi
Steve Kemp wrote:
There are several of the plugins contained are in the repository
which fail to pass a basic perl syntax check, for example:
The plugins were not originally intended to be complete Perl scripts but
rather are stubs which are loaded by Qpsmptd::Plugins (which includes
Qpsmt
Ask Bjørn Hansen wrote:
As John said, the databytes configuration should do what you are
asking. It'll reject the message right away if the sender uses the
extension that specifies the size in MAIL FROM and if not then it'll
stop buffering the data after the configured number of bytes has been
Jared Johnson wrote:
it occurs to me that the most appropriate thing would be to drop a
connection and stop listening when we have received what we consider
to be too much data after the DATA command.
That would be a major violation of the applicable RFC, and as such I
don't think it would be
Are we at a state where we could release? I'd like to get Net::SMTP::ESMTP
released before OSCON (so I can do a lightning talk on it), but I rely on an
installed qpsmtpd instance for the test suite (go figure, you need an MTA to
test a SMTP client).
Anything I can do to help (apart from actua
Matt Sergeant wrote:
OK, I'm fine with that.
Hopefully to put this thread to rest, I committed my one line change to preserve
the connection notes. If anyone's favorite core plugin stashes
connection-related stuff (like dnsbl) in the transaction notes, let's start
individual threads (with p
Chris Lewis wrote:
SMTP state and qpsmtpd/filtering state are not the same thing. The RFCs
talk about destroying SMTP state. It already does that without having
to destroy any notes() AFAICT. But it shouldn't blithely throwing away
qpsmtpd/filtering state - it's none of the RFC's business.
Matt Sergeant wrote:
I don't think we should care so much about the RFCs. If there are bits
in connection notes that might help determining if this is spam (or some
other thing we're trying to detect) before STARTTLS we need to allow
qpsmtpd to keep that information.
I'm talking about keeping
Chris Lewis wrote:
John Peacock says:
It's a required part of the RFC, see RFC-2487 Section 5.2:
Upon completion of the TLS handshake, ... [t]he server MUST discard any
knowledge obtained from the client...
Do you even have to purge envelope addresses per-se? It doesn't sa
[EMAIL PROTECTED] wrote:
And the result:
=== Trying host:25...
=== Connected to host
<- 220 host ESMTP qpsmtpd 0.40 ready; send us your mail, but not your spam.
-> EHLO
<- 250-host Hi xxx [x.x.x.x]
<- 250-PIPELINING
<- 250-8BITMIME
<- 250 STARTTLS
*** No acceptable authentication type
[EMAIL PROTECTED] wrote:
I have multiple maildir mailbox, I want to deliver new mail in the
mailbox containing the previous message (reply, thread, ...).
I strongly recommend against implementing this in a qpsmtpd delivery
plugin. Normally, you want delivery to do as little work as possible s
Matt Sergeant wrote:
So I'm about to apply Hano's fix for this - if you still object we can
always back out the patch. The point being that per-object hooks never
really worked, and this way is faster.
Go ahead, I've been off the net for the last 5 days (installing a new OS on a
new hard driv
Matt Sergeant wrote:
But there's a patch in this thread to fix that, right?
Not a complete one, no. I'm at $WORK now, and I can't take a look at it
Changing %hooks to an "our" makes that work though.
Yes, but my mind automatically recoils at using package globals like
that. YMMV ;-)
I
Matt Sergeant wrote:
Because otherwise hooks are re-loaded on every connection (register()
needs re-run on every mail) which is a huge performance detriment.
Then we need to rethink that architecture; would it be acceptable to
return immediately if hooks are already defined (instead of just wa
Hanno Hecker wrote:
On Sun, 30 Mar 2008 21:51:26 -0700
Ask Bjørn Hansen <[EMAIL PROTECTED]> wrote:
On Mar 30, 2008, at 4:39 PM, Markus Ullmann wrote:
After tracing it down to rev 814-818, a friend of mine came up with
this patch and it seems to make it work for me again. Maybe someone
with
Juerd Waalboer wrote:
> Neither opening appears to have anything to do with qpsmtpd, the topic
> of this mailing list.
One of the primary reasons I got this job was the experience I gained working
with qpsmtpd. Hurray for open source projects...
John
p.s. sorry if you were offended... ;-)
I hope Ask doesn't feel like I'm poaching his userbase... ;-)
I thought I'd bring some job opportunities to your attention. If you
are willing to relocate to Columbia, MD, there are two positions open at
my new job:
http://jobs.perl.org/job/7848
http://jobs.perl.org/job/7846
Jared Johnson wrote:
> What's the best way to do this? Is there any way to avoid forcing it
> into spooling to disk?
Please describe what you are trying to do, rather than how you think you need to
do it. I can read that question several different ways, each with it's own
solution.
John
Jared Johnson wrote:
So perhaps Data::Dumper is having some trouble handling our data
structure? We get the same error trying to operating on $transaction
alone or $self alone.
Try setting
$Data::Dumper::Purity = 1;
(use the POD, Luke...;-)
My questions right now -- anybody got ano
Hanno Hecker wrote:
There's no real queueing mechanism with the smtp-forward plugin, the
mail will be rejected with a temporary error, which means the mail will
stay in the client's queue and sent later again... well at least for
most MTAs.
If you don't have any other queue plugin loaded, you a
[EMAIL PROTECTED] wrote:
of course you should run all common qpsmtpd anti-spam plug-ins up-
front, like: no_dialup, geo_blacklist_whitelist, check_earlytalker,
and so on. Captcha response mails are only being send to senders whose
mails have passed those plug-ins.
But that doesn't change the ba
Michael Salbinger wrote:
my qpsmtpd (smtp) auth does not work anymore.
the logs show some errors:
==> /opt/qpsmtpd/log/main/current <==
2007-11-18 21:11:32.754924500 Premature end of base64 data at lib/Qpsmtpd/Auth.pm
line 262, line 7.
2007-11-18 21:11:32.755041500 22483 running plugin (auth-l
Rob wrote:
A vanilla qmail install will accept email for domains listed in rcpthosts.
If no other instructions are specified in either virtualdomains or
smtproutes, qmail should just follow the published MX and forward the email
to the primary - which it does.
That isn't right. You should neve
David Summers wrote:
> I know I can hack the current plugins to do more of that but I was
> wondering if there was any development work to both reduce the amount of
> logging and/or make it more concise?
The whole logging system could definitely handle some reorganization, to
rationalize what gets
Jason Smith wrote:
I would like to add tls encryption support to my server to allow STARTTLS
connections, as well as CRAM-MD5 and AUTH-LOGIN. I am at the prelimnary
stage of finding out if this is possible.
qpsmtpd already has tls and AUTH support. The former is enabled simply
by creating cer
Chris Lewis wrote:
> Any idea why I'd be getting these:
>
> _convert_to_ssl failed (Could not create SSL socket: Socket operation on
> non-socket at ./plugins/tls line 158
>
> [At end of _convert_to_ssl(), I'm logging $@ if it's non-null]
>
> It may be that tls plugin's "init" method is NOT bein
Chris Lewis wrote:
I note that plugins/tls_cert clobbers the machine's name on Solaris. It
issues `hostname --fqdn` in an attempt to find the machine's full name,
and on Solaris, that's treated as setting the hostname to "--fqdn".
Ouch.
Sorry, that's my fault (but in my defense, you should
Hanno Hecker wrote:
> Index: lib/Qpsmtpd/SMTP.pm
> ===
> --- lib/Qpsmtpd/SMTP.pm (revision 804)
> +++ lib/Qpsmtpd/SMTP.pm (working copy)
> @@ -802,6 +802,7 @@
>my ($self, $rc, $msg, $args) = @_;
>
># reset trans
John Peacock wrote:
Peter J. Holzer wrote:
If I can't fix it, I'll probably remove the id code completely (or move
it to a branch). Despite the length of the discusssion I don't think
it's really that important, and it can be implemented in a plugin (as my
logging/file_con
Peter J. Holzer wrote:
If I can't fix it, I'll probably remove the id code completely (or move
it to a branch). Despite the length of the discusssion I don't think
it's really that important, and it can be implemented in a plugin (as my
logging/file_connection demonstrates).
It's really simple
Ask Bjørn Hansen wrote:
> Cool! Pretty funny that qpsmtpd makes a good test tool for an SMTP
> client. :-)
Yeah, well, qpsmtpd is a lot lighter weight and yet feature complete (not to
mention easier to configure) than any other MTA I've yet encountered. ;-)
I have grandiose plans to write an
All -
As part of my new $JOB (www.messagesystems.com), I've rewritten and
combined bits of Net::SMTP, Net::SMTP_auth, and Net::SMTP::TLS, into a
new class that I'm calling Net::SMTP::ESMTP. I have a full test suite
for it, but it currently relies on an instance of qpsmtpd running at
some kno
Ed McLain wrote:
Been having some issues where a connection would be killed by DENY or
DENYSOFT in the rcpto stage and yet qpsmtpd would allow the sender to
continue issuing commands and still accept the email. I've thrown together
a quick little patch that implements a {_killed} variable based
Brad Fitzpatrick wrote:
> But postfix/dovecot were only using the .crt and .key, as far as I can
> see. Why does qpsmtpd need the CA file? Isn't Geotrust in clients'
> default CA lists?
It isn't the client, rather it is the server that needs the Geotrust CA in it's
own CA file. OpenSSL on the s
vvitkov wrote:
I have a mail relay machine on which i want simple checks performed.
Checks like early talker, dnsbl and some very simple sanities.
Then the mail should be relayed to the real MX which will perform
spam/av detection/marking/clearing
What Robin said, but more directly:
MAKE SURE
Brian Szymanski wrote:
> Does anyone have any ideas for dealing with a DDOS? We're currently
> getting slammed with bogus bounce messages to the tune of 1.5 million a
> day, and it's hard for regular clients to get a word in edgewise. We've
> made sure all of our clients are using SSL instead of T
John Peacock wrote:
The above mentioned company is based 30 minutes from my house and is
advertising for a developer position. Does anyone have actual
experience with them as a company (or employer)?
Just to follow up on this thread; I have accepted a developer position
with Message Systems
The above mentioned company is based 30 minutes from my house and is
advertising for a developer position. Does anyone have actual
experience with them as a company (or employer)?
TIA
John
Saw this mentioned on the Jifty dev list:
http://brad.livejournal.com/2329271.html?thread=13756599#t13756599
Previously we did the "preforked pool of servers all doing blocking
accept" thing, but that didn't allow scaling of the pool size to deal
with demand. So instead, I sat down with some of
Les Mikesell wrote:
Or that users in your domain use email as it was designed to be used and
aren't nailed down to IP addresses... Yes, you can fix that with some
large amount of work these days, but what's the point?
With the trunk version of QPSMTPD, it is trivially easy to configure
SMT
Peter J. Holzer wrote:
I especially don't want a dependency on
daemontools because I haven't the slightest idea what the license is
(I couldn't find any information in the tarball or on the website, and
given the unacceptably restrictive license of qmail I won't take
chances).
It's not /that/ h
Peter J. Holzer wrote:
A colleague of mine who uses bash (I use zsh even as root) restarted
qpsmtpd-forkserver a few days ago, and we found that some plugins
(virus/clamav and one I wrote) terminated with a fatal plugin error
after that, because exec (I think) considers BASH_ENV tainted.
If you
abhilash s wrote:
> Hi,
>
> I would like to setup the smtps using qpsmtpd : I have followed the
> steps of Method 1 in the following link :
>
> http://wiki.qpsmtpd.org/config:smtps
>
The trunk version of qpsmtpd handles multiple ports (well, the forkserver code
does anyway) for a while now, i
abhilash s wrote:
> I have tried the dns_whitelist_soft plugin before but it was not
> working . For this I had created a file named config/whitelist_zones
> and entered the IP that is to be avoided from scanning .
dns_whitelist_soft uses a DNS zone (much like an RBL) to whitelist addresses.
The w
Matt Sergeant wrote:
On 18-May-07, at 10:32 AM, John Peacock wrote:
In the case of require_resolvable_fromhost, it is already configured
to work with dns_whitelist_soft, so you would only need to change it
like this:
Any reason that shouldn't be in core?
Yeah, we don't ship whit
abhilash s wrote:
How we can Whitelist an IP from require_resolvable_fromhost plugin
processing . My qpsmtpd config/plugins file have whitelist_soft
enabled . Also I have added the particular IP to the
config/whitelisthosts file. But still it is checked by the
require_resolvable_fromhost plugi
Guy Hulbert wrote:
I'm guessing that, like me, most people on this list just expect to port
587 to allow relaying for people using SMTP AUTH.
That is how I'm using it. I don't worry much about the Section 4
"Mandatory Actions" because I don't accept non-FQDN's at all (so I don't
need to worr
Johan Almqvist wrote:
Unfortunately, this will not work, because the dnsbl plugin will deny
the connection before whitelistsender can be set: dnsbl hooks connect(),
while sender whitelisting only can be done when the sender is known -
and that's afer connect.
Not quite accurate. dnsbl hooks
Lucas -LandM- wrote:
>
> Hi,
>
>I try to add domainkeys plugin, but I have this error:
Where did you get that plugin from? The one in trunk should work (the API
changed in Mail::DomainKeys::Message in an incompatible way, and I fixed up the
trunk version (formerly branches/0.3x) to deal wi
Peter Eisch wrote:
This is the case in 0.32. I'm not subversion-enabled so I tried pulling
down each of the files from trunk. The result was, well, dismal. Could
someone please fling at me a tarball?
I sent Peter a tarball; I wonder if we could configure
SVN::Notify::SnapShot on the reposit
Peter Eisch wrote:
Ok, this is curious:
<- 250 AUTH PLAIN LOGIN
-> AUTH LOGIN
<- 334 VXNlcm5hbWU6
That is the base64 encoded string "Username:"
-> cGVpc2No
This is your username (again base64 encoded).
<- 334 UGFzc3dvcmQ6
That is the string "Password:" (again in base64),
-> NDJ
Peter Eisch wrote:
I've tracked this down to be more a client issue than plugin. Both clients
I've tried (oddly both M$) fail to present credentials it seems.
For testing, I always use swaks:
http://jetmore.org/john/code/#swaks
since you can see exactly what is going on in both direc
Hans Salvisberg wrote:
> I guess it makes sense to put the checks that are absolutely required
> (such as checking config("me")) into a plugin that needs to be run in a
> minimal system to receive /any/ messages at all.
>
> OTOH it is pretty wasteful to save the easiest checks for last, and it
> b
Michael Salbinger wrote:
> hi,
>
> is someone using smtp after pop auth with qpsmtpd?
> i am searching for a plugin to do that.
It's really better to use SMTP AUTH instead of SMTP after POP, since all modern
mail clients handle the former, it is more secure, and it doesn't require
additional bina
Matt Sergeant wrote:
> Does this work then? If so I can check it off my list :-)
Work in the sense that you can add it to config/plugins and it blocks PollServer
for the requested number of seconds, yes. However, my understanding of
PollServer was that this might not be the best way to handle the
Robert Spier wrote:
> I've finally reorganized the svn repository.
Your check is in the mail... ;-)
> At some point we'll decide whether the next version will be 0.33 or
> 0.40.
If we are shipping qpsmtpd-async, I'd vote for 0.40 (since that seems like a big
jump.
John
Matt Sergeant wrote:
qpsmtpd-async baby yeah! ;-)
EDOESNTWORK
The qpsmtpd-async script exists in branches/0.3x, but the Danga::Client
stuff does not (that's only in trunk). If I switch lib to trunk/ then I
get failures because Qpsmtpd::DSN doesn't exist in trunk (that's only on
the 0.3x b
Jens Weibler wrote:
tls was last updated last year - over 12 months ago
(http://svn.perl.org/viewcvs/qpsmtpd/trunk/plugins/tls?view=log)
Don't look at trunk; most recent development is on branches/0.3x:
http://svn.perl.org/viewcvs/qpsmtpd/branches/0.3x/plugins/tls?view=log
But the place that
Peter J. Holzer wrote:
Most of the time when forkserver maxes out the problem isn't CPU
usage[0], it's clients which simply connect and hang around doing
nothing until the timeout kills them. Greylisting doesn't help there, of
course.
That's exactly what I was seeing (strace yielded "read(0,"),
Ask Bjørn Hansen wrote:
A couple of generic detaint regular expressions sounds reasonable
though, no? Or maybe it's just an endless downhill slope (and not in a
good way). Hmn.
I was thinking about that after I sent my last response. If we offered
a trio of detainting methods for:
1) num
Ask Bjørn Hansen wrote:
Hmn, if we are leaving it to individual plugins to do this it seems like
we should at least have a utility method to help.
Yes, but the detainting is fairly specific to what kind of data the
plugin expects, so any utility method would have to accept a regex, at
which p
Michael Holzt wrote:
Hmm... very odd. You shouldn't get PollServer used at all if you're
running forkserver.
Wrong. I just checked out qpsmtpd-dev from svn and the qpsmtpd-forkserver
code uses Qpsmtpd::Pollserver at the mentioned position.
That's trunk, which has not been undergoing as much t
Bryan Scott wrote:
Forkserver maxes at 30 on the 2 filters and 15 on the primary (which is
mostly answering to machines using stale DNS records, i.e. dynamic
zombie hosts).
That is almost precisely our current configuration (except that the
inbound servers are ~450MHz Pentium-equivalent!). I
Ramiro Gonzalez wrote:
I am using qpsmtpd and smtp_forward plugin to redirect to a qmail-ldap
server running on 2525 port.
Why? Wouldn't it be more efficient to have qpsmtpd directly
authenticate against the LDAP server and use the qmail-queue plugin to
inject the delivery into qmail?
But
How is everyone else coping with this exponential rise in spam? I'm
drowning in it; I have to throw some new servers in place just so I can
continue to accept any mail. I used to have forkserver set to 21
simultaneous sessions and I would consistently have 5-10 free. I just
bumped that up to
Hans Salvisberg wrote:
perldoc README
only returns
No documentation found for "README".
Is this an intentional side effect of installing qpsmtpd? How can I
repair it?
Is the file README in the current directory? perldoc is not magical; if
the file isn't in the current directory, or
Hans Salvisberg wrote:
This returns "/root/tmp/" when running as root, i.e. it uses the current
user, no matter which -u user is set. If I hard-wire
$Spool_dir = "/home/smtpd/tmp/";
on the next line, then I can run ./qpstmpd-forkserver successfully.
Without that hack, I can only run it
Guy Hulbert wrote:
Is there a way to get a gmail account without an invitation ? (not
looking for one ... just asking).
Cellphone/PDA:
https://www.google.com/accounts/SmsMailSignup1
John
alias table.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
JT Moree wrote:
my qpsmtpd is running on a number of servers that filter the mail before
sending onto the real mail server. Since the users are not available a
plugin can be used to query the real mail server.
Is there one available already that does this? It would vary based on
the mail serve
allows the plaintext password to be passed from the client inside a
TLS wrapper, and yet be encrypted on disk at all times. This is far
more secure than any of the challenge methods, which require storing the
plaintext password on the server...
John
--
John Peacock
Director of Information
James Turnbull wrote:
I had a look at Qpsmtpd::Auth and note DIGEST-MD5 authentication isn't
available (I presume because of the tiny number of clients who support
it).
Yeah, not having any simple way to test it makes it kind of hard to
implement... ;-)
However, Thunderbird is apparently g
If you haven't noticed (and are still using it), ORDB is going offline
today:
http://ordb.org/news/?id=38
Personally, I'm down to using just my internal RBL and
sbl-xbl.spamhaus.org at this point and the latter has been responsible
for the majority of my upfront culling for some time
the
time... :(
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5748
Bryan Scott wrote:
> Ok. My fault for not knowing about the pre-connection hook.
> I tweaked dnsbl to run at pre-connection time and it's working great. I
> only use it on the "extremely trusted" blacklists, and have set up a
> dnsbl-soft and a dnsbl-tagonly that handle the less perfect blacklists
[EMAIL PROTECTED] wrote:
Matt Sergeant writes:
On 21-Nov-06, at 10:57 PM, jwa wrote:
What is the correct way to rewrite the entire message body?
Probably easiest to write your own queue plugin that does what you need.
I'm guessing someone must have wanted to do more extensive
body-rewrit
Unknown Sender wrote:
* missing "use Qpsmtpd::Constants" here and there.
Committed.
* plugins/count_unrecognized_commands only resets it's internal
counter on init (this can't work well in preforking,
I've seen a couple of other plugins broken for prefork, like
the "delete $ENV{RELAYCLI
Hanno Hecker wrote:
On Fri, 17 Nov 2006 11:22:29 -0500
John Peacock <[EMAIL PROTECTED]> wrote:
Just to make clear - it's not specific to tls, but fails the same way
for any plugin. I earlier got the error trying to load any of the
logging plugins.
You're using svn rev 671
Peter Eisch wrote:
Watercooler chatting got me to learn it. I don't like stumbling onto 'use'
statements inside conditionals but it seems to be necessary to evaluate
->port properly.
Except that unless you wrap that in an eval, or do the equivalent thing
using 'require', you are going to brea
Peter Eisch wrote:
Mine are basically the 0.32 framework. I don't use the 'tls' plugin at this
point though.
Just to make clear - it's not specific to tls, but fails the same way
for any plugin. I earlier got the error trying to load any of the
logging plugins.
John
I'm trying to get Apache::Qpsmtpd going on a new server and I'm not getting much
success:
Apache 2.2
Mod_Perl 2.02
Perl v5.8.8
I'm using the configuration exactly as described in the POD:
> Listen 0.0.0.0:25
>
>
> use lib qw( /var/qmail/service/qpsmtpd/lib );
> use Apache::Qpsm
Just FYI -
The drive on my primary [Linux] dev machine failed on Friday (tick,
tick, tick). Thankfully nothing terribly vital was there except for the
work in progress rewrite of the extended SMTP keyword support (TLS and
Auth), which I can easily recreate. I will be out of operation for a
Ask Bjørn Hansen wrote:
> Are there any bug-fix patches we must apply before releasing 0.33? I'd
> like to get it out soon-ish. It's been +6 months since the last release
> and I like us to have at least a couple of releases a year. :-)
I'm not aware of any bugfixes that are outstanding, only
Hanno Hecker wrote:
> the "skip_plugins" plugin lets you skip selected plugins for some hosts.
> This is similar to the whitelist plugins, but
> - the config is done in one config file for all plugins
> - no plugin needs to have the whitelist tests
> - each plugin can be disabled (or re-enable
Hanno Hecker wrote:
> With some changes to the code... the plugins/queue/postfix-queue now
> contains a pod section with "POSTFIX COMPATIBLITY" notes.
Applied, Thanks! I took the liberty of moving the pf2qp.pl script into the
directory with the generated Constants.pm and added a prompt for the pa
Sean Kennedy wrote:
I am setting up an anti-spam layer for my users. Each user has
preferences stored in LDAP. Individual users should be able to control
turning spam filtering on/off, virus filtering on/off, message handling
(tagged or quarantined?), the aggressiveness of spamassassin, and hav
Charlie Brady wrote:
I'm a little surprised that John (and kernel developers) don't want
patches as attachments, because reformatting by email and web clients
will often cause such breakage, whereas you won't see such problems with
attachments.
I *do* want attachments, but I find it harder to
1 - 100 of 842 matches
Mail list logo
