Re: [exim] blocked using Barracuda Reputation

Page principale
Supprimer ce message
Répondre à ce message
Auteur: W B Hacker
Date:  
À: exim users
Sujet: Re: [exim] blocked using Barracuda Reputation
David Saez Padros wrote:
> Hi
>
> you can hide your customer ip address using this:
>
> received_header_text = Received: \ ${if and
> {{def:sender_rcvhost}{!def:authenticated_id}}\ {from $sender_rcvhost\n\t}\ {\
> ${if def:sender_ident {from ${quote_local_part:$sender_ident} }{\ ${if
> def:authenticated_id {from ${quote_local_part:$authenticated_id} }}\ }}\ ${if
> def:sender_helo_name {(helo=$sender_helo_name)\n\t}}\ }\ }\ by
> $primary_hostname \ ${if def:received_protocol {with $received_protocol}} \
> ${if def:tls_cipher {($tls_cipher)\n\t}}\ (Exim $version_number)\n\t\ ${if
> def:sender_address \ {(envelope-from <$sender_address>)\n\t}}\ id
> $message_exim_id\ ${if def:received_for {\n\tfor $received_for}}
>
>
> this is the fast way to solve this problem and be sure that it will never
> happen again with those f*ck*ng Barracuda appliances
>
>> Hi one of customers who sends email out via our server using asmtp is
>> having his email blocked by a barracuda system. But they are blocking it
>> based on his address rather than our smtp server which is not black listed.
>>
>>
>> 2010-10-22 09:58:17 1P9DR3-000I43-DY ** mhussain@???
>> F=<office@???> R=dnslookup T=remote_smtp: SMTP error from remote
>> mail server after end of data: host smtpmail.ead.ae [195.229.40.150]: 554
>> Service unavailable; Client host [ns0.1stkmh.co.uk] blocked using Barracuda
>> Reputation;
>> http://www.barracudanetworks.com/reputation/?r=1&ip=86.170.248.224
>> 2010-10-22 09:58:17 1P9DR3-000I43-DY Completed
>>
>> Must be a configuration error some where just not sure if it is the clients
>> end our mail server or the Barracuda system
>>
>>
>> ta Terry
>>
>


??

The 'fast' as in low-resource and highly predictable way is simpler and requires
less 'logic':

In the remote_smtp (or equivalent) transport, add/include:

headers_remove = Received

CAVEATS:

- Violates spirit if not letter of RFC.
(But not as badly as filtering on the wrong headers!)

- Wise to have an *unaltered* copy archived for troubleshooting. We store two -
one by originator, the other by destination - for quicker findingness.

;-)

HTH,

Bill