Is there a way we could get a configuration for a timer to be set on
blacklist items in any blacklist?
For instance when I configure firewall rules and use address lists I
always use a timer on these list
to be removed from the list after a certain amount of time but the rule
is always there so
Thats where I was headed with this one..
UGH!
How annoying.
We need a honeypot approach for these guys and then tarpit them into a
blackhole.
I will post a resolve on this once a I try a few things.
thanks
Dave
On 06/03/2014 11:19 AM, Angus McIntyre wrote:
On Jun 3, 2014, at 11:25 AM, David
Just found out my spamassassin doesnt seem to be working..
Ill post logs soon
On 06/03/2014 09:10 PM, Eric Shubert wrote:
I haven't seen this sort of thing in quite some time (thankfully).
Have you sent them through sa-learn so bayes can detect them?
Ok,
found the issue..
We use webmin to admin alot of servers and a few weeks ago we attempted
to write a rule that would detect certain phrases within
a body of the message and when it was applied all seemed fine but webmin
did not know how to properly restart spamd.
Anyways looking into
Yes,
sorry,
I posted resolution there.
Fixed by cleaning all email accounts and correcting tcp.rules then
adding a spam assassin rule to catch all
email with a common phrase html tag
Thanks
Dave
On 06/23/2014 03:12 PM, Eric Shubert wrote:
You got this resolved on the QMT list, right?
I have two server. One I install the latest spamdyke v3.1.1, let's call this
server A and the other server B.
Both
have spamdyke v3.1.1, using plesk. But when I send email via webmail
from server A to the server B email, some how the email cannot be
delivered.
When I check server B the log shows
I would like to report that v3.1.0 also suffer from the same issue as described
below.
So now I am back to v3.0.1, I think many mail will be missing if I continue to
test.
I believei it should be able to resolve quickly.
- Original Message
From: david boh [EMAIL PROTECTED
/etc/xinetd.d/smtp_psa file and your spamdyke
configuration file (if you have one)?
-- Sam Clippinger
david boh wrote:
I would like to report that v3.1.0 also suffer from the same issue as
described below.
So now I am back to v3.0.1, I think many mail will be missing if I
continue
/spamdyke --config-file
/var/qmail/spamdyke/spamdyke.conf /var/qmail/bin/relaylock
/var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true
/var/qmail/bin/cmd5checkpw /var/qmail/bin/true
I need to update the documentation to include this.
-- Sam Clippinger
david boh wrote:
Sure
: [spamdyke-users] Problem in v3.1.1 make it un-usable.
This is very strange. When the messages remain in the queue, are you
seeing any errors in the qmail logs? Can you enable spamdyke's full
logging on the receiving server and send me a log of a failed delivery?
-- Sam Clippinger
david boh
Hi Marc,
i can't say wich are best, but i can tell you wich we're using:
check-dnsrbl=sbl-xbl.spamhaus.org
check-dnsrbl=list.dsbl.org
check-dnsrbl=zombie.dnsbl.sorbs.net
check-dnsrbl=dul.dnsbl.sorbs.net
check-dnsrbl=bogons.cymru.com
And also don't forget to block the unresolvable
blows
your hdd. :-D
Regards,
David
Am 05.03.2008 um 16:03 schrieb Marc Van Houwelingen:
Arne, David -
Thanks you both for your replies. Unfortunately *all* the hosts you
sent me
are either gone or down - not one of them resolves to an IP, with the
exception of dnsbl.sorbs.net, which I'm
Hi,
i made a full Programm for that incl. an overview for Plesk. If you're
interested i would like
to give it to you. I'm using PHP-CLI and a cron analyzing the logs.
Regards,
David
Marcin Orlowski schrieb:
Jake Briggs wrote:
But seriously, getting simple rough stats from the logs really
Hi Nightduke,
sure, just give me an hour (or two) to make a package from that, as it's
not very general atm.
I'll publish that on my private site later on and give you a link to
check it out. Do you also
want the stuff for plesk, or just analyzing the logs?
David
nightduke schrieb:
David i
Hi Stefan,
ich hatte mal ein ähnliches Problem, wo die Greylist-Files den falschen
User hatten und Spamdyke diese
nicht überschreiben konnte. Alle Greylist-Files sollten den passenden
User haben. Bei mir ist das
qmaild.nofiles.
Gruß,
David
---
Hi Stefan,
i had a similar Problem, where all
So here you can see my first steps:
http://www.php-schnippsel.de/archives/8
David Stiller schrieb:
That's close to what i've made. ;)
Stefan Pausch schrieb:
I would love to get my hands on that package as well. I am working on
a log analyzing script, too and would love to see how
Another thing - did you figure out, how to implement an own programm
into Plesk using the right
template and check for logins? I think the way i did it, it may be a
little insecure as it could be
opened without any login by the direct url...
David Stiller schrieb:
That's close to what i've made
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Snow schrieb:
Hi!
I would have a wishlist for spamdyke, because it is a real gret software,
and I plan to use it in all of my installations.
1. It would be nice if I can quarantine everykind of message. I'm thinking
of the messages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Stefan,
dynamic IP's need a dynamic whitelist. For exampe write a 30-min-cron,
looking for your
dyndns-hostname's IP and refresh spamdyke's whitelist. Something like
this should do the trick.
#!/bin/bash
WL=/var/qmail/spamdyke/whitelist_ip
/listinfo/spamdyke-users
David Stiller
Technischer Support
Blackbit Neue Medien GmbH
Ernst-Ruhstrat-Straße 6 - D-37079 Göttingen
tel.: +49 [551] 50675-60 - fax.: +49 [551] 50675-20
email: [EMAIL PROTECTED] - hotline: [EMAIL PROTECTED]
Klassische Werbung und Online-Marketing: http://www.blackbit.de
: [spamdyke-users] Strage happend (time to time)
Here is a quote from my spamdyke.conf:
reject-empty-rdns
reject-unresolvable-rdns
reject-ip-in-cc-rdns
BTW - spamdyke works with file blacklist_keywords not so good as
we need...
On Thu, 10 Jul 2008 13:50:24 +0200
David Stiller [EMAIL PROTECTED
I agree. Great work!
One thing i just noticed: Spamdyke gave me an error writing to the
greylist. To a folder and file called _none. Maybe it's a config-
issue?
It tried to write to my graylist like this:
/var/qmail/spamdyke/greylist-dir/domain/_none/_none
Maybe it was an exception, but where
ln -s /usr/local/bin/spamdyke-4.0.2 /usr/local/bin/spamdyke
Regards,
David
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Spamdyke already does that on my system, like this:
Aug 19 14:18:59 plesk-mail spamdyke[29178]:
ALLOWED
from: [EMAIL PROTECTED]
to: [EMAIL PROTECTED]
origin_ip: 84.132.147.168
origin_rdns: ***.dip0.t-ipconnect.de
auth: w.viertel
Or do you mean, you
with outgoing mails.
Regards,
David
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
Hi all!
I created a bash-script to analyze and clean up my greylist. Maybe
someone needs one which
reports what has been done or just check the greylist without deleting.
I use this one, because a simple find over 90 Domains and 2k
Mailaccounts caused high
server load, this step-by-step
guess that these errors are very
likely caused by the same bugs that have been plaguing David Stiller on
SLES 10.1 64-bit. I've been working with David for several weeks to
identify the source of the crashes and I believe I've finally done it.
The latest beta version (published
. Also, your server is crashing at address
0 as well, it just prints it in a different format ().
I don't _know_ if this is the same bug, I just _hope_ that it is. :)
-- Sam Clippinger
David Stiller wrote:
A little difference to my system is that he'd been told
,
even if valid recipients could still possibly be given. Thanks to David
Stiller for reporting this one.
Fixed the handling of unencoded null characters in messages
(technically not legal) so spamdyke does become confused and timeout. Thanks
to Arthur Girardi for reporting this one
Maybe it's just the particular order spamdyke is running the filters?
I would try to set the blacklist-ip by IP-Range, if it catches before
the Greylist.
Look at the FAQ wich says the following:
Does spamdyke run its filters in any particular order?
Yes. spamdyke evaluates its filters in
and local IP's and also created
a button to check the reverse data. As far as i know, thats a way the
big providers do it, i mean tagging
mails manually as spam or ham.
Am i right?
Greetz,
David
___
spamdyke-users mailing list
spamdyke-users
and local IP's and also created
a button to check the reverse data. As far as i know, thats a way the
big providers do it, i mean tagging
mails manually as spam or ham.
Am i right?
Greetz,
David
___
spamdyke-users mailing list
spamdyke-users
Clippinger
David Stiller wrote:
Hi all,
i've written a Spamdyke GUI for Plesk for my customers, so that they all
have their own responsibility,
if they want to use greylisting and are able to maintain their black-and
whitelists. It's nice, as they all can see, what's
really happening
Yes, me also. Looks like this is one of the reasons, why Linux-tools
are mostly
developped for specific systems, when making RPM's. So Spamdyke 4.0.5 seems
to be good for SuSE's, and maybe not on others? Just quick shot from me^^ :)
Arne Metzger schrieb:
Hi,
on my vm running Suse10.0 i can't
of the global spamdyke setup. Looks
quite logical for me
and should be easy to be maintained.
-
David
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
/customer_blacklist_sender
I hope this helps! ;)
David
Linto Paul schrieb:
Greetings,
Could please let me know if there is a way to whitelist a domain on
the IP_IN_RDNS_KEYWORDS on a per domain basis.
Say we get user complaining about a domain called example.com
http://example.com, and they say, I am
As an answer to this:
Is it possible to just put a whitelist for example.com
http://example.com and deny all others matching this keyword.
Sure. I would just whitelist 66.49.15.190 and blacklist .nuvox.net
http://nuvox.net. Don't know wich one catches
first. I would try.
Regards,
David
http
Hi Rafael,
Rafael Andrade schrieb:
How i can block emails, searching some Regex on ur body?
Example: Searching Viagra, or Mercadolibre, Cialis, Xxx, Sex, whatever
some words on email send or receive.
It's not Spamdyke's Job to scan mails for contents. Spamdyke doesnt' see
any word of the
[EMAIL PROTECTED] schrieb:
Hi
David
I had use [EMAIL PROTECTED] for example of mail, is not real mail.
Yes, thats why i didn't use a dig on that and said i guess.
Peter
I check same too, 53-255-112-92.pool.ukrtel.net don't resolve to A
entry. But I suppose rnds
Yes, probably the log-file-format doesn't fit. That spamdyke-stats.pl parses
the default-format of qmail. Plesk writes another. The qmail-SMTP-Logs
normally
begin with:
@400048ee184815c9cc04
and Plesk write human-readables:
Nov 3 16:08:07 plesk-mail [...]
Peter schrieb:
Hi folks!
Does
I think you had another. ;-) If you want, i can look if i can find my
old one.
Peter schrieb:
Am Montag, den 03.11.2008, 16:06 +0100 schrieb David Stiller:
Yes, probably the log-file-format doesn't fit. That spamdyke-stats.pl parses
the default-format of qmail. Plesk writes another
DENIED_RBL_MATCH: 372
DENIED_RDNS_RESOLVE: 384
ALLOWED: 452
DENIED_GRAYLISTED: 236
TIMEOUT: 4
DENIED_OTHER: 12
DENIED_SENDER_NO_MX: 4
Or for all with paging:
./spamdyke-domrep-cli -a | less
This is the analysis-routine used for my plesk-module.
So probably will work for you.
Greetz,
David
no comment :-D
David Stiller schrieb:
Ok, if you can use PHP-CLI, try the attached scripts. Move arg_parse into
/usr/lib/php-cli/ or change the path in the main-script. Then you can
use it
like this:
./spamdyke-domrep-cli -d example.com
example.com
Looks like a temporarily problem, the RDNS can be found now:
# host -r 65.55.111.96
96.111.55.65.in-addr.arpa domain name pointer
blu0-omc2-s21.blu0.hotmail.com.
David Stiller schrieb:
I think spamdyke doesn't find the origin_ip listed in the mx's of
hotmail.com:
# dig mx hotmail.com
nightduke schrieb:
Hi i wish to know if it's possible to add a domain at graylisting
directory, if it's added every email from that domain will be
automactly added and people start receiving emails from that domain.
I hope people can understand what i'm saying.
Nightduke
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
David Stiller
Technischer Support
Blackbit Neue Medien GmbH
Ernst-Ruhstrat-Straße 6 - D-37079 Göttingen
tel.: +49 [551] 50675-60 - fax.: +49 [551] 50675-20
email: [EMAIL PROTECTED] - hotline: [EMAIL PROTECTED
to allow for this?
Thanks.
--
Erald Troja
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
David Stiller
Technischer Support
Blackbit Neue Medien GmbH
Ernst
For me it looks loka a local delivery and you probably authenticated
- so Spamdyke
doesn't need to block mails from you, to you. SCP should show another
field, like
Auth, as my surface does.
Am 24.03.2009 um 09:37 schrieb Ulrich C. Manns:
As you can see in attached picture. Sometimes i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ulrich C. Manns schrieb:
@Sam Clippinger
Hi Sam,
my whishes:
1. A new parameter to reject emails if sender=recipient (because
we?re hosting many domains an Eduard method won?t work for us)
Hi Ulrich,
isn't it a quite usual method
.
*Von: *David Stiller david.stil...@blackbit.de
*Antworten an: *spamdyke users spamdyke-users@spamdyke.org
*Datum: *Thu, 7 May 2009 11:03:49 +0200
*An: *spamdyke users spamdyke-users@spamdyke.org
*Betreff: *Re: [spamdyke
Hi Eric,
check if the privileges of the files in /var/qmail/bin/ are set correctly.
Plesk uses qmail-queue as the qmail-wrapper, wich needs the sticky-bit:
-r-xr-xr-x 1 root qmail 24704 Aug 24 2008 qmail-lspawn
[...]
-r-s--x--x 1 drwebqmail 152436 Sep 17 2008 qmail-queue
-r-s--x--x
-boun...@spamdyke.org
[mailto:spamdyke-users-boun...@spamdyke.org] On Behalf Of David Stiller
Sent: Thursday, June 04, 2009 7:23 PM
To: spamdyke users
Subject: Re: [spamdyke-users] Qmail writes with wrong user to the maildir
Hi Eric,
check if the privileges of the files in /var/qmail/bin
to run /usr/local/psa/admin/sbin/mchk?
The thing is, that’s what (in my opinion) caused the problem in the first
place (besides emptying a few configuration files and rewriting other config
files with incorrect data :) ).
-Original Message-
From: David Stiller [mailto:david.stil
Just a suggestion, but I'm thinking that you could optimise this a bit.
dial will already match dialin, dialpool and dialup, so there's
no need to include those three, just dial. Same with a few of the others.
Cheers,
Dave
Sam Clippinger wrote:
Sure. Please keep in mind this list works for me,
Christoph Kuhle (Expat Email Ltd) wrote:
I also think that a lot of emails are getting through because they come
from a secondary mail server and we have been told that Spammers often
choose the lowest priority MX record and send to that. This then passes
the checks which is frustrating
Pretty sure these options are what you're looking for:
http://www.spamdyke.org/documentation/README.html#SMTP_ERROR
Cheers,
Dave
Marcin Orlowski wrote:
Hi,
I'd love to see a way to configure messages spamdyke emits, i.e.:
421 Refused. Your reverse DNS entry does not resolve. See: URL
Hi Eduard,
would you please explain me, why you add .com and .net to the
/etc/spamdyke/blacklist_keywords file? They are valid
tld's to send mails from, or do i just miss anything?
Eduard Svarc schrieb:
Hello,
I see you have two things out. 1st you using RBLS, that could give you
a lot
@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
David Stiller
Technischer Support
Neues von Blackbit: aktuelle Projekte und Wissenswertes aus
unserer Werbeagentur unter http://www.blackbit.de/tagebuch
Blackbit neue Medien GmbH
Ernst-Ruhstrat-Straße 6 - D-37079 Göttingen
Tel
On 21/05/2010 16:15, b.hinzer wrote:
Strange thing here now. I blacklisted my complete domain by setting
wildcard in whitelist_senders:
@web-vision.de
But still a spam email with a faked email address came through.
Is it possible that it just skipped spamdykes tests by using a TLS
Can you post the origin-rdns of that connection please?
On 01.06.2010 12:20, David Stiller wrote:
Blacklist all, Whitelist \b[a-z0-9._%+...@[a-z0-9.-]+\.[a-z]{2,4}\b
:-D Don't use this! Was a joke ;-)
Am 01.06.2010 um 11:20 schrieb Arvydas:
Hello,
Jun 1 12:16:41 sun spamdyke[10110
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Sehr geehrte Kundin! Sehr geehrter Kunde!
Ich bin vom 05. Juli 2010 bis 16. Juli 2010 einschließlich im Urlaub.
Bitte senden Sie Fehlermeldungen und Störungen an hi...@blackbit.de, dort
wird Ihre Anfrage einem Mitarbeiter zugewiesen.
Mit freundlichen Grüßen,
David Stiller
Technischer Support
Hi all!
With Spamdyke v4.1 i think the three exclamation marks dont work anymore:
Jul 21 11:13:32 plesk-mail spamdyke[18097]: ERROR: Bad or unparsable value for
option reject-unresolvable-rdns: !!!
Jul 21 11:13:32 plesk-mail spamdyke[18097]: ERROR: Bad or unparsable value for
option
I found a workaround how my server does not cause segmentation faults. I
get them
when i comment out the config-dir option wich i normally use. I
commented it out,
because i had problems with RBL false positives.
Is it the same in your case Ken?
Am 21.10.2010 21:36, schrieb Sam Clippinger:
Ok, so it's another reason. I've let spamdyke run overnight and i now i have 97
Segfaults again.
I think it's more than my config-dir, thats just a workarounf for the
mail-sending problem.
So sending mail works, but stillt some spammers get disconnected. :-D Sam just
send me your
IP to access
It's more than i thought:
[r...@plesk-mail 11:12:33:~]
# grep segf /var/log/messages | grep Oct 25 | wc -l
6768
# dmesg | wc -l
2655
I think it got so high as there's someone sending a newsletter.
Am 25.10.2010 um 09:38 schrieb David Stiller:
Ok, so it's another reason. I've let spamdyke
IN A 75.125.118.227
Spamdyke asked it for entries and blocked ALL incoming mails, instead of
letting the
mails through to the next filters, as the list told no domain name.
So double-check your mail-log if you use any RHSBL's or RBL's.
Regards,
David
On 12/08/2011 23:55, Markus weber wrote:
I'm still quite new to spandyke and have a problem I just cannot find
the reason for.
All dns-blacklist-file or dns-blacklist-entry are completely ignored by
my spamdyke.
*snip*
The options are rdns-blacklist-entry and rdns-blacklist-file - you're
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
--
David Milholen
Project Engineer
P:501-318-1300
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http
of blacklist entries shouldn't be a problem.
Because each entry is a separate file, you could write a very simple
script to automatically delete any files older than X days. That
would make them automatically expire.
-- Sam Clippinger
On Apr 9, 2013, at 7:08 AM, David Milholen wrote:
Very Clever
Hello,
Any progress with this issue?
regards,
David Davidov
On 06/18/2013 06:47 PM, David Davidov wrote:
Hi Sam,
I am a colleague of Theodor. This is a simple way to trigger the problem:
dave~$ telnet mx.example.com 25
Connected to mx.example.com
Escape character is '^]'.
220
with each additional message, the list of addresses grows and
duplicate messages are printed.
I'll incorporate the fix in the next version, hopefully coming soon.
-- Sam Clippinger
Thanks a lot for your efforts!
Waiting for the next version.
best regards,
--
David Davidov | System Administrator
SA logs show nothing for scanning
here is what I have
qtp-whatami v0.3.8 Fri Jun 13 21:45:41 CDT 2014
REAL_DIST=CentOS
DISTRO=CentOS
OSVER=5.10
QTARCH=i686
QTKERN=2.6.18-371.3.1.el5
BUILD_DIST=cnt50
BUILD_DIR=/usr/src/redhat
On 6/3/2014 9:10 PM, Eric Shubert wrote:
I haven't seen this sort of
!
---
David Sanchez Martin
Administrador de Sistemas
dsanc...@e2000.es
GPG Key ID: 0x37E7AC1F
E2000 Nuevas Tecnologías
Tel : +34 902 830500
smime.p7s
Description: S/MIME cryptographic signature
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http
the graylisting.
All this is just for ease transition.
Thank you again!
---
David Sanchez Martin
Administrador de Sistemas
dsanc...@e2000.es
GPG Key ID: 0x37E7AC1F
E2000 Nuevas Tecnologías
Tel : +34 902 830500
smime.p7s
Description: S/MIME cryptographic signature
Hi Michael,
So Set it to 1 minute. Certainly your users can
wait 1 minute...
I think greylisting may loose some of its effectiveness this way...
Set it to 10 minutes, don't tell them it's there, and they
likely won't even
notice.
I know, but what I'm trying to do is,
David,
That sounds like a neat idea, but I don't think it'd work. If
you simply
allow the session to complete and create a greylist entry for
everything, you will have effectively whitelisted every incoming
message, including the bad ones. Greylisting works because
some spammers
That will populate the database for all email. Including
spammers. Any
spammers who send messages during the period in which the database is
being populated will get a free pass, even after greylisting is
activated. Perhaps you can live with that.
That will populate the database with
case, but that wasn't what I was trying
to solve (as you said, this is something I should consider if it's
acceptable
or not, but this is another matter, graylisting is what it is, you can take
it or leave it as is).
Best regards :-)
---
David Sanchez Martin
Administrador de Sistemas
dsanc...@e2000
It seems to be a client (I am using Outlook express) issue changing the port
to 465 and removing unlinit somewhat solved the issue.
But in I have
grep spamdyke /var/log/mail.info
Sep 22 07:46:17 server spamdyke[4311]: ALLOWED from: d...@elektronik.dk to:
d...@vip.cybercity.dk origin_ip:
I only get ALLOWED
I have
server:/var/log# cat /etc/spamdyke.conf
access-file=/etc/spamdyke-relay
smtp-auth-level=always
smtp-auth-command=/usr/bin/checkpassword /bin/true
relay-level=normal
server:/etc# cat spamdyke-relay
192.168.1.:deny
127.0.0.1:allow
:deny
It should deny everything unless
feature? Is
spamdyke logging any errors?
-- Sam Clippinger
David Bo Jensen wrote:
It seems to be a client (I am using Outlook express) issue changing the
port
to 465 and removing unlinit somewhat solved the issue.
But in I have
grep spamdyke /var/log/mail.info
Sep 22 07:46:17 server
, but you're not giving enough information to work
with.
Have you tried running spamdyke's config-test feature to look for
problems?
-- Sam Clippinger
David Bo Jensen wrote:
I solved the problem with
server:/# cat /etc/spamdyke-smtps.conf
log-level=verbose
tls-level=smtps
tls-certificate-file
. When an authenticated connection is
allowed, you will see ALLOWED in the syslog and the auth: field will
contain the username.
I should probably reword the documentation to make this more clear.
-- Sam Clippinger
David Bo Jensen wrote:
I only get ALLOWED
I have
server:/var/log# cat /etc
messages. When an authenticated connection is
allowed, you will see ALLOWED in the syslog and the auth: field will
contain the username.
I should probably reword the documentation to make this more clear.
-- Sam Clippinger
David Bo Jensen wrote:
I only get ALLOWED
I have
server:/var/log# cat
What is
ls -la /home/vpopmail/bin/vchkpw
and what is the user for the tcpserver?
What do you mean with
preferring pop-before-smtp over smtp-auth ?
You have no configuration file for spamdyke, and I have learned that
access-file and local-domains-file must be present.
these two option are not
* David Bo Jensen d...@elektronik.dk [090926 08:12]:
What is
ls -la /home/vpopmail/bin/vchkpw
-rwx--x--x 1 vpopmail vchkpw 190656 Nov 24 2007
/home/vpopmail/bin/vchkpw
and what is the user for the tcpserver?
qmaild
I don't know /home/vpopmail/bin/vchkpw. But it is possible that you
the certificate file.
Please see my new thread
-- Sam Clippinger
David Bo Jensen wrote:
Running the config test gave me some ERRORS. I added access-file and
local-domains-file to my config file
in order to remove some of them. Here is my result but remember I was root.
:/etc# /usr
`
To this:
-g `id -g qmaild`
You should then be able to change the file permissions back to their
original settings.
NO it is not possible to change the permissions back to their original settings
-- Sam Clippinger
David Bo Jensen wrote:
In my /etc/init.d/qmail I have
...
rblsmtpd2=/usr
Sam Clippinger, you are right, but I think some clarification is needed.
It would be wonderfull if `id -g name` gave the id of the group with the name
'name',
but that is not how id works. name is a user and 'id -g' will always give the
id of
the principal group associated with name. Usually
I have the famous problem with a newly installed debian lenny AMD64
unable to find protocol number with getprotobyname()
Yes I know it has something (I have read) to do with UDP.
grep UDP /etc/protocols
udp17UDP#user datagram protocol
However I can successfully, send and
The code in spamdyke is very simple it just call
getprotobyname(udp), and if the returned pointer is null it logs the error
message.
My guess is that getprotobyname for some reason hasn't been able to read the
/etc/protocols.
I have made a small testprogram using getprotobyname and it works
I have posted this mail before but somehow it didn't end on the top of the mailling
list, so I try again.
I have the famous problem with a newly installed debian lenny AMD64
unable to find protocol number with getprotobyname()
Yes I know it has something (I have read) to do with UDP.
grep
Problem solved.
ulimit in my qmail script was simply too low
___
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
99 matches
Mail list logo
