On Fri, 16 Dec 2011 12:20:18 +0100
M. Fioretti articulated:
> I am sure that if a barracuda salesperson realized how many of their
> customers do braindead settings because they don't provide clear
> enough warnings of how many documented problems those settings cause,
> he'd immediately call the
On Fri, Dec 16, 2011 10:45:04 AM +0100, Reindl Harald wrote:
> again: the only thing to send them is the question why in the world
> they are not updating their appliance and even if this option exists
> a barracuda sales is not respsonsible for customers which doing
> braindead settings
I am sur
Am 16.12.2011 07:58, schrieb M. Fioretti:
> to the OP, I suggest to contact with alternate email address the
> admins and users of the Barracuda instances that are blocking your
> email (with a Barracuda sales rep in CC!) to let them know that dumb
> default settings and unclear documentation of
On Thu, 15 Dec 2011 23:11:22 +0100, Robert Schetterer wrote:
sorry, for sure your postmaster ( if you arent it yourself) from the
isp smtp relayhost has to do it for you
if not possible, call the recipient fixing his broken baracuda setup
or setup spf on sender domain with relayhost ip, and h
On Thu, Dec 15, 2011 16:34:08 PM -0600, /dev/rob0 wrote:
> Barracuda "Deep header parsing" is a disaster. A large percentage of
> legitimate mail from end users on dynamic IP addresses (most people
> are in that group) will be blocked.
Right. This is a well known fact. 2 years ago I publicly re
On Thursday 15 December 2011 15:50:42 Duane Hill wrote:
> On Thursday, December 15, 2011 at 21:41:51 UTC, bjloc...@lockie.ca
> confabulated:
> > I run my own domain off a dynamic IP but all my postfix uses
> > relayhost set to smtp.myisp. This works 99.9% of the time but I
> > have encountered two
Am 15.12.2011 22:54, schrieb Robert Schetterer:
> Am 15.12.2011 22:41, schrieb James:
>> I run my own domain off a dynamic IP but all my postfix uses relayhost set
>> to smtp.myisp.
>> This works 99.9% of the time but I have encountered two recipients who use
>> Barracuda's that block email from
Am 15.12.2011 22:54, schrieb Robert Schetterer:
> you can try to delete your dny ip from the header
>
> read .i.e for ideas
>
> http://blog.tenak.net/2011/04/2011-04-dont-send-client-ip-postfix.html
you can not because you are not in the position to change
any "received from" of the target-se
Am 15.12.2011 22:41, schrieb James:
> I run my own domain off a dynamic IP but all my postfix uses relayhost set to
> smtp.myisp.
> This works 99.9% of the time but I have encountered two recipients who use
> Barracuda's that block email from my domain.
>
> The bounce includes "(reason: 554 Serv
On Thu, Dec 15, 2011 at 04:41:51PM -0500, James wrote:
> I run my own domain off a dynamic IP but all my postfix uses relayhost set to
> smtp.myisp.
> This works 99.9% of the time but I have encountered two recipients who use
> Barracuda's that block email from my domain.
>
> The bounce includes
On Thursday, December 15, 2011 at 21:41:51 UTC, bjloc...@lockie.ca confabulated:
> I run my own domain off a dynamic IP but all my postfix uses relayhost set to
> smtp.myisp.
> This works 99.9% of the time but I have encountered two recipients
> who use Barracuda's that block email from my domain
I run my own domain off a dynamic IP but all my postfix uses relayhost set to
smtp.myisp.
This works 99.9% of the time but I have encountered two recipients who use
Barracuda's that block email from my domain.
The bounce includes "(reason: 554 Service unavailable; Client host [smtp.myisp]
block
12 matches
Mail list logo
