Bug#849770: exim4: bogus reject response on overlong lines
It seems you are missing the size check in the DATA ACL and so the
messages are refused in the transport that, as you report, gives a very
unhelpful error.
The "acl/40_exim4-config_check_data" that ships with stretch should
refuse the messages with "maximum allowed line length is 998 octets, got
$max_received_linelength", which is much more helpful:
acl_check_data:
# Deny if the message contains an overlong line. Per the standards
# we should never receive one such via SMTP.
#
.ifndef IGNORE_SMTP_LINE_LENGTH_LIMIT
deny message = maximum allowed line length is 998 octets, \
got $max_received_linelength
condition = ${if > {$max_received_linelength}{998}}
.endif
I had to disable the check because it was blocking many legitimate
messages, so it should probably not be the default.
Rúben
Bug#686314: Wheezy Instalation Report on Samsung NP305U1A
Em 31-08-2012 06:09, Christian PERRIER escreveu: Can you confirm that loading the fuse module *during the install process before the boot loader setup* was enough for W7 to be detected? The first time the boot loader setup run it did not find W7. I went back several times and retried the setup. The same. Then I lookup up the installation scripts and one of them (don't remember now which one) called grub-mount. I invoked grub-mount on the command line and got the error fuse not available or something like that. I tried to insmod fuse but the module was not found. Then I installed the fuse module from the target dir. Retried the boot loader setup and W7 was now found. If it helps I can reinstall wheezy from scratch. Just Let me know which information I should collect. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
