Still broken after upgrade linux-image-oem-24.04b:amd64 6.11.0-1017.17
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100571
Title:
IPU6 camera stopped working with upgrade of linux-image-oem-24.04b
Still broken after upgrade linux-image-oem-24.04b:amd64 6.11.0-1018.18
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100571
Title:
IPU6 camera stopped working with upgrade of linux-image-oem-24.04b
Still broken after upgrade to linux-image-oem-24.04b:amd64
6.11.0-1016.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100571
Title:
IPU6 camera stopped working with upgrade of linux-image-oem-24.
Public bug reported:
Hardware: Dell XPS 9315
Description:Ubuntu 24.04.2 LTS
Release:24.04
linux-image-oem-24.04b:amd64 6.11.0-1013.13 upgraded to linux-image-
oem-24.04b:amd64 6.11.0-1015.15 after phasing for four days.
IPU6 camera was working previously, but now fails to run in both
I've been stuck on this for a while now and was wondering if you could help.
The question is:
"A pentagonal number is defined as n(3n - 1)/2 for n = 1,2 etc. So, the first
few numbers are 1, 5, 12, 22 etc. Write a function with the following header
that returns a pentagonal number:
def getPenta
It looks like QP core uses gethostbyaddr() but not gethostbyname(). the fcrdns
plugin uses Net::DNS, and as far as I can tell Net::DNS never calls
gethostbyname() either. So I *think* we're good.
-Jared
From: Charlie Brady
Sent: Wednesday, January 28,
Looks like this might do what you need:
https://github.com/smtpd/qpsmtpd/blob/72f1a7a9620b5d732749a2c84e71998113f5d1fc/plugins/qmail_deliverable
-Jared
From: Reinhard Seifert
Sent: Wednesday, January 21, 2015 5:18 AM
To: qpsmtpd@perl.org
Subject: Is ther
$qpsmtpd->run(\*STDIN);# pass the "socket" like -prefork/-forkserver
$qpsmtpd->run_hooks("post-connection");
Master has #168 reverted so that will probably work for you now as well, but if
the above change works I can re-submit this PR in a working state.
-Jared
2015 um 23:31:06 Uhr
Von: "Jared Johnson"
An: "salvi...@gmx.ch"
Betreff: Re: Issues in the current HEAD
What daemon mode are you using? Prefork?
Hi all,
My employer (eFolder, Inc - www.efolder.net) is seeking a senior Perl
developer to join our team working on our email security software. I
respect a lot of the regulars on this list, and our software is built
with qpsmtpd, so I'm hoping some among you might be available and
intereste
>> At any rate, if a branch like this exists and someone else had the time
>> and motivation to do the leg work of applying enhancements from the
>> various forks to the core branch, I would most definitely ask my
>> employers
>> to put most of our codebase at your disposal to do this. Even if the
> I am to the point where I need to deploy. I was hoping that I could get my
> changes merged into the main branch, but that appears impossible. I hate
> the prospect of forking, but I see few alternatives.
>
> I hereby propose the creation of qpsmtpd-dev.
>
> The primary aim is merging the forks m
> In addition to whatever value it might have for Bayesian filters, it may
> be useful to always add an X-From: header, so that diagnosing email
> problems like my client with the forged From: header would be easier. I
> had to grep through his server logs to see how the spammer bypassed the
> SPF
You could ask the core developers to give you direct access to the main github
repo :-)
It seems apparent that you're invested in moving QP forward, and have the time,
talent, and motivation to do so while still playing by the rules. If I was on
the core team I think I'd be fine with letting yo
>> Why hasn't your rejected idea been worked into qpsmtpd yet?
>
> Because I came to view qpsmtpd in a different way than many
> do (many view it as a service with useful plugins which they
> can deploy, use, and enjoy). Instead I view it more as a
> framework for rejecting/processing/handlin
> Yup. Part of the motivation for this plugin was to short circuit all the
> intermediate plugins and handlers so I can feed the message to sa-learn
> and dspam. Until dspam is trained, that's a very important step in
> training it. But there's no gain in validating the HELO name, SPF, or
> Domain
> Yup. Part of the motivation for this plugin was to short circuit all the
> intermediate plugins and handlers so I can feed the message to sa-learn
> and dspam. Until dspam is trained, that's a very important step in
> training it. But there's no gain in validating the HELO name, SPF, or
> Domain
> What problems might I encounter if I were to do this?
>
> I ask because I have a client who is currently getting spammed viciously
> by spammers who use one address in MAIL FROM (to pass SPF tests) and they
> use the senders email address in the From: header so they can get
> whitelist scoring by
> Been there, tried that. I've had mx2.freebsd.org soft 4xx blocked for 1
> day at a time for over a week. Besides the increased number of connections
> to my server, using a 4xx error makes almost no difference. As soon as
> the penalty box expires, the queued ham and spam pour in and mx2 gets
>
We do something not exactly similar to this, but which might be somewhat
instructive. We modified the banner delay plugin so that the amount of
delay we apply to a server depends on its previous behavior with us. The
default delay is 15 seconds; if you send a message that we reject as spam
or vir
> There's several plugins that have something like what you've suggested:
>
> plugin action [ add-header | deny | denysoft ]
>
> And here's a sampling of the arguments that various plugins use with
> action:
>
> add-header, log, continue, reject, deny, denysoft, accept, delete, add
>
>
a little OT: 'reject N' seems a little clunky; why not something more
like 'action [reject | add-header | ...]'?
-Jared
> I also changed the per-user feature to only take effect if the
> message has a single recipient.
Perhaps it would be useful to give people the option of only accepting one
recipient per SMTP transaction? This seems a bit messy/inefficient, we
don't do it ourselves, but I've heard from at least
> 6. spamassassin plugin: added support for per-user SA config settings,
> rewrote header processing logic in spamassassin plugin so it adds all the
> SA generated X-Spam-* headers to the message. Refactored the code for
> better maintainability.
Adding all the X-Spam-* headers to all recipients'
> $sock->timeout is intended to be a connect timeout. Why should read
> timeout be the same.
well, it seemed like a good compromise short of providing a new API, which
I didn't have any bright ideas about. If you thought it best to provide
such an API, I wouldn't object to using it :) Also, I gu
eh... didn't mean to send this with no subject :)
> Our software generates a whole lot of concurrent LDAP traffic right now
> and we started running into an issue where our child processes would hang
> forever waiting around for LDAP operations that had apparently hung on the
> server end. This w
thout inadvertently stripping the headers :)
-Jared
> That line of code doesn't look at the headers though, just at the final
> dot at the end-of-data.
>
>> --------
>>
>> Jared Johnson <mailto:jjohn
ine inserted by qpsmtpd, qpsmtpd doesn't see _any_ headers.
>>
>> This implementation is backrev (0.80 I think), and as it's only spam
>> from one particular bot, we don't care about that particular wierdness
>> enough to investigate further. But it's worth
Oh and FYI, this patch is well tested on our own variant of SMTP.pm, but
that variant is slightly forked, and this version is itself not
specifically tested. I'm fairly positive it'll work though :)
> Hi,
>
> We got a bug report from someone using IBM's Lotus suite (I think for both
> their MUA a
Hi,
We got a bug report from someone using IBM's Lotus suite (I think for both
their MUA and MTA). Their users would often send messages where all the
content was in the subject and they didn't bother sending any message
content. I'm not sure if it's due to an apparently uncommon behavior for
th
That sounds like a pretty sweet configuration!
> [Note if you are running qpsmtpd-async, as we do, it's not really
> possible to route DNS queries differently for DNSBLs versus other DNS
> queries qpsmtpd does. ParaDNS doesn't handle paralleled DNS queries to
> different servers well.]
when I fi
> I thought about a module which learns from the plugin dnsbl.
>
> Maybe we call it check_known_dnsbl_spammer ;-) and use the module
>
> http://search.cpan.org/~robm/Cache-FastMmap-1.39/lib/Cache/FastMmap.pm
Hi Aleks,
We discussed doing this once at my organization and someone astutely
pointed ou
I've been otherwise occupied but I forwarded this to the rest of our dev
team and our resident security "guru" had this to say
Original Message
Subject: Re: [Fwd: STARTTLS vulnerabilty and qmail-spamcontrol ucspi-ssl
qpsmtpd]
From:"Pete
> On 05/20/2011 02:56 PM, Jared Johnson wrote:
>> We do the sort of signing that is a huge doozy, and Matt is right, it's
>> a
>> doozy :) There are a couple of ways we've accomplished re-writing the
>> body from a MIME::Entity. Honestly it seems a bit non-s
We do the sort of signing that is a huge doozy, and Matt is right, it's a
doozy :) There are a couple of ways we've accomplished re-writing the
body from a MIME::Entity. Honestly it seems a bit non-standard to me but
we have some special requirements, like leaving the original body around;
I coul
Hi,
We've been chasing issues with Tumbleweed (now Axway) MailGate appliances
sending messages using TLS through us. Finally Tumbleweed told one of our
clients that this was probably due to a bug in their software when the
receipient MTA "makes multiple writes to the socket". On a guess, we
patc
> I agree that sharing code should be possible here (and that would be
> desirable); but as Matt suggested using the plugin inheritance stuff would
> be better than (eventually) making the One True Spam Fighting plugin. :-)
OK, I agree. Hopefully the integration will happen for our next release
So our organization is planning doing some big changes to the rbl plugin
and it dawned on us that it seems a lot easier to just add an earlier hook
to the existing uribl plugin (and rename it to rbl? or bl? or
something?). But of course I still have in mind that someday I'll get the
plugin comple
Specifically regarding the quoted-printable stuff.. my diff must have been
off an older version. This is probably a better representation of your
changes:
@@ -574,15 +574,22 @@
my $line;
my @qp_continuations;
while ( $line = $txn->body_getline ) {
+chomp $line;
if
> Although I could write some scripts to poll the user db at the mail server
> back ends. It would be nice if I could be somewhat lazy have have a plugin
> do this. ;) Real time checking for each delivery is obviously unworkable,
> but poll then cache with maybe a expiry is still a practical optio
Pretty sure he meant:
my ( $self, $transaction, $recipient) = @_;
my $sender = $transaction->sender;
Then you can do:
my $recipientdomain = $recipient->host;
my $senderdomain = $sender->host;
-Jared
Steve Freegard wrote:
>Hi Tapio,
>
>On 11 Jan 2011, at 11:34, Tapio Salonsaari wrote:
>
>> -
> return DENYSOFT_DISCONNECT, 'Too many connections from your class C'
> if ( grep {(ip_to_int($_)&0xff00) == $mask}
> @{$arg->{child_addrs}} )
Though this code is still untested in its
heavily-modified-from-our-version form, I feel like I should point out
that should
> IIRC, the connections-per-ip code isn't in a plugin right now -- it's
> part of the main binary -- because it requires some sort of shared
> state which we don't have for plugins.
The checks do exist in the binaries but they don't have to, you can use
$arg{child_addrs} and $arg{remote_ip} in hoo
> commit a52660a646012691f993cca821c00fe05cff08bb
> Author: jaredj
> Date: Wed Mar 25 07:38:05 2009 -0500
>
> Spool body when $transaction->body_fh() is called
>
> Qpsmtpd::Transaction::body_filename() calls $self->body_spool() if
> the message body has not already been spool to disk
> With this in mind is it possible without having to patch qpsmtpd to
> influence the order that auth methods are presented in from "250 AUTH
> PLAIN LOGIN CRAM-MD5" such that LOGIN is the first available option?
> Apparently in turnpike you can't specify the method you use and it
> always picks th
I've made a bunch more changes to the uribl plugin locally; man, we
_really_ need to get some kind of svn-to-gig thing going. Or at least I
need to re-educate myself on git and start putting things in my github
again. If I don't manage to do this by the time (soon) that things are
settled down a
Would anyone object to setting the default action to 'deny' on certain
reliable low-fp URIBL lists? Probably Spamhaus SBL-XBL and DBL and URIBL
Black. It seems like a new user turning on uribl checks would expect them
to do something more than adding headers, as long as the services it
rejects fo
> Another thing that nothing stops us from, in a late-bound programming
> language without private namespaces, is adding additional methods to
> base objects without changing the code that declares the base objects,
> as long as the implementation of the base objects promises to remain
> the same.
> colleagues have also complained that notes() even exists as a method and
> think it would be fine for it to just be a reserved namespace accessed
> directly as a hash key.
or at least that notes() should return the {_notes} hashref if it doesn't
have any callers
-Jared
> I have stuff that might wind up looking like
>
> $rcpt->persistent->{statistics_receivedmsgs_total}++;
>
> $rcpt->persistent->{statistics_receivedstatsbysender}{$NormalizedSenderAddress}++;
Perhaps $rcpt->storage could be provided that could be tied... it just
seems like this is the
> so inside QP, the qpsmtpd::address object would have a known parameter
> that brings up the per-address persistence hash, which would be a flat
> hash. Something like
..
See in my mind, per-recipient config and persistent data storage are more
separate. Maybe part of the reason I look at it thi
qld.gov.au sa.gov.au
so.gov.pl sr.gov.pl starostwo.gov.pl tas.gov.au ug.gov.pl um.gov.pl
upow.gov.pl uw.gov.pl vic.gov.au wa.gov.au
There were also about _1400_ reserved .us TLDs prune from the list, IIRC
You make some pretty good points. It may well not be worth the trouble,
at least for one-level TLDs.
Thanks,
Jared Johnson
Software Developer
DoubleCheck Email Manager
>
>
> Jared Johnson wrote:
>>
>> > I think we should probably consider putting support for parsed
>> messages
>> > into core, with the parsing done lazily if requested by the API.
>>
>> I forgot, we did kinda think of a couple of reasons not to
> I think we should probably consider putting support for parsed messages
> into core, with the parsing done lazily if requested by the API.
I forgot, we did kinda think of a couple of reasons not to want an API.
depending on where you put it, you may find QP in general depending on
MIME::Parser
> I think we should probably consider putting support for parsed messages
> into core, with the parsing done lazily if requested by the API.
It's a good idea, it's only that I haven't yet had the time and
justification to write and to test a move from the plugin model (see the
attached plugin in m
I assume you meant to CC the list originally, I've added it :)
>> Could you show some code examples?
>
> not immediately, but sure
>
>> What do you do with the queue
>> plugin(s) if recipients ended up having different headers or bodies due
>> to
>> tagging etc.?
>
> Advenge only deals with delive
> My experience porting the Advenge SMTPD to be a qpsmtpd plug-in
> indicated that the current interface is entirely adequate for
> per-recipient things, as long as the plug-in manages its own
> persistence. I don't think any new hooks are required.
On principal I'd agree that it's possible to do
>> Attached also is tld_lists.pl, a companion file that needs to be dropped
>> in lib/Qpsmtpd/ which provides the list of first, second, and third
>> level
>> TLDs that we care about. It's derived from our URIBL datafeed as well
>> as
>
> Would they be ok if this was
> released as an independent C
> sub rejected_recipients {
> my $self = shift;
> @_ and $self->{_rejected_recipients} = [...@_];
I noticed after posting this that the line above is a no-op. Ha :)
> return () unless $self->{_recipients};
> return grep { $_->dsn and ! $_->dsn->action ~~ [qw(Delivered Queued
> Quarantine
> Having a common API for "per-recipient" things have long been on the todo
> list.
>
> We've talked about it a couple times before; but the
> requirements/needs/wishes never sunk in deep enough in my head to do
> anything about it. So: How do you use this?
>
> My thoughts all along have been to
>> And
>> I'm confused by that bit. From what I can tell, the async/uribl plugin
>> ignores plugins/uribl entirely and uses
>> Qpsmtpd::Plugins::Async::DNSBLBase, which in turn uses ParaDNS.
>
> In that case, it's possible (and likely) that it may never have
> worked with async. When time is shor
> On Wed, Jul 21, 2010 at 07:54:30AM -0500, Jared Johnson wrote:
>> Unlike the other bits of "dodge this sort of munging" operations,
>> examining my test results and asking uncle google has not made it clear
>> to
>> me what "inserted-semicolon mungin
> On Sun, Jul 25, 2010 at 04:43:36AM -0500, Jared Johnson wrote:
>> The plugin has the following advantages over the original:
>
> Based on a single read-through of the code, I like most of it. Some
> assorted observations, though:
>
> - Parsing out the MIME sections is
> Do the owners of that data care about it being used this way? You may
> be violating any agreement with them. Would they be ok if this was
> released as an independent CPAN module?Either way, can we
> structure this as an API instead of just an include file?
Forgot to mention, yes, I'd be
>> - Introduces support for URIBL services that may not have worked right,
>> at
>> least out of the box, before. Defines the subtle differences between
>> various known URIBL services in order to maximize compatibility.
>
> Is it worth pulling some of this config out of the code and putting it
>
> while ( m{ ( (?: [a-zA-Z0-9:./-]+ @ )?
> [a-zA-Z0-9][a-zA-Z0-9.;-]+\.$tld )
>(?! \.?\w ) }gxo ) {
> my $host = lc $1;
> # Deal with inserted-semicolon munging, e.g. 'http://foo;.com'
> if ( my @split = $host =~ /(.*?);(.*)/ ) {
>
> This seems to be a big improvement at least on the 3 million lines of
> random traffic i tested with, and it's a smaller patch:
[snip]
Well, it may have been an improvement over my own data, but a colleague
pointed out the following case:
check out spamsite.com;it's awesome!
And this didn't de
>> It seems like
>> all you have to do to get around the etc. problem is to wait a
>> little longer before applying the fixup -- allow the semicolon to match
>> in
>> the hostname search and then strip it out.
>
> My bad.. I guess the plugin currently only fixes up '&#\d\d\d' encoding,
> not et
> It seems like
> all you have to do to get around the etc. problem is to wait a
> little longer before applying the fixup -- allow the semicolon to match in
> the hostname search and then strip it out.
My bad.. I guess the plugin currently only fixes up '&#\d\d\d' encoding,
not etc. maybe i'
on MIME::Parser and Net::DNS::Async and completely changes
the config file format. I don't really have approval to spend hours
creating digestible individual patches... but posting the whole plugin is
better than not posting any code, right? :)
-Jared
> On Wed, Jul 21, 2010 at 07:54:30AM
Hi,
I'm working with Devon Carraway's URIBL plugin and have been testing its
effectiveness in finding URI's using 6 million lines or so of email
traffic from a day in the life of our mail servers. My testing has shown
that the following line in the while ( $l = $transaction->body_getline )
loop w
I'm in agreement with Alexander. Icedove upgraded and removed enigmail and
iceowl extensions. It
looks like ice-owl is present in my kept section now, but I would like to know
the status for
engimail to be matched with icedove 3.x?
Thanks,
Jared Johnson
--
CONFIDENTIALITY. This elect
I'm in agreement with Alexander. Icedove upgraded and removed enigmail and
iceowl extensions. It
looks like ice-owl is present in my kept section now, but I would like to know
the status for
engimail to be matched with icedove 3.x?
Thanks,
Jared Johnson
--
CONFIDENTIALITY. This elect
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/45108138/XsessionErrors.txt
** Changed in: gksu (Ubuntu)
Status: Incomplete => New
** Tags added: apport-collected
--
Unable to authenticate to perform administrator functions
https://bugs.launchpad.net/bugs/5684
Architecture: i386
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: gksu 2.0.2-2ubuntu1
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
Uname: Linux 2.6.31-20-gen
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45108119/Dependencies.txt
--
Unable to authenticate to perform administrator functions
https://bugs.launchpad.net/bugs/568451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45020180/Dependencies.txt
** Attachment added: "UbuntuoneClientPackages.txt"
http://launchpadlibrarian.net/45020181/UbuntuoneClientPackages.txt
** Attachment added: "XsessionErrors.txt"
http://launchpadlibrarian.net/4
Public bug reported:
Binary package hint: ubuntuone-client
When trying to perform administrative functions such as adding software
or users, the authentication window pops-up, shaking rapidly for almost
a second, and then closes. There is no input box and I can see
"Authentication Failure" befor
getting this on current karmic beta. the automagical bug stuff led me
here.
--
gnome-power-manager frequently crashes with SIGSEGV in IA__g_closure_invoke()
or g_closure_invoke()
https://bugs.launchpad.net/bugs/260314
You received this bug notification because you are a member of Ubuntu
Bugs, w
getting this on current karmic beta. the automagical bug stuff led me
here.
--
gnome-power-manager frequently crashes with SIGSEGV in IA__g_closure_invoke()
or g_closure_invoke()
https://bugs.launchpad.net/bugs/260314
You received this bug notification because you are a member of Ubuntu
Desktop
So, our fork has a few logging and bayes training mechanisms that run in
hook_reset_transaction. They are all very fast, most of the time; but
recently one of them broke and started running very slowly. The result:
QP would inject an incoming messages into the queue, enter
hook_reset_transac
From: Ask Bjørn Hansen [...@develooper.com]
Sent: Tuesday, September 15, 2009 5:22 PM
To: qpsmtpd@perl.org ML
Subject: Released 0.83
prefork: More robust child spawning (Jared Johnson)
You might as well credit this one to Peter Samuelson while you&#x
Patches submitted where?
-Jared
On 09/09/2009 04:43 PM, Jason Mills wrote:
Okay patches submitted.
For for the time delay but I had a bit of hard drive scare last night
after I finished the code but before I could spin the patch.
Any input, suggestions and or scorn is welcome :)
- J
On Tue,
On 08/23/2009 04:03 PM, Matt Sergeant wrote:
On Thu, 20 Aug 2009 10:18:39 -0500, Jared Johnson wrote:
It looks like logging/file doesn't like the empty hashref returned by
Qpsmtpd::transaction().
I never understood why it did that. Any reason it can't return either
undef or (prefera
On 08/14/2009 04:31 PM, Ask Bjørn Hansen wrote:
On Aug 14, 2009, at 14:14, Jared Johnson wrote:
This should allow the logging/file plugin to log even if it isn't
called from
within a transaction
Thanks, applied and pushed.
The conditional around where you made the first change are a b
This should allow the logging/file plugin to log even if it isn't
called from
within a transaction
Thanks, applied and pushed.
The conditional around where you made the first change are a bit of a
mess (indicating that there's a better way to do whatever it does),
but I didn't look closer ...
From: Jared Johnson
This should allow the logging/file plugin to log even if it isn't called from
within a transaction
---
plugins/logging/file |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/plugins/logging/file b/plugins/logging/file
index 31292ad..5717fe5 1
We noticed that logging/file sometimes emitted this error:
XX: Can't call method "notes" on unblessed
reference at /usr/share/qpsmtpd/plugins/logging/file line 272.
It appears this is because QP internal sometimes legitimately calls ->log before
a transaction object exists. The patch I'm sending
On 07/29/2009 09:39 PM, Ask Bjørn Hansen wrote:
On Jul 29, 2009, at 12:07, Jared Johnson wrote:
We recently noticed a message in our postfix queue that thought it
was addressed to " foo.com". After examining it, it turned out that
Qpsmtpd accepted a MAIL FROM command formatted like
On 07/30/2009 07:11 AM, Peter J. Holzer wrote:
On 2009-07-29 14:07:53 -0500, Jared Johnson wrote:
We recently noticed a message in our postfix queue that thought it was
addressed to " foo.com". After examining it, it turned out that Qpsmtpd
accepted a MAIL FROM command formatted like
We recently noticed a message in our postfix queue that thought it was
addressed to " foo.com". After examining it, it turned out that Qpsmtpd
accepted a MAIL FROM command formatted like so:
MAIL FROM:
When it passed it to postfix, it transmographied it first into the
sender 'u...@domain.com
works pretty well on 3.0.193.0~svn20090708r20142-0ubuntu1~ucd3~jaunty,
64-bit. A bit choppy sometimes... but I think I'll probably hold the
chromium updates till flash support gets official so it doesn't break
any worse, and never open firefox again :)
-Jared
On Jul 9, 1:09 pm, Danilo Raineri
This thread may or may not be applicable:
http://www.nntp.perl.org/group/perl.qpsmtpd/2008/07/msg8134.html
-Jared
On 07/09/2009 07:15 AM, Stefan Priebe wrote:
Hi!
I've massive problems with authentification and qpsmtpd. After some time
i always get a you're already authorized. This is cause b
One could however offer a alternate standard set of plugins
implementing the discussed ideas, I think.
One could. I've been considering it, but mine's not as configurable (in
terms of handling mailer behaviour on a hit) as I'd like. Probably
wouldn't be hard to rework that bit.
The project a
I like this approach, but it's had its complications for us because we
don't want to make the compromise of doing the rest of the checks at a
given stage needlessly; e.g. if our RBL plugin hits, we don't want to
bother doing RDNS and SPF lookups only to say 'sorry, you were on an
RBL' afterward
We've been considering blocking messages that break RFC compliance by
including a space before or after the colon in MAIL FROM: and RCPT TO:
commands. From RFC 5321 Section 3.3:
Since it has been a common source of errors, it is worth noting that
spaces are not permitted on either side o
erest in accepting this if I tested it and put
it in my git?
-Jared
On 06/02/2009 08:09 AM, Jared Johnson wrote:
Why not set --idle-children at start-up to something higher (or just 0
to disable)?
Setting it higher is a bit bothersome because our QP children use too
much memory right now (m
Why not set --idle-children at start-up to something higher (or just 0
to disable)?
Setting it higher is a bit bothersome because our QP children use too
much memory right now (mainly from using DBIx::Class), so it would be a
bit unfortunate to have more memory-consuming kids around that aren'
Even if you're not near max children the parent will only spawn max idle
children, then it sleeps until an event, wake-up and see if more
children are needed. Debug log should give some clue, if this is the
reason.
Bingo. Looking further into things, it was apparent that a freshly
restarted no
Inbound and outbound email scanned for spam and viruses by the
DoubleCheck Email Manager v5: http://www.doublecheckemail.com
Do we have to be exposed to this spam?
*blush*
Since I administer our qp installation that adds those, I suppose I
could exempt myself without anybody noticing :)
-J
1 - 100 of 211 matches
Mail list logo
