Status: New
Owner:
New issue 32 by stua...@longlandclan.yi.org: qpsmtpd doesn't work with
sslserver
http://code.google.com/p/smtpd/issues/detail?id=32
Hi all,
I'm trying to get SMTPS (that is, SMTP over SSL; rather than STARTTLS)
working as that's what the mail client in my phone
Status: New
Owner:
New issue 30 by leif...@gmail.com: Does not accept mail if first MX is ipv6
only
http://code.google.com/p/smtpd/issues/detail?id=30
If the domain of an incoming message has (the first?) MX as ipv6 only,
qpsmtpd 0.82 rejets the message 450 Could not resolve
Updates:
Status: Fixed
Comment #2 on issue 29 by a...@develooper.com: Qpsmtpd::config caches
default value instead of real value
http://code.google.com/p/smtpd/issues/detail?id=29
(No comment was entered for this change.)
--
You received this message because you are listed in the
Comment #1 on issue 29 by pholzer: Qpsmtpd::config caches default value
instead of real value
http://code.google.com/p/smtpd/issues/detail?id=29
fix is now in
http://github.com/hjp/qpsmtpd/commit/5f02ea6ef1ee905bfc25ab18f3116749f61e0b1c
and
I
sent a pull request to abh.
--
You received
Status: Accepted
Owner: pholzer
New issue 29 by pholzer: Qpsmtpd::config caches default value instead of
real value
http://code.google.com/p/smtpd/issues/detail?id=29
What steps will reproduce the problem?
1. Change any configuration setting (via hook_config or get_qmail_config)
for which a
Comment #2 on issue 27 by hanno.hecker: Add module requirements to the
META.yml file
http://code.google.com/p/smtpd/issues/detail?id=27
http://www.perlfoundation.org/perl5/index.cgi?meta_yml
... at least a list of required recommended modules not in the perl core
distribution
would be
Issue 27: Add module requirements to the META.yml file
http://code.google.com/p/smtpd/issues/detail?id=27
New issue report by [EMAIL PROTECTED]:
I'm not actually sure what this is about, but it was a note in the STATUS
file.
Issue attributes:
Status: New
Owner: [EMAIL
Issue 28: Use ESMTPA in received headers for authenticated connections
http://code.google.com/p/smtpd/issues/detail?id=28
New issue report by [EMAIL PROTECTED]:
use keyword ESMTPA in Received header in case of authentication to
comply with RFC 3848.
Is this something we actually want to do?
Issue 26: spamassassin plugin rename subject if spam score = threshold
http://code.google.com/p/smtpd/issues/detail?id=26
Comment #1 by [EMAIL PROTECTED]:
Thanks for the report. I think the code is doing the right thing and
what is expected, but you are right the
documentation is off.
I
Issue 25: qpsmtpd-async: premature end of data
http://code.google.com/p/smtpd/issues/detail?id=25
New issue report by [EMAIL PROTECTED]:
What steps will reproduce the problem?
1. Send a mail to qpsmtpd-async instrumented so that when the mail data is
transmitted, the payload of a TCP packet
Issue 23: [Patch] Making postfix-queue use the cleanup socket path parameter
http://code.google.com/p/smtpd/issues/detail?id=23
Comment #3 by ahansen:
(No comment was entered for this change.)
Issue attribute updates:
Status: Feedback
--
You received this message because you are
Issue 22: Greedy regexps cause false hits on Hi virus
http://code.google.com/p/smtpd/issues/detail?id=22
New issue report by jdhedden:
Some of my emails to the p5p mailing list have been rejected. I traced it
to 'greedy' regexps in the hi virus plugin in qpsmtpd. The following is a
portion of
Issue 16: [patches for tls problem with unrecognized_command_response + bug in
prefork for IO::SOCKET::INET]
http://code.google.com/p/smtpd/issues/detail?id=16
Comment #1 by [EMAIL PROTECTED]:
- second patch (except for $renice stuff) fixed in rev 760.
- first: not going to fix it this way... a
Issue 20: Make default configuration location more sensible
http://code.google.com/p/smtpd/issues/detail?id=20
Comment #2 by matt.harrell:
I'm not sure I understand the problem but I can check since I do run Debian. It
looks like the init.d file that starts it is setting QPSMTPD_CONFIG to
14 matches
Mail list logo
