severity 688853 normal
retitle 688853 Incorrect error message when a line is too long in a message
thanks
Le jeudi 27 septembre 2012 07:23:49, Andrey a écrit :
'Broken pipe' error occurs in Exim because Dspam just drops connection
while Exim trying to send data to the socket though 530 reply
Package: dspam
Version: 3.10.1+dfsg-3~bpo60+1
Severity: critical
dspam sends '530 5.2.0 Message is empty. Aborting.' while receiving
incorrect spam message with long-long line, for example with length
about 300K bytes:
Le mercredi 26 septembre 2012 11:07:09, vous avez écrit :
Package: dspam
Version: 3.10.1+dfsg-3~bpo60+1
Severity: critical
dspam sends '530 5.2.0 Message is empty. Aborting.' while receiving
incorrect spam message with long-long line, for example with length
about 300K bytes:
From what
severity 688853 grave
thanks
Le mercredi 26 septembre 2012 14:40:20, Thomas Preud'homme a écrit :
Le mercredi 26 septembre 2012 11:07:09, vous avez écrit :
Package: dspam
Version: 3.10.1+dfsg-3~bpo60+1
Severity: critical
dspam sends '530 5.2.0 Message is empty. Aborting.' while
Yes, I see in daemon_getline() function in daemon.c it tries to read
buf[1024] with some timeout and get. But it seems that read_sock()
returns NULL message.
26.09.2012 16:40, Thomas Preud'homme пишет:
Le mercredi 26 septembre 2012 11:07:09, vous avez écrit :
Package: dspam
Version:
'Broken pipe' error occurs in Exim because Dspam just drops connection
while Exim trying to send data to the socket though 530 reply occurs
also. I don't know whether this is the SMTP RFC rules? And this behavior
causes delay and retries to send email to the other Dspam users.
26.09.2012
6 matches
Mail list logo
