We sometimes have problems sending email to servers using Barracuda boxes. Here is an example:
message text rejected by server-using-barracuda:
554 Service unavailable; Client host [our-server] blocked using Barracuda Reputation; http://bbl.barracudacentral.com/q.cgi?ip=84.226.24.238
The IP 84.226.24.238 is the IP the customer has used to connect to our server (authenticated with SMTP Auth) and NOT the IP of our server.
The client IP 84.226.24.238 is actually listed in BRBL, but our IP is NOT listed.
So it seems that the Barracuda boxes can be configured to reject emails based on blacklist entries of any IP in the received headers and not just the last one. This does not make sense to me as most client IPs are dynamic ones and listed in some blacklist.
To circumvent this problem I have been thinking about hiding the received headers, in CGP:
Settings - Mail - SMTP - Sending - Hide Received Fields
How are you dealing with this problem? Have you enabled "Hide Received Fields"? Is there any disadvantage of doing this?
Thanks
Daniel
#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGat...@mail.stalker.com>.
To unsubscribe, E-mail to: <CGateP...@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com>
Send administrative queries to <CGatePro...@mail.stalker.com>
Lyle Giese
LCR Computer Services, Inc.
Barracuda did not notify us.
The error message our customers got did not reveal much details.
There's no spam sample or detailed info, just a general page telling you the
spam problems this world has.
They offer a temporary whitelisting, which we used and after a few days the
ip was again listed.
They offer a durable whitelisting but they want money for this - ha.
We wrote to Barracuda and after a few days they wrote, that they have no
idea why our ip was listed at all. Our ip was taken off the list and the
history deleted.
We wrote to the Barracuda customer, told them to change the settings on the
box or look for another antispam solution.
The customer wrote us that we have a spam problem and should use the
whitelisting.
Nobody paied us, maybe we should open a payable whitlist...
Regards
Ralf
-----Ursprüngliche Nachricht-----
Von: CommuniGate Pro Discussions [mailto:CGat...@mail.stalker.com] Im
Auftrag von Lyle Giese
Gesendet: Sonntag, 6. Dezember 2009 20:35
An: CommuniGate Pro Discussions
Betreff: Re: Problems with Barracuda Reputation
> Hi,
>
> We sometimes have problems sending email to servers using Barracuda
> boxes. Here is an example:
>
> message text rejected by server-using-barracuda: 554 Service
> unavailable; Client host [our-server] blocked using Barracuda
> Reputation; http://bbl.barracudacentral.com/q.cgi?ip=84.226.24.238
>
> The IP 84.226.24.238 is the IP the customer has used to connect to
> our server (authenticated with SMTP Auth) and NOT the IP of our
> server.
Your clients should connect to your server directly, bypassing Barracuda
or other external filters. You need to force all your clients to
authenticate when sending, then if there's a spammer among your users
you'll know who it is and will be able to take administrative/legal
measures; there can be zombied spam bots but it's unlikely they'll
authenticate.
It's also useless to scan outgoing mail for spam since spam filters
catch spam being in circulation and if it's a newly composed spam it's
very low chance it will be detected.
> The client IP 84.226.24.238 is actually listed in BRBL, but our IP is
> NOT listed.
>
> So it seems that the Barracuda boxes can be configured to reject
> emails based on blacklist entries of any IP in the received headers
> and not just the last one. This does not make sense to me as most
> client IPs are dynamic ones and listed in some blacklist.
There are different blacklists around: some include dynamic IPs and can
be used only for checking the topmost address (e.g. pbl.spamhaus.org),
others include only real spamhosts and can be used for deep headers
scanning (xbl.spamhaus.org)
> To circumvent this problem I have been thinking about hiding the
> received headers, in CGP:
>
> Settings - Mail - SMTP - Sending - Hide Received Fields
>
> How are you dealing with this problem? Have you enabled "Hide
> Received Fields"? Is there any disadvantage of doing this?
The disadvantage of using it is that it will be difficult to investigate
who was the sender of a particular message in case of an accident.
--
Sincerely,
Roman
=======================================================================
When answering to letters sent to you by the tech.support staff, make
sure the original message you have received is included into your reply.
That does seem to be a little strange because of what you said....quite often a dynamic IP address is on some blacklist for something.
--
Jeff Wark
TBayTel Internet
807-625-3041
So their paid whitelist is just a scam to make more money from non customers.
Jon
--------------------------------------------------
The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, an associate or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.
Thank you.
GVC Direct, Inc.