>Error: syntax error in report address in
>/usr/share/assp/files/blockreportuser.txt in entry
>*...@non_local_domain=>[email protected]=>2
>According to help text that should be a valid entry (?)
?? - replace 'non_local_domain' with the ('non local') domain name you
want to search for.
>I'd suggest to make subject bold ("strong")
Edit the 'blockreport_sub.txt' to do this.
>1) The markup für the icon in the html part of the block report
sometimes gets splitted within the cid: number, like
ASSP is not doing this nor should this be done by the HTML-Browser. It
could be happen that a source viewer shows the HTML source this way, but
this could be ignored.
Thomas
Von: Zrin Ziborski <[email protected]>
An: ASSP development mailing list <[email protected]>
Datum: 17.08.2010 11:25
Betreff: [Assp-test] Further problems with Block-reports
Am 16.08.2010 08:20, schrieb Thomas Eckardt:
>> looking for the cause of doubled MIME markup in block-report:
[...]
>> push( @textreasons, $user{sum}{mimehead} )
> comment the line out - tell me it if it solves the double MIME markup
> (possibly yes - because the mimehead is separately added to every
> BlockReport)
It seems that this did the trick.
Further problems:
1) The markup für the icon in the html part of the block report
sometimes gets splitted within the cid: number, like
<img src=cid:1
000 alt="request ASSP to resend this blocked email" border=0 width="16"
height="16">
which of course breaks it.
Perhaps inserting a newline before it would help?
2) While looking at the logs I've found following (2.0.1 / 1.1.27):
Error: syntax error in report address in
/usr/share/assp/files/blockreportuser.txt in entry
*...@non_local_domain=>[email protected]=>2
According to help text that should be a valid entry (?)
A uggestion:
In order to make html block report more readable I'd suggest to make
subject bold ("strong") and to insert a line break before it - I've added
$line =~ s/\[([^\]]+)\] ;/<br\/>[<strong>$1<\/strong>]/;
to getBlockReasons just before "$line = Encode::encode("utf-8", $line)
...", but I guess there's a cleaner solution.
TIA,
Zrin
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
