On Tue, 13 Jan 2015, Moritz Both wrote: > Don, > > thank you for the response. I hope this bug report does not mutate > to a support case embarrasingly ;) Anyway I'm confused.... your > source code is diffrent from mine... is there something newer than > 0.3.2-1 in stable? Is your code from 0.3.2-1b1 from sid? > > moritz@eroski:~/src$ apt-get source spamass-milter > [...] > Holen: 1 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1 > (dsc) [1.882 B] > Holen: 2 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1 > (tar) [155 kB] > Holen: 3 http://ftp.de.debian.org/debian/ wheezy/main spamass-milter 0.3.2-1 > (diff) [15,1 kB] > Es wurden 172 kB in 0 s geholt (526 kB/s). > dpkg-source: Information: spamass-milter wird nach spamass-milter-0.3.2 > extrahiert > dpkg-source: Information: spamass-milter_0.3.2.orig.tar.gz wird entpackt > dpkg-source: Information: spamass-milter_0.3.2-1.debian.tar.gz wird entpackt > dpkg-source: Information: ignore_by_smtp_auth wird angewandt > dpkg-source: Information: fix_spacing_in_received_header wird angewandt > dpkg-source: Information: fix_header_char_cast wird angewandt > dpkg-source: Information: add_ipv6_support wird angewandt > dpkg-source: Information: auth_in_received wird angewandt > > Now, spamass-milter.cpp says > > string rec_header; > rec_header=(string)"Received: from "+macro_s+" > ("+macro__+")\r\n\t"; > if (strlen(macro_auth_type)!=0) { > rec_header+=(string)"(authenticated"; > if (strlen(macro_auth_ssf)!=0) { > rec_header+=(string)" bits="+macro_auth_ssf; > } > rec_header+=(string)")\r\n\t"; > } > rec_header+=(string)"by "+macro_j+"("+macro_v+"/"+macro_Z+") > with "+ > macro_r+" id "+macro_i+"\r\n\t"+ > macro_b+"\r\n\t"+ > "(envelope-from "+assassin->from()+"\r\n"; > > debug(D_SPAMC, "Received header for spamc: %s", > rec_header.c_str()); > assassin->output(rec_header); > > It is obvious that this code does not add the ; or ). To me it is not > obvious why my dates are messed up. I added the -d ALL switch and wait > for the next occurance in the next several hours.
Hrm. Actually, I see the problem now. For some crazy reason, the patches (probably when I was updating to 3.3.2) got screwed up, and I didn't catch this. I'll fix them now. -- Don Armstrong http://www.donarmstrong.com Live and learn or die and teach by example -- a softer world #625 http://www.asofterworld.com/index.php?id=625 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
