That's very strange; spamdyke should insert a CR before every bare LF in 
order to fix this problem.

Could you send me two things: first, an unaltered copy of a message with 
an attachment from your Exchange server (turn off spamdyke so it will be 
delivered correctly).  Please don't just forward it; a gzipped copy of 
the file from the user's mail directory would be best.  Second, a full 
log file from spamdyke when the Exchange server tries to deliver a 
message with an attachment.  Hopefully I can use those two things to 
figure out what's happening.

Is anyone else seeing problems like this?

-- Sam Clippinger

Hans Strandel wrote:
> Hi,
>
> Problem:
> ********
> When somebody with a microsoft exchange server (all service packs installed) 
> sends a e-mail message to our linux qmail mailserver (spamdyke 4.0.10 
> installed) AND also sends an attachment, the mail will not be delivered to 
> the mail account on our server.
>
> Maillog sample error message:
> **************************
> Dec 31 05:14:28 ns2 spamdyke[30995]: ALLOWED from: [email protected] to: 
> [email protected] origin_ip: 92.42.184.69 origin_rdns: plesk1.juhui.ch 
> auth: (unknown)
> Dec 31 05:14:28 ns2 qmail-queue-handlers[30999]: possible qmail-smtpd exited 
> by timeout, reset connection or with "See 
> http://pobox.com/~djb/docs/smtplf.html.";
>
> Hint:
> ****
> http://pobox.com/~djb/docs/smtplf.html
> It must be a CR problem, as Microsoft is not fully compatible.
>
> Solution???
> **********
> http://www.dt.e-technik.uni-dortmund.de/~ma/qmail-bugs.html
> -> 4.13. qmail-remote does not handle CR properly.
>
> When I deactivate spamdyke at all, we do not have any attachment problems.
> So there must be a configuration option to let those messages from microsoft 
> exchange server WITH attachements comming through.
>
> spamdyke.conf
> *************
> log-level=debug
> local-domains-file=/var/qmail/control/rcpthosts
> max-recipients=20
> idle-timeout-secs=300
> connection-timeout-secs=600
> graylist-dir=/var/qmail/spamdyke/greylist
> graylist-level=none
> graylist-min-secs=300
> graylist-max-secs=1814400
> policy-url=http://my.policy.explanation.url/
> sender-blacklist-file=/var/qmail/spamdyke/blacklist_senders
> recipient-blacklist-file=/var/qmail/spamdyke/blacklist_recipients
> ip-in-rdns-keyword-blacklist-file=/var/qmail/spamdyke/blacklist_keywords
> ip-blacklist-file=/var/qmail/spamdyke/blacklist_ip
> rdns-blacklist-dir=/var/qmail/spamdyke/blacklist_rdns.d
> reject-empty-rdns
> reject-unresolvable-rdns
> reject-ip-in-cc-rdns
> rdns-whitelist-file=/var/qmail/spamdyke/whitelist_rdns
> ip-whitelist-file=/var/qmail/spamdyke/whitelist_ip
> greeting-delay-secs=0
> dns-blacklist-entry=bl.spamcop.net
> dns-blacklist-entry=zen.spamhaus.org
> dns-blacklist-entry=zombie.dnsbl.sorbs.net
> dns-blacklist-entry=dul.dnsbl.sorbs.net
> dns-blacklist-entry=wormrbl.imp.ch
> dns-blacklist-entry=spamrbl.imp.ch
> reject-missing-sender-mx
> tls-certificate-file=/var/qmail/control/servercert.pem
> sender-whitelist-file=/var/qmail/spamdyke/whitelist_sender
>
> Any help is very much appreciated
> Greetings Hans
>   
_______________________________________________
spamdyke-users mailing list
[email protected]
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to