mahesh.b...@modelytics.com wrote:
Hi Eric,
to add to what dani query i have had problems in taming Spamdyke.
spam dyke and just started blocking good domains too.
The only good domains that I've seen spamdyke block are ones who don't
have rDNS configured correctly. In these cases, I
I changed 2 of my email address passwords today via qmailadmin and now both
of those accounts get duplicate emails.
Any ideas on how to stop this?
In my .qmail file
|/var/qmail/bin/preline /usr/bin/maildrop -A 'Content-Filter:
maildrop-toaster' /etc/mail/mailfilter
Ok, I deleted the second line and it fixed the problem. Did it insert this
line using the qmailadmin web app?
- Original Message -
From: Ronnie Tartar rtar...@host2max.com
To: qmailtoaster-list@qmailtoaster.com
Sent: Wednesday, August 05, 2009 1:54 PM
Subject: [qmailtoaster]
You might want to test a bit. Which package versions?
Ronnie Tartar wrote:
Ok, I deleted the second line and it fixed the problem. Did it insert
this line using the qmailadmin web app?
- Original Message - From: Ronnie Tartar rtar...@host2max.com
To:
Ok, let me see if I can shed some light if you have not figured this out yet.
Check your /etc/tcp.smtp file. In there are the rules on who gets scanned.
Mine looks like this:
127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1
Kent Busbee wrote:
Ok, let me see if I can shed some light if you have not figured this out yet.
Check your /etc/tcp.smtp file. In there are the rules on who gets scanned.
Mine looks like this:
127.:allow,RELAYCLIENT=,DKSIGN=/var/qmail/control/domainkeys/%/private,RBLSMTPD=,NOP0FCHECK=1
Dear all
This is the message option
Return-Path: d...@stanley.co.id
Delivered-To: d...@stanley.co.id
Received: (qmail 31266 invoked by uid 89); 5 Aug 2009 12:14:37 -
Received: from unknown (HELO mail.aol.com) (91.149.180.129)
by mailsvr.stanley.co.id with SMTP; 5 Aug 2009
In some systems where we are using old setup, we were facing the same
issue. Ronnie, hope if any modification done in the qmailadmin for
the same user will again bring the problem back. Plz check this. If
the problem does not occur again, its good. If the same thing happens,
use the following
