This was meant as a qpsmtpd bug to be fixed. I can't see how this
ever worked, without a list of DNS servers to pull from.
ParaDNS is working fine.
Matt Sergeant wrote:
To be fair I don't do perl coding any more, so I'm happy for someone to
take over ParaDNS maintainence.
ParaDNS-XS is in my
Hi Matt
How about putting it on Github? Then anybody can look and decide if they
want to continue work on it and perhaps make it cpan -ready.
To be fair I don't do perl coding any more, so I'm happy for someone
to take over ParaDNS maintainence.
ParaDNS-XS is in my SVN server. Happy to shar
To be fair I don't do perl coding any more, so I'm happy for someone
to take over ParaDNS maintainence.
ParaDNS-XS is in my SVN server. Happy to share that with anyone who wants
it. It's basically ParaDNS using adns backend rather than Net::DNS. It's a
bit hacky and probably doesn't work 100%
Matt Sergeant wrote:
Do you have ParaDNS::XS installed? If not, try installing it. It's
generally likely to be better than plain ParaDNS (and will be used
automatically if it's installed).
There is no ParaDNS::XS on cpan... At least nothing returned for...
http://search.cpan.org/search?qu
Do you have ParaDNS::XS installed? If not, try installing it. It's
generally likely to be better than plain ParaDNS (and will be used
automatically if it's installed).
On Thu, 17 Jul 2014, David Favor wrote:
I've been running qpsmtpd-async for years on all sorts of servers.
The symptom of this problem is qpsmtpd-async just hangs
forever in the HELO part of SMTP transaction.
After putting reams of debug code in ParaDNS.pm + qpsmtpd,
the fix I came up with is a minor change to...
lib/Qpsmtpd/PollServer.pm
In start_conversation() no nameserver list specified. I
.6634.
>
>
>
>
> -----Original Message-
> From: David Favor
> Date: Friday, July 18, 2014 at 9:07 AM
> To: Edward McLain
> Cc: qpsmtpd
> Subject: Re: qpsmtpd-async weird ParaDNS lookup problem
>
>> Ed McLain wrote:
>>> If using dig yo
On Fri, 18 Jul 2014, David Favor wrote:
> > What's the actual problem you are trying to solve though?
>
> Problem is ParaDNS is failing on all lookups for this server.
...
> Notice the there lines with prepended '>>>' which show ParaDNS failing.
Perhaps you should be looking for assistance on a
m/>
Please direct all support questions to our support team at
host...@teklinks.com <http://mailto:host...@teklinks.com/> or 205.314.6634.
-Original Message-
From: David Favor
Date: Friday, July 18, 2014 at 9:07 AM
To: Edward McLain
Cc: qpsmtpd
Subject: Re: qpsmtpd-async weird P
A 127.0.0.1
localhost. 604800 IN ::1
What¹s the actual problem you are trying to solve though?
Problem is ParaDNS is failing on all lookups for this server.
export PARADNS_DEBUG=100
perl ./qpsmtpd-async -j 1 -v --user root --port 3000 --config-port=23000
16024 Lo
ks.com <http://mailto:host...@teklinks.com/> or 205.314.6634.
-Original Message-
From: David Favor
Date: Thursday, July 17, 2014 at 10:58 AM
To: Edward McLain
Cc: qpsmtpd
Subject: Re: qpsmtpd-async weird ParaDNS lookup problem
>Ed McLain wrote:
>> For an IP you need to look
this...
dig 1.0.0.127.in-addr.arpa
which returns the same on machines where qpsmtpd-async is working
and the one machine where it's broken...
;; AUTHORITY SECTION:
127.in-addr.arpa.604800INSOAlocalhost. root.localhost. 1
604800 86400 2419200 604800
If you're referri
direct all support questions to our support team at
host...@teklinks.com <http://mailto:host...@teklinks.com/> or 205.314.6634.
-Original Message-
From: David Favor
Date: Thursday, July 17, 2014 at 9:18 AM
To: qpsmtpd
Subject: qpsmtpd-async weird ParaDNS lookup problem
>I&
I've been running qpsmtpd-async for years on all sorts of servers.
Likely I have something in DNS setup slightly wrong on a new server
I'm setting up + what's wrong escapes me.
The symptom is qpsmtpd-async hanging forever in the HELO sequence.
Both forkserver + prefork work fin
On Sat, 30 May 2009, Baltasar Cevc wrote:
On May 28, 2009, at 4:37 PM, Matt Sergeant wrote:
Seems a little fragile. There aren't many bounces that quote all
headers. You'd be better off just rejecting all bounces in qpsmtpd,
then you only see "legit" bounces where the remote end issued an
imme
On May 28, 2009, at 4:37 PM, Matt Sergeant wrote:
Seems a little fragile. There aren't many bounces that quote all
headers. You'd be better off just rejecting all bounces in qpsmtpd,
then you only see "legit" bounces where the remote end issued an
immediate 5xx to your Exim's outgoing mail. Of
On Thu, May 28, 2009 at 3:27 PM, Matt Sergeant wrote:
> On Thu, 28 May 2009, David Nicol wrote:
>
>> On Wed, May 27, 2009 at 9:18 AM, David Favor wrote:
>>
>> I wrote a plugin to create VERP variable envelope return path
>> addresses for each and every message passing through my forwarding
>> sys
On Thu, 28 May 2009, David Nicol wrote:
On Wed, May 27, 2009 at 9:18 AM, David Favor wrote:
I host many domains and I'd like to protect them all
against backscatter
I wrote a plugin to create VERP variable envelope return path
addresses for each and every message passing through my forwardi
On Wed, May 27, 2009 at 9:18 AM, David Favor wrote:
> I host many domains and I'd like to protect them all
> against backscatter
I wrote a plugin to create VERP variable envelope return path
addresses for each and every message passing through my forwarding
system, kept track of in a little data
On Thu, 28 May 2009 12:04:27 -0400 (EDT), Charlie Brady wrote:
>
> On Thu, 28 May 2009, Matt Sergeant wrote:
>
>> years. So my qpsmtpd runs a no_bounces plugin, which I believe I've
>> posted here before.
>
> Google seems not to have heard of it.
Ah. OK. It basically just does this:
if ($tra
On Thu, 28 May 2009, Matt Sergeant wrote:
years. So my qpsmtpd runs a no_bounces plugin, which I believe I've
posted here before.
Google seems not to have heard of it.
Matt Sergeant wrote:
On Wed, 27 May 2009 09:18:32 -0500, David Favor wrote:
I'm currently running qpsmtpd-async.
I host many domains and I'd like to protect them all
against backscatter using something like this:
http://psg.com/~brian/software/authbounce/configure-authbounce.txt
On Wed, 27 May 2009 09:18:32 -0500, David Favor wrote:
> I'm currently running qpsmtpd-async.
>
> I host many domains and I'd like to protect them all
> against backscatter using something like this:
>
> http://psg.com/~brian/software/authbounce/configure-authbou
David Favor wrote:
I'm currently running qpsmtpd-async.
I host many domains and I'd like to protect them all
against backscatter using something like this:
http://psg.com/~brian/software/authbounce/configure-authbounce.txt
to add a bounce key to each outgoing message of the for
I'm currently running qpsmtpd-async.
I host many domains and I'd like to protect them all
against backscatter using something like this:
http://psg.com/~brian/software/authbounce/configure-authbounce.txt
to add a bounce key to each outgoing message of the form:
X-bounc
On Tue, 3 Feb 2009, Pedro Melo wrote:
Hi,
I have a AnyEvent-based project that requires a SMTP server. I was
considering either write a AnyEvent::Impl::Danga::Socket so that I can run
qpsmtpd directly.
Has anybody played with something like this here?
I don't think so... Though I have a b
Hi,
I have a AnyEvent-based project that requires a SMTP server. I was
considering either write a AnyEvent::Impl::Danga::Socket so that I can
run qpsmtpd directly.
Has anybody played with something like this here?
The other possibility is to rewrite parts of qpsmtpd to use
AnyEvent::Sock
it's not documented but i think it doesn't work for me because all my
mysql boxes i use --old-password option
Matt Sergeant wrote:
On Sun, 21 Dec 2008 00:17:29 -0800 (PST), bryanh wrote:
Because MySQL client libs are always blocking
Rather than going through the rest of your mail,
MysqlAsync doesn't seem so stable.
I get this scrolled over and over again, my config looks fine on MySQL 5.x
MysqlAsync: this should never happen
MysqlAsync: this should never happen
MysqlAsync: this should never happen
MysqlAsync: this should never happen
MysqlAsync: this should never happen
Thanks Matt!
We figured it out, we'll check that URL out.
Best
Bryan Heitman
FuseMail, LLC
Direct: 816.270.3460
Toll Free: 877.888.3873 x3460
Fax: 314.754.9932
Matt Sergeant wrote:
On Sun, 21 Dec 2008 00:17:29 -0800 (PST), bryanh wrote:
Because MySQL client libs are always blocking
On Sun, 21 Dec 2008 00:17:29 -0800 (PST), bryanh wrote:
> Because MySQL client libs are always blocking
Rather than going through the rest of your mail, I stopped here, and
thought I'd point out:
http://jeremy.zawodny.com/blog/archives/010699.html
You should be able to make it work just fine wi
Hi Everyone!
I am very new to qpsmtpd and I am trying to write my first plugin.
For starters I want to use qpsmtpd-async instead of the other options
available. Because of this I have been learning about how qpsmtpd
handles polling within the code. It looks like certain plugins are
available
Matt Sergeant wrote:
> Looks good.
>
> On Mon, 15 Dec 2008 08:06:28 +0100, Hanno Hecker wrote:
>> The attached diff should fix it. If Matt says it's OK, I'll commit it
>> later.
The patch works for me.
FYI: the current ident/p0f can't possibly work with the latest 2.0.8
p0f. Insufficient parame
Looks good.
On Mon, 15 Dec 2008 08:06:28 +0100, Hanno Hecker wrote:
> The attached diff should fix it. If Matt says it's OK, I'll commit it
> later.
On Mon, 15 Dec 2008 01:10:13 -0500
"Chris Lewis" wrote:
> qpsmtpd-async is missing settings for connection->local_ip and
> connection->local_port. Hence the p0f plugin (for example) won't work.
The attached diff should fix it. If Matt says it's OK, I'll comm
qpsmtpd-async is missing settings for connection->local_ip and
connection->local_port. Hence the p0f plugin (for example) won't work.
[The p0f plugin doesn't work for other reasons too, I'll be getting a
new copy sent in shortly.]
Matt Sergeant wrote:
>
> I'm thinking more on the lines of pushing back reads if they're not full
> lines.
>
> Probably needs a bit of support for that in lib/Danga/Client.pm
Attached is an attempt to do that. The reason for this is that I've seen
another case of end of data marker coming in t
Radu Greab skribis 2008-04-14 22:19 (+0300):
> $data =~ s/\r\n\.\r\n(.*)\z/\r\n/ms
If you don't want to use the regex engine (and indeed, especially
regexes with .* are often inefficient), you could use good old index and
substr to achieve the same:
# untested code
my $data_end = index(
Matt Sergeant wrote:
>
> >> I can't help feeling there's a better way to do it - I hate applying
> >> two
> >> regexps every time a DATA packet comes in... I'll have a think on
> >> it.
One option could be to keep this regexp
$data =~ s/\r\n\.\r\n(.*)\z/\r\n/ms
and, if it is not matched, the
On Mon, 14 Apr 2008, Guy Hulbert wrote:
On Mon, 2008-14-04 at 12:54 +, Matt Sergeant wrote:
Attached are a test script and a suggested patch.
I committed the patch 95% the same as yours.
I can't help feeling there's a better way to do it - I hate applying
two
regexps every time a DATA pa
On Mon, 2008-14-04 at 12:54 +, Matt Sergeant wrote:
> > Attached are a test script and a suggested patch.
>
> I committed the patch 95% the same as yours.
>
> I can't help feeling there's a better way to do it - I hate applying
> two
> regexps every time a DATA packet comes in... I'll have a
On Sat, 12 Apr 2008, Radu Greab wrote:
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended with CRLF.
Attached are a test script and a
On Mon, 14 Apr 2008, Matt Sergeant wrote:
On Sat, 12 Apr 2008, Radu Greab wrote:
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended
On Sat, 12 Apr 2008, Radu Greab wrote:
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended with CRLF.
Attached are a test script and a
Radu Greab wrote:
>
>
> Matt Sergeant wrote:
> >
> > Though I could have sworn I fixed this - are you sure you're testing
> > against latest SVN?
>
> I do not have the latest SVN in production. I have 0.43rc1 with
> additional patches, including your change #129 which, I think, is what
> you
Matt Sergeant wrote:
>
> Though I could have sworn I fixed this - are you sure you're testing
> against latest SVN?
Hi,
I do not have the latest SVN in production. I have 0.43rc1 with
additional patches, including your change #129 which, I think, is what
you are referring to as having fixed th
Ask Bjørn Hansen wrote:
On Apr 12, 2008, at 6:33, Radu Greab wrote:
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended with CRLF
On Apr 12, 2008, at 6:33, Radu Greab wrote:
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended with CRLF.
Hi Radu,
Can you add it
I found a case where qpsmtpd-async detects the end of data marker
incorrectly: the previous packet did not end with CRLF and the current
packet starts with .CRLF. The code assumes that the previous packet
ended with CRLF.
Attached are a test script and a suggested patch.
Thanks,
Radu Greab
Applied, thanks
On 10-Mar-08, at 5:09 PM, Radu Greab wrote:
I found that qpsmtpd-async can not deliver mail with queue/postfix-
queue
due to lack of permissions, the qpsmtpd-async process did not
belong to
the postdrop group.
Here is a patch to update qpsmtpd-async to set the
will send back the combined
output from all children?
Yes. Originally there was no -j option to qpsmtpd-async. But my
sysadmin bitched at me that we have 4 CPUs so I should use them all :-)
So the plan is either to do some sort of communication with the
children (that's setup now for th
Radu Greab wrote:
>
> The patch to qpsmtpd-async also closes the config socket in child. I
> think the child does not need that socket.
I used the config port for the first time today and I found that, if
my patch is applied, the config port becomes useless: you can connect
to it but
Sorry, somehow the description got lost.
I found that qpsmtpd-async may stop accepting SMTP connections, if the
child qpsmtpd-async dies and a new one is created.
The sequence of events leading to that is:
- parent starts running
- parent creates SMTP listening socket
- parent forks a child
I found that qpsmtpd-async may stop accepting new SMTP connections if a
child server dies and a new child is created.
The sequence of events leading to a closed SMTP socket was:
- parent creates the SMTP listening socket
- parent forks a child; the child inherits the SMTP socket
- child creates
I found that qpsmtpd-async can not deliver mail with queue/postfix-queue
due to lack of permissions, the qpsmtpd-async process did not belong to
the postdrop group.
Here is a patch to update qpsmtpd-async to set the supplementary UNIX
groups, like qpsmtpd-forkserver.
--- qpsmtpd-async.orig
Good morning,
> OK, and for prof.freud?...
now it works.
On 30-Jan-08, at 5:14 PM, mark warren bracher wrote:
Matt Sergeant wrote:
On 29-Jan-08, at 12:55 PM, [EMAIL PROTECTED] wrote:
So I'll need more info about your configuration.
ok, found something. this only happens, when I use logging/
adaptive.
If I take that out, the dnsbl starts to work.
Matt Sergeant wrote:
On 29-Jan-08, at 12:55 PM, [EMAIL PROTECTED] wrote:
So I'll need more info about your configuration.
ok, found something. this only happens, when I use logging/adaptive.
If I take that out, the dnsbl starts to work.
Can you send the output from enabling verbose mode (tw
On 29-Jan-08, at 12:55 PM, [EMAIL PROTECTED] wrote:
So I'll need more info about your configuration.
ok, found something. this only happens, when I use logging/adaptive.
If I take that out, the dnsbl starts to work.
Can you send the output from enabling verbose mode (two -v flags)
with cur
> So I'll need more info about your configuration.
ok, found something. this only happens, when I use logging/adaptive.
If I take that out, the dnsbl starts to work.
mark warren bracher wrote:
Matt Sergeant wrote:
On 29-Jan-08, at 11:42 AM, mark warren bracher wrote:
same config here, except I'm using qmail-queue.
OK - let me align versions. What version of qpsmtpd and what version
of ParaDNS?
qpsmtpd 0.40. I had ParaDNS 1.3, but I just upgraded to 1
Matt Sergeant wrote:
On 29-Jan-08, at 11:42 AM, mark warren bracher wrote:
same config here, except I'm using qmail-queue.
OK - let me align versions. What version of qpsmtpd and what version of
ParaDNS?
qpsmtpd 0.40. I had ParaDNS 1.3, but I just upgraded to 1.4 and tested
again, with t
On 1/29/08, Matt Sergeant <[EMAIL PROTECTED]> wrote:
> OK - let me align versions. What version of qpsmtpd and what
> version of ParaDNS?
qpsmtpd 0.42rc1 from trunk
ParaDNS 1.4
On 29-Jan-08, at 11:42 AM, mark warren bracher wrote:
same config here, except I'm using qmail-queue.
OK - let me align versions. What version of qpsmtpd and what version
of ParaDNS?
Matt Sergeant wrote:
On 29-Jan-08, at 2:53 AM, [EMAIL PROTECTED] wrote:
What steps will reproduce the problem?
qpsmtpd-async(rev 838) with dnsbl plugin enabled
The Problem is, qpsmtpd will never print out the initial 220, so that
the smtp dialog can start.
I don't see that:
$ cat c
On 29-Jan-08, at 2:53 AM, [EMAIL PROTECTED] wrote:
What steps will reproduce the problem?
qpsmtpd-async(rev 838) with dnsbl plugin enabled
The Problem is, qpsmtpd will never print out the initial 220, so that
the smtp dialog can start.
I don't see that:
$ cat config/plugins
async/
I'm taking a look.
On 29-Jan-08, at 2:53 AM, [EMAIL PROTECTED] wrote:
Dear friends,
I filed this also under code.google.com/p/smtpd as an 'Issue', but it
looked so deserted there.
What steps will reproduce the problem?
qpsmtpd-async(rev 838) with dnsbl plugin enabled
What
Dear friends,
I filed this also under code.google.com/p/smtpd as an 'Issue', but it
looked so deserted there.
What steps will reproduce the problem?
qpsmtpd-async(rev 838) with dnsbl plugin enabled
What is the expected output? What do you see instead?
15958 Plugins already loaded
159
On Mon, 11 Jun 2007, David Favor wrote:
1) async appears to start correctly and work correctly
when no -j given
OK.
2) when starting async incorrectly senses how Danga::Socket
will poll, which should access Danga::Socket->method()
Yup. That's minor, but easily fixed. It doesn't affect
On Jun 11, 2007, at 3:21 PM, David Favor wrote:
Let me know the preferred way to generate patches and I'll supply a
patch
next time.
"svn diff" (or any other way to make unified diffs) and submit it to
the Google Code issue tracker:
http://code.google.com/p/smtpd/issues/list
-
1) async appears to start correctly and work correctly
when no -j given
2) when starting async incorrectly senses how Danga::Socket
will poll, which should access Danga::Socket->method()
3) when started with '-j 2' errors tumble out, both processes
appear to start and messages appear to
David Favor wrote:
If the -j option is supplied, then CNTL-C leaves all processes
running. With no -j supplied, CNTL-C seems to shutdown the single
process correctly.
I thought you couldn't get it started? ;-)
What OS and Perl version are you on?
If the -j option is supplied, then CNTL-C leaves all processes
running. With no -j supplied, CNTL-C seems to shutdown the single
process correctly.
- David
--
Like feeling your best ever, all day, every day? Here's how...
Your simple secrets are here - http://RadicalHealth.com
[EMAIL PROTECTED] 0.40]# ./qpsmtpd-async --user=root -j=2
28721 Loaded Qpsmtpd::Plugin::logging::warn=HASH(0x9913790)
28721 trying to get config for plugins
28721 trying to get config for plugin_dirs
28721 logging::file hooking connect
28721 logging::file hooking disconnect
28721 trying to get
t;);
As the code is now:
my $POLL = "with " . ($Danga::Socket::HaveEpoll ? "epoll()" :
$Danga::Socket::HaveKQueue ? "kqueue()" : "poll()");
qpsmtpd-async will always report using "poll()".
Let me know the preferred way to g
75 matches
Mail list logo
