For purposes of comparison
Hey all, I've lurked here for a little while but haven't popped in to say anything til now ;) I've been doing some performance analysis of a qpsmtpd instance I have set up. Using async with SPF,database-driven rcpt to checker,anglebrackets,logging/file,queue/smtp-forward can drop ~76msgs per second to invalid senders and deliver ~23 msgs per second to valid recipients. I'm guessing that the slowdown of the latter would be due to the non-async nature of the smtp-forward plugin? Has anyone rewritten it in an async way and/or anyone have a better way for me to eventually queue this to a postfix installation? In addition, do these figures line up with anyone else's? This is v4 of qpsmtpd-async running on a dual 2.8ghz xeon with 4gb of ram with -j 4 (and it beats on the cpu pretty good during the stress tests). Thanks all, Tom Callahan
Re: Hi, bug report/feature request
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 being called. The > $self->log() record referencing ciphers from init() doesn't appear in > the logs. I have not been able to do much with async at all, because the production site I have been supporting (even though I've not been at that job for a month) use way too many unsupported plugins for async to cope. This may be a Matt question.. John
Re: Hi, bug report/feature request
On Oct 3, 2007, at 11:09, Chris Lewis wrote: Running 0.40 qpsmtpd-async as a spamtrap on both Linux and Solaris (2.8/2.9). [I use ordinary poll on Linux because my OS is too old] I've hacked qpsmtpd-async to support daemonization and pid locking files. Rather than dig into SVN, who should I send the modified copy to? Matt? A patch from current SVN put into the issues tracker is ideal; but any format is better than nothing. :-) We can even put it into 0.42 as we still have an outstanding qpsmtpd- prefork fix to do before the release... - ask -- http://develooper.com/ - http://askask.com/
Re: Hi, bug report/feature request
On 3-Oct-07, at 5:25 PM, James Turnbull wrote: Chris Lewis wrote: I've hacked qpsmtpd-async to support daemonization and pid locking files. Rather than dig into SVN, who should I send the modified copy to? Matt? Chris Since no one else answered the question I'd recommend logging a ticket at http://code.google.com/p/smtpd/issues/list and attaching the patch there. Sorry, yes please do that. Or just mail the patch to the list. Either works. Matt. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Re: Hi, bug report/feature request
Chris Lewis wrote: > I've hacked qpsmtpd-async to support daemonization and pid locking > files. Rather than dig into SVN, who should I send the modified copy > to? Matt? > Chris Since no one else answered the question I'd recommend logging a ticket at http://code.google.com/p/smtpd/issues/list and attaching the patch there. Cheers James Turnbull -- James Turnbull <[EMAIL PROTECTED]> --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/159059/) --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40) signature.asc Description: OpenPGP digital signature
Re: Hi, bug report/feature request
John Peacock wrote: 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 shouldn't be running that script as root in any case). True enough. I'm sure that there is a platform-independent way to get the hostname, but for the moment you can just call the script (not as root) with ./plugins/tls_cert --CN your.host.name [Aside from the error hostname will throw.] and the cert will still be created (or you can pass in all of the other options as well, if you care what your cert looks like). I'll look to protect that `hostname` call... 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 being called. The $self->log() record referencing ciphers from init() doesn't appear in the logs.
Re: Hi, bug report/feature request
Robin Bowes wrote: John Peacock wrote: I'm sure that there is a platform-independent way to get the hostname How about: use Sys::Hostname; $host = hostname; Returns the non-qualified hostname (at least on this Solaris). I guess when it boils down to it, this machine is misconfigured. Sigh.
Re: Hi, bug report/feature request
John Peacock wrote: > > I'm sure that there is a platform-independent way to get the hostname How about: use Sys::Hostname; $host = hostname; R.
Re: Hi, bug report/feature request
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 shouldn't be running that script as root in any case). I'm sure that there is a platform-independent way to get the hostname, but for the moment you can just call the script (not as root) with ./plugins/tls_cert --CN your.host.name and the cert will still be created (or you can pass in all of the other options as well, if you care what your cert looks like). I'll look to protect that `hostname` call... John
Hi, bug report/feature request
Running 0.40 qpsmtpd-async as a spamtrap on both Linux and Solaris (2.8/2.9). [I use ordinary poll on Linux because my OS is too old] I've hacked qpsmtpd-async to support daemonization and pid locking files. Rather than dig into SVN, who should I send the modified copy to? Matt? 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. Unfortunately, this OS is obnoxious, and tends ot have non-qualified hostnames (under hostname, and Sys::Hostname). So, not sure what to suggest here.
Too many open files at lib/Qpsmtpd.pm
qmsptmd-forkserver 0.32 I am seeing this error, increasingly, but far from being for every connection: could not open configfile ./config/logging: Too many open files at lib/Qpsmtpd.pm line 168, line 1430. The last item is sometimes different. I presume the last item is another process qpsmtpd is trying to run. When this happens for a connection, I may end up with hundreds of these lines in the log file. Is there some place I should be increasing the number of open files allowed? Where and how? Thanks.
Re: Reply ID & from Name
Anilkumar wrote:
Dear All,
I am intrested in knowing the From Name of mail
sender & his reply e-mail id,
what will be the command for it.
$transaction->header->get("From")
-Johan
--
Johan Almqvist
Christies gate 34 A
0557 Oslo
Norway
Mobile: +47 40 04 68 21
E-mail: [EMAIL PROTECTED]
