Hi all,
I've spent quite a few hours trying to install qpsmtpd, with only limited
success. Here are some of the issues:
1. Does qpsmtpd need to be "compiled" and installed? This article
http://searchopensource.techtarget.com/tip/0,289483,sid39_gci1235770,00.html
by James Turnbull, which is very
Hi all,
I've spent quite a few hours trying to install qpsmtpd, with only
limited success. Here are some of the issues:
1. Does qpsmtpd need to be compiled and installed? This article
http://searchopensource.techtarget.com/tip/0,289483,sid39_gci1235770,00.html
by James Turnbull, which is very
(sorry about the duplicate posts!)
Thank you for your reply, Michael!
Michael Holzt wrote:
# ./qpsmtpd-forkserver
without the -u parameter (which is supposed to default to smtpd) results in the
message:
Could not create spool_dir /root/tmp/: Permission denied at lib/Qpsmtpd.pm line
464.
Why w
Thank you for your additions and encouragement, Guy!
Your findings are a bit scary, especially
(Is anyone running this in production ?? How ??).
The option to use AUTH is tempting, but I'm not confident I can handle
bleeding edge code...
The point about stripping down the plugins is a
Please bear with me -- I have to take this one step at a time...
Peter seems to favor the distributed (make install) approach and Michael
the all-in-one-place. I think I have a better chance to get up and
running with the latter, at least initially. If I have a user smtpd with
a home directory
Thank you very much for posting the updated files, Peter!
Peter J. Holzer wrote:
The other two files (which are now almost trivial) don't concern qpsmtpd
directly. They are also not completely generic: They expect a certain
file system layout and also some details of the configuration. So at the
Guy Hulbert wrote:
Since you are running Suse, the easiest thing to do might be to try
building 0.32 from Peter's .rpm files (I believe he has source ones for
everything).
He has RedHat and Debian. I'm a bit scared to mess up something by
trying to install a package that may or may not work
James Turnbull wrote:
What I meant to add was that the xinetd page got rolled into the
deployment options summary - it seemed unnecessary to have a page
dedicated to x(inetd) alone - the content of the page was changed to
mention Peter's patch. I'll update the
http://wiki.qpsmtpd.org/deploy:start
Peter,
I dumped the idea of running qpsmtpd from the smtpd directory and
instead followed James Turnbull's instructions at
http://searchopensource.techtarget.com/tip/0,289483,sid39_gci1235770,00.html
to install 0.3x.
This means
# perl Makefile.PL
# make
# make install
all the way to
# mkdir
Thank you, Guy! I feel stupid to ask questions that have such simple
answers...
Guy Hulbert wrote:
On Thu, 2007-25-01 at 07:02 +0100, Hans Salvisberg wrote:
finding the plugins. How can I tell it where the plugins are?
You can add a config file called 'plugin_dirs' in which you
Ok, now I have a second server where perldoc is hosed...
perldoc README
worked just fine. Then I ran
perl Makefile.PL
make
make test
make install
make clean
After that
perldoc README
only returns
No documentation found for "README".
Is this an intentional side effec
Hi John,
Thank you for your reply!
John Peacock wrote:
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?
qpsmtpd 0.3x is running under xinetd and the basic functionality is
working fine, especially the check_verybadrcptto plugin.
Now I'd like to enable greylisting and I inserted
greylisting mode testonly db_dir /home/smtpd/data
and set the data directory as follows
drwx-- 2
Thank you for your reply and explanation, Peter
Peter J. Holzer wrote:
Since the greylisting module can get the dbdir from a variety of sources
it probably should check and untaint it itself. My variant does this:
I looked at your doc at
http://www.hjp.at/projekte/qpsmtpd/denysoft_greylist/
Thank you for your detailed reply, Peter!
Peter J. Holzer wrote:
"/denysoft_greylist.dbm" within the config directory is used.
According to the various installation HOWTOs, the config directory
(/etc/qpsmtpd in my case) should be set like
drwxr-x--- 2 root smtpd 1024 Feb 2 12:15
This is also very interesting for learning how qpsmtpd works, but I see
some strange output in my log file:
dispatching RCPT TO: <[EMAIL PROTECTED]>
to email address : [<[EMAIL PROTECTED]>]
DENIED by rcpt_ok
550 Relaying denied (#5.7.1)
This occurs about 50 times in a row in the sam
Michael Holzt wrote:
This occurs about 50 times in a row in the same process with the same
remote address. Why should rcpt_ok be run last (that's what it says
inside the file)? After all this is a pretty basic and cheap test.
No. rcpt_ok _finally_ decides to accept or reject a message. It must
Hanno Hecker wrote:
Yes, it's the wrong place for creating connections to a DB. Maybe you
haven't seen it yet, this is from my (upcoming) plugin doc
(http://ankh-morp.org/~vetinari/tmp/plugins.pdf -> chapter 2.1)
I've been looking for something like this. Please allow me to make some
comments a
Why does qpsmtpd accept email addresses that contain characters like 'é'
(eacute), which aren't really defined?
RFC 2821 says:
Systems MUST NOT define mailboxes in such a way as to require the use
in SMTP of non-ASCII characters (octets with the high order bit set
to one) or ASCII "con
I run some of my domains with a catch-all address (i.e. no recipient
checking), and I have a considerable number of retired addresses there.
Many were never in actual use but have been invented by spammers! With
this setup check_verybadrcptto takes care of about half of my spam,
because a lot o
Thank you for your reply, Peter!
Peter J. Holzer wrote:
Hmm. If you are running a domain with catch-all, worrying about the
efficiency of reading/writing a single record in a dbm file seems like
putting the cart before the horse to me.
Ok, got that. Will greylisting ever purge records, or does
Thanks for your reply, Gavin!
Gavin Carr wrote:
What's your primary concern here Hans? That noting the connection in
the greylisting db is relatively expensive? Or that you're 'polluting'
the database with connections from IPs that you're going to deny soon
anyway (i.e. more database size)?
Al
Is there a hook that is always fired at the end of a connection under
xinetd?
If qpsmtpd disconnects, then hook_disconnect() and
hook_post_connection() are fired. But if the other side disconnects
without a QUIT, then neither of them are fired.
Hans
Hanno Hecker wrote:
On Wed, 28 Feb 2007 20:52:21 +0100
Hans Salvisberg <[EMAIL PROTECTED]> wrote:
Is there a hook that is always fired at the end of a connection under
xinetd?
If qpsmtpd disconnects, then hook_disconnect() and
hook_post_connection() are fired. But if the othe
ps ax shows this:
24195 ?Rs 306:26 /usr/bin/qpsmtpd [208.250.48.181 :
post.taipan2.net : 15:21:08 2007-02-26]
26546 ?Rs 290:14 /usr/bin/qpsmtpd [208.250.48.181 :
post.taipan2.net : 15:51:17 2007-02-26]
27702 ?Rs 288:06 /usr/bin/qpsmtpd [208.250.48.181 :
post.taip
Hi All,
When using qpsmtpd (trunk) to relay outgoing messages, it constructs a
Received header that contains among other information
-- the SMTP authorization mechanism
-- the SMTP authorization username
-- the qpsmtpd version number
I know that obscurity does not provide security, but u
Matt Sergeant wrote:
1) If the sender meant to send the mail, then the recipient knows who
the user is anyway.
The sender may be sending email to mailing lists, which broadcast his
username to the world at large.
Try this
http://www.google.com/search?q=%22smtp-auth+username%22+qpsmtpd
i
Matt Sergeant wrote:
On 8-Apr-07, at 7:06 PM, Hans Salvisberg wrote:
Matt Sergeant wrote:
1) If the sender meant to send the mail, then the recipient knows who
the user is anyway.
The sender may be sending email to mailing lists, which broadcast his
username to the world at large.
Yup
Matt Sergeant wrote:
On 9-Apr-07, at 12:56 AM, Hans Salvisberg wrote:
Matt Sergeant wrote:
On 8-Apr-07, at 7:06 PM, Hans Salvisberg wrote:
Matt Sergeant wrote:
1) If the sender meant to send the mail, then the recipient knows
who the user is anyway.
The sender may be sending email to
Hans Salvisberg wrote:
Yes, this works great -- thank you!
I spoke a bit too soon. There's a strange problem that I don't
understand (maybe my lack of Perl skills): the string that I return is
truncated at the first newline. If I omit the newlines, I can set a very
long Received h
Matt Sergeant wrote:
On 9-Apr-07, at 8:34 PM, Hans Salvisberg wrote:
Hans Salvisberg wrote:
Yes, this works great -- thank you!
I spoke a bit too soon. There's a strange problem that I don't
understand (maybe my lack of Perl skills): the string that I return is
truncated at
Matt Sergeant wrote:
On 10-Apr-07, at 12:57 PM, Hans Salvisberg wrote:
It should produce the standard header, except for a few additional
spaces after "from", so I can be sure that my code is used. It's taken
straight out of SMTP.pm, with the addition of "qp->"
Werner Fleck wrote:
I have changed the plugin so that it, in addition to "<>" as the sender
of bounces, fires when the user part of the envelope sender is
"MAILER-DAEMON". This might not be RFC conforming, but since I get a lot
of these I am blocking them.
During a recent misdirected bounces
Since this thread is still active, I'll add my 2 cents:
Werner Fleck wrote:
I did not mean forged bounces but real bounces for forged mails.
Spammers discovered my domains some months ago and are increasingly
using them for forged mails. I am using SPF to protect my domains but if
other mail s
Werner Fleck wrote:
I'm using a different email address for almost every party I communicate
with. This way I can trace who is giving away my email address and I can
block an address if it is misused. The drawback is, that I cannot use
something like check_goodrcptto because I do not know all t
Some of my clients use outgoing SMTP; they access from changing
residential IPs and do TLS and then SMTPAUTH via the auth_imap plugin.
I've just installed Peter's denysoft_greylist, and now I find that
they're being greylisted, which doesn't make sense.
I could probably use whitelistsenders to
David Nicol wrote:
I would purpose
the existing IP address to the customers and give the inbounds a new IP.
Thank you for your reply, but there are only four users in this
organization and I can't use more than one IP for them.
Hans
Peter J. Holzer wrote:
so try changing $ENV{RELAYCLIENT} into
$self->qp->connection->relay_client() and see if that works.
Yes, this works perfectly! There's no harm in keeping the "obsolete
method" and just adding the new one.
Thanks a lot!
Hans
Elliot Foster wrote:
It's been a while so there might be more that I've forgotten. This
allowed me to run one process to relay and accept mail, but be able to
enforce receiving mail separately from relaying clients. Let me know if
you're interested in any of the above.
Thank you for your rep
Hi List
I've been happily running qpsmtpd 0.33-dev from xinetd for close to two years
now, with the following configuration:
service smtp
{
flags = REUSE
socket_type = stream
protocol= tcp
wait= no
user= smtpd
Hanno Hecker wrote:
> > What am I doing wrong?
> Nothing .)
Thanks for restoring my sanity!
BTW, does it make any difference whether I install qpsmtpd as in...
perl Makefile.PL
make
make test
make install
make clean
... or not?
I'll be happy to test the updated trunk. Sorry to come in so lat
Yes, this works, Thank you very much for the quick fix!
Now on to configuration!
Hans
Hanno Hecker wrote:
> This is a quick fix. I'm not sure if we solve it this way in SVN, but
> it fixes the seen error :)
>
> Hanno
What's the difference between installing qpsmtpd as in...
perl Makefile.PL
make
make test
make install
make clean
... or running it directly from /home/smtpd/qpsmtpd?
Presently I'm running ./qpsmtpd from xinetd, so the installed copy is probably
wasted, right?
Is there any benefit/downside in
I've set rlimit_as=UNLIMITED (8GB in the host) and this hasn't made any difference.
Actually, the culprit is not dkim but dmarc. Commenting out dmarc lets the mails come in.
(I can't try it the other way around, because dmarc crashes if dkim isn't active.)
Hans
Gesendet: Sonntag, 0
No, I don't think this has made any difference.
This is the error output written for an outgoing mail, i.e. submitted by an authorized user, after applying the patch:
...
4358 4358 click, disconnecting
4358 4358 (post-connection) connection_time: 1.528 s.
4358 FATAL PLUGIN ERROR [lo
Hmm...
Install
Install.Authentication
Install.Starttls
on https://github.com/smtpd/qpsmtpd/wiki/Install.Authentication suggests that you set up authentication without tls (it's commented out in config.sample) and only activate tls in a third step. Only the third page says
"Notice now t
Going to the new HEAD
b1abc66 - qpsmtpd: Add additional dependency for geoip: Math::Complex. (2015-01-03 18:29:08 +0100)
has brought some relief:
Handle 2 now gives me only 7 instances of
FATAL PLUGIN ERROR [logging::file_3a7]: Can't call method "notes" on unblessed reference at /ho
I like configuring a debug log as
logging/file:7 loglevel LOGDEBUG nosplit tsformat %F_%T /var/log/qpsmtpd/7-debug-%F_%H%M%S.log
In spite of the presence of "nosplit", the logs (with the %S in the filename) are typically broken into three files.
Incidentally, it would be nice to
.pm line 93.
Deep recursion on subroutine "Qpsmtpd::run_hooks_no_respond" at lib/Qpsmtpd.pm line 105.
Out of memory!
Hans
Gesendet: Montag, 05. Januar 2015 um 01:35 Uhr
Von: "Matt Simerson"
An: "Hans Salvisberg"
Cc: "Jared Johnson" , "qpsmtpd@perl.org
For the record:
Matt suggested to use PHP to send via SMTP to localhost. I've found https://github.com/PHPMailer/PHPMailer and a Drupal module of the same name that makes it available in Drupal. This works pretty much out of the box. Thanks!
Hans
Gesendet: Montag, 19. Januar 2015 um 22
Those have been fixed in the meantime.
(Hard to explain why I didn't see them when I posted the original
message...)
Hans
On 2015-02-13 15:05, John Crisp wrote:
> On 03/01/15 18:10, salvi...@gmx.ch wrote:
>> summarize is broken, too, in HEAD as well as in commit ee01a07 (2014-12-22
>> 15:01:12
Hi All,
Once again I'm installing qpsmtpd (the current HEAD at this point) on a
new server and having some trouble.
The first issue was installing Mail::SPF -- I got the test failure
described here:
https://rt.cpan.org/Public/Bug/Display.html?id=116421
and I used "force" to install anyway
use-bugs/2016-06/msg04186.html
Hans
On 2016-09-22 08:27, Hans Salvisberg wrote:
Hi All,
Once again I'm installing qpsmtpd (the current HEAD at this point) on
a new server and having some trouble.
The first issue was installing Mail::SPF -- I got the test failure
described here:
It turns out there are more -T issues in Net:DNS.
I'm running on Ubuntu 14.04 which has perl 5.18.2. Is this a problem
with that perl version?
Is there a work-around, or what can I do?
Hans
On 2016-09-24 17:25, Hans Salvisberg wrote:
The line 570 in /usr/local/share/perl/5.18.2/Ne
that seems to be current.
Hans
On 2016-09-24 20:49, Richard Siddall wrote:
What version of Net::DNS do you have?
Richard.
Hans Salvisberg wrote:
It turns out there are more -T issues in Net:DNS.
I'm running on Ubuntu 14.04 which has perl 5.18.2. Is this a problem
with that perl ve
I found the fix -- it's the patch in
https://rt.cpan.org/Public/Bug/Display.html?id=114819#txn-1632799
Apparently it's an issue that came in in 1.06 and should be fixed in 1.07.
Thanks,
Hans
On 2016-09-25 10:10, Hans Salvisberg wrote:
Thank you for your reply, Richard!
I'm
56 matches
Mail list logo
