This one time, at band camp, Mark Farver wrote:
> Scott Ryan wrote:
> 
> >This one time, at band camp, Scott Ryan wrote:
> > 
> >
> >>Can someone explain what this error message means:
> >>
> >>@4000000043788c3a0b741b24 delivery 691: deferral: 
> >>196.15.168.3_failed_after_I_sent_the_message./Remote_host_said:_451_Receiving_compressed_data_failed:_invalid_distance_too_far_back_#(4.3.0)/
> >>
> >>Both the relay machine and the receiving machine are qmail-ldap-20050401a
> >>   
> >>
> >
> >Just to add some more on this: 
> >My setup is as as follows - Machine A can send mail to machine B without 
> >any problems, however when machine b tries to send to machine A, I get the 
> >msg above and the following message sometimes:
> >
> >@400000004378934e2d6b867c qmail-smtpd 21775: compressed data read failed: 
> >invalid literal/lengths set
> >
> >Both machines, like I said are running qmail-ldap20050401a and they were 
> >compiled with zlib-devel-1.2.2 and both have zlib-1.2.2 on them.
> >
> >Any ideas/pointers would be extremely appreciated.
> >
> > 
> >
> Same binaries or were they compiled independantly on each machine?  Just 
> a guess but it sounds like some offset issue/ 64 bit vs 32 or other 
> weirdness.

Intersting. I have been using a 64 bit buildhost with a linux32 chroot 
environment to build my qmail-ldap rpms. I will look into it and see if I 
havent been doing anything weird. 
I also noted that the errors are in the zlib code and not qmail-ldap. So it no 
longer makes it a a problem with qmail-ldap.

Thanks for you help/advice.

> 
> Mark Farver
> 
> 

-- 
slr,

ISP Systems Specialist
Telkom Internet
#qmail-ldap @ irc.freenode.net

This message has been made from 100% recycled bits.

----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT/MU/E d? s+:+ a- C++++>+++++ USL++++$ P++++ !E(---)W+@ !N
o?(--) K? !w(---) O- M+ V PS+@ PE Y-- PGP++>+++ !t(---) !5 !X
R-- !tv b(++) DI++ !D(----) G+++>++++ e++>* h----(*) r+++ y++++
-----END GEEK CODE BLOCK------

Attachment: pgpmT2DOJGJPd.pgp
Description: PGP signature

Reply via email to