Hi Sam, Yes, I had one customer who had 4 pdf-attachments. 2 corrupted, 2 where ok. On the next try the other 2 attachments where corrupted, the first corrupted where ok. So at the end we had 4 visible attachments.
Andreas > I'm still working on this bug -- several people have sent me full logs > and test messages; those are helping a lot. I haven't succeeded in > duplicating corrupted attachments yet though. > > I did find one bug that might be causing this issue. At this point, I > don't think it has anything to do with TLS (although TLS may make it > easier to trigger the bug). What I've found occurs when a client sends > its data in a large burst and disconnects without waiting for the > server's responses. Under the right conditions, spamdyke can duplicate > up to 4K of the end of the data. I'm still looking -- there may be more > bugs lurking. > > I have a question for everyone who's seeing file corruption. In emails > with multiple attachments, do you ever get messages where multiple > attached files are corrupted OR is it only one file corrupted in each > message? > > -- Sam Clippinger > > Sam Clippinger wrote: >> Can you send me the full log from a message with corrupted images >> (privately if you prefer)? It would be best if the message was a test >> where you have the original images so I could compare the original data >> with the corrupted data. >> >> Also, could you test this problem with version 3.1.4? It would be very >> handy to know exactly which version introduced this bug. >> >> -- Sam Clippinger >> >> Dragomir Denev wrote: >>> Hi all, >>> >>> >>> >>> I have spamdyke 3.1.5 and I noticed that all my attached images are >>> corrupted when sending e-mails. When I disable spamdyke images are OK. >>> I >>> tested this thoroughly and I am positively sure that spamdyke is >>> causing >>> the file corruption. Downgrading to 3.1.3 also fixes the problem. >>> >>> >>> >>> My setup: >>> >>> >>> >>> - CentOS 4 >>> >>> >>> >>> - spamdyke 3.1.5 >>> >>> >>> >>> - qmail with SMTPAuth and TLS >>> >>> >>> >>> - spamdyke and qmail are run via xinetd service: >>> >>> /var/qmail/bin/tcp-env -Rt0 /usr/local/bin/spamdyke -f >>> /etc/spamdyke.conf /var/qmail/bin/qmail-smtpd >>> /home/lxadmin/mail/bin/vchkpw true >>> >>> >>> >>> - my conf file: >>> >>> log-level=2 >>> >>> tls-certificate-file=/var/qmail/control/servercert.pem >>> >>> reject-empty-rdns >>> >>> reject-unresolvable-rdns >>> >>> reject-ip-in-cc-rdns >>> >>> ip-in-rdns-keyword-file=/home/spamdyke/blacklist_rdns_keywords >>> >>> ip-blacklist-file=/home/spamdyke/blacklist_ip >>> >>> ip-whitelist-file=/home/spamdyke/whitelist_ip >>> >>> rdns-whitelist-file=/home/spamdyke/whitelist_rdns >>> >>> local-domains-file=/var/qmail/control/rcpthosts >>> >>> recipient-blacklist-file=/home/spamdyke/blacklist_recipients >>> >>> sender-blacklist-file=/home/spamdyke/blacklist_senders >>> >>> reject-missing-sender-mx >>> >>> graylist-min-secs=300 >>> >>> graylist-max-secs=1814400 >>> >>> greeting-delay-secs=5 >>> >>> max-recipients=5 >>> >>> idle-timeout-secs=60 >>> >>> >>> >>> Best regards, >>> >>> drank >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> spamdyke-users mailing list >>> [email protected] >>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users >> _______________________________________________ >> spamdyke-users mailing list >> [email protected] >> http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
