I hope someone can suggest to me why this particular
scenario is happening.
We have a client with a static IP address to the outside
world. Everyone in the facility (6) thus sends with this
outside IP
address. Someone apparently was naughty and ended up with
their IP
address listed in CBL which then gets into Spamhaus etc.
OK, we
understand that. have to find the culprit and fix it then
ask CBL to
de-list them.
BUT. One of the workstations is having more nightmares than
others. He can not even send email to a colleague without
it being
trapped within Surgemail. He can not send email to specific
target
outside addresses without Surgemail dropping it because of
the black list.
However, another person in the office can send the first
person email
without being blocked. They can also send to the very same
outside
email addresses without being blocked. What's up with this?
I don't
understand what is happening and my customer, naturally,
wants an
explanation from me as to why HE can't send email but his
office mate can.
Can anyone suggest why this would be happening? The
customer is
pretty unhappy right now and while he understands the black
list he
isn't accepting that as the explanation as long as this
disparity
between users is apparent. Black list should be Black list
for all
the sending messages. Surgemail certainly is not looking
specifically at individual senders and HAS to come up with
the same
resolution (ie. black listed) with each of the senders. I
have
looked at the mail log and I can see his transmissions are
being
dropped because of the black list but his office mate are
allowed to
pass. I think the black list drop is because I have it set
this way
in the local filter. Line 104 to be specific. I drop
anything
listed in Spamhaus which uses CBL. I suppose I could relax
this rule
until we figure out why this is being applied unequally.
Second question, Is there a way to bounce only local
messages when
the sending IP is found in Spamhaus?
Orin Wells
Support awasco.com
253-630-5296
|