On 09/28/2011 10:35 AM, David wrote:
On 09/28/2011 09:28 AM, Eric Shubert wrote:
On 09/28/2011 07:03 AM, David wrote:
Hello All,
I havent posted in a while but ran into an issue with this log entry
DENIED_OTHER from: [email protected] to: [email protected]
origin_ip: 209.85.160.178 origin_rdns: mail-gy0-f178.google.com auth:
(unknown)
I need to allow this sender through but since spamdyke did not tell
specifics on why its blocked I am
not sure how to whitelist him..
Ideas..
Thanks
Dave
---------------------------------------------------------------------------------
When spamdyke rejects with DENIED_OTHER, it means that some
non-spamdyke filter kicked in, and spamdyke is simply reporting the
overall action taken. You should see another message preceding the
spamdyke message which explains the rejection reason, such as
spf-reject or badmailto. I'm not positive, but I think that
whitelisting via spamdyke's whitelists would be ineffective for these
filters.
Looking through my log just now, I noticed that there are a few
DENIED_OTHER messages that have no other message associated with them.
:( If this is the case with your rejection, please see if you can get
a copy of the bounce to see if there's any indication in the bounce of
why the rejection.
There should be no rejections w/out a corresponding message in the
log. SPF rejects used to be this way, and I don't recall which version
fixed that case. Once you've identified the cause of rejection,
hopefully we can get the code patches to log a message for that
situation.
I'm sure you realize that without knowing the cause for rejection,
it's pretty much impossible to tell how to whitelist it. ;)
Thanks David.
Yes,
Looked a little closer and saw SPF-Reject Looks like the sender may be
using some form of cloud to route mail.
Do I need to add a special spf for this sender or what?
Thanks
Dave
---------------------------------------------------------------------------------
Looks as though durand simply hasn't coded their spf record appropriately:
shubes@edwin:~$ dig durandassociates.com txt
; <<>> DiG 9.7.0-P1 <<>> durandassociates.com txt
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21735
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;durandassociates.com. IN TXT
;; ANSWER SECTION:
durandassociates.com. 7200 IN TXT "v=spf1 mx a ip4:67.23.247.145
-all"
;; Query time: 103 msec
;; SERVER: 192.168.70.2#53(192.168.70.2)
;; WHEN: Wed Sep 28 11:03:27 2011
;; MSG SIZE rcvd: 85
The sending IP isn't defined as one that's allowed to send for
durandassociates.com. Your QMT is doing what it's supposed to do.
durandassociates.com needs to fix their spf (DNS TXT) record. I'm
guessing they probably just switched over to google mail and neglected
to modify their spf record.
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
