This doesn't look like it's email originating from your system.
Instead, it looks like spamdyke has accepted the message and then qmail
is doing the rejection. My guess is that it passes through spamdyke
with an invalid destination user. Qmail then tries to reject it.
You can avoid this by
Don't you need a private key file as well? Mine has:
tls-certificate-file=fullchain.pem
tls-privatekey-file=privkey.pem
On 10/12/2016 03:31 PM, marek--- via spamdyke-users wrote:
I read an old thread on this problem, but did not see a solution.
# spamdyke -v
spamdyke
ld show
the IP address right after the username, separated by a space. (NOTE:
I haven't compiled or tested this change, proceed with caution...)
-- Sam Clippinger
On Jul 22, 2016, at 6:17 PM, Gary Gendel via spamdyke-users
<spamdyke-users@spamdyke.org <mailto:spamdyke-users
Sam,
Is there a way to get spamdyke to log invalid authorizations in a manner
that fail2ban can use? My host has been hit continuously with
brute-force attacks. Unfortunately, the logs only have:
Jul 22 18:54:43 tardis spamdyke[26727]: [ID 702911 mail.info]
FILTER_AUTH_REQUIRED
Jul 22
Faris,
Looks like it does. From the documentation in the section on Reverse DNS:
When matching an IP address in an rDNS name, spamdyke looks for the IP
address in many forms; for example, if the IP address is 11.22.33.44,
spamdyke will look for the following patterns in the rDNS name (the
Sam,
I've started a discussion on the OpenIndiana developer's mailing list
about Spamdyke and generated a lot of interest. I know you're working
on divorcing Spamdyke from Qmail and also supporting IPv6. How is this
work progressing? It seems that IPv6 seems to be a sticky point for
show the AUTH lines
in every case.
How did you install qmail? Is this netqmail or Plesk or QTP or?
-- Sam Clippinger
On Aug 24, 2015, at 11:42 AM, Gary Gendel via spamdyke-users
spamdyke-users@spamdyke.org mailto:spamdyke-users@spamdyke.org wrote:
Sam,
Yes I'm on 5.0.1.
I've
Gendel via spamdyke-users
spamdyke-users@spamdyke.org mailto:spamdyke-users@spamdyke.org wrote:
Sam,
If I use qmail with smtp auth, then spamdyke announces STARTTLS
capabilities, but if I have spamdyke do it then it doesn't. It's
there and works, but it isn't announced in the ehlo response
Sam,
If I use qmail with smtp auth, then spamdyke announces STARTTLS
capabilities, but if I have spamdyke do it then it doesn't. It's there
and works, but it isn't announced in the ehlo response.
gary@abby ~ openssl s_client -starttls smtp -crlf -connect
tardis.genashor.com:587 -starttls
I use port 22 for non-auth mail and 587 for TLS with auth mail. On 587
I ended up using postfix because I could never get spamdyke working. It
always failed valid authorizations.
I was putting together a new server and I decided to take another look.
The problem ended up in the
to let it go. If spamdyke can forward connections
from port 25 to port X while doing all the filtering it does now, it
should work nicely with just about any other mail server.
-- Sam Clippinger
On Aug 18, 2015, at 12:03 PM, Gary Gendel via spamdyke-users
spamdyke-users@spamdyke.org
Phil,
The greylisting feature of Spamdyke kicks in after whitelisting and
blacklisting operations. If these operations don't specifically reject
or accept the incoming email then it is chosen for greylisting. I
suggest you scan it's features from the spamdyke homepage. It sounds
like it
12 matches
Mail list logo
