>looking for the cause of doubled MIME markup in block-report:
>in sub genBlockReports there is a line (23255 in 2.0.1-1.1.27)
> push( @textreasons, $user{sum}{mimehead} );
>adding MIME header to the text part (!?)
>Is this the culprit?
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)
Thomas
Von: Zrin Ziborski <[email protected]>
An: ASSP development mailing list <[email protected]>
Datum: 15.08.2010 21:01
Betreff: Re: [Assp-test] Problems with Block-report message format
Hi,
looking for the cause of doubled MIME markup in block-report:
in sub genBlockReports there is a line (23255 in 2.0.1-1.1.27)
push( @textreasons, $user{sum}{mimehead} );
adding MIME header to the text part (!?)
Is this the culprit?
My BlockReportFile:
*...@*=>=>2 # next run: 2010-8-17
*...@non_local_domain=>[email protected]=>2
I'm looking at the produced block-report message
and the sub getBlockReasons, building my $mimehead:
[...]
my $mimehead = <<"EOT";
MIME-Version: 1.0
EOT
$mimehead .= <<"EOT" if ( $BlockReportFormat != 1 );
Content-Type: multipart/related;
boundary=\"$relboundary\"
--$relboundary
EOT
[...]
I think it would be (more) logical (unless BlockReportFormat is
"text-only",)
to set the Content type of the message to multipart/alternative, not
multipart/related.
Then the html part would have "Content-Type: multipart/related" with
one text/html and one image/gif part.
I see it does "work" (message is displayed) in Thunderbird with switched
order as
well, but when composed (e.g.) in Thunderbird or with maildrop/makemime
the
structure is
multipart/alternative { text/plain | multipart/related { text/html
| image/gif } }.
best regards,
Zrin
Am 13.08.2010 09:30, schrieb Zrin Ziborski:
> Hello,
>
> the block reports generated on schedule are often (or always?) shown as
> empty in Thunderbird.
> I've observed this with version 2.0.1 (1.1.12) and now 2.0.1 (1.1.27) as
> well.
> If I request the block report, then the structure of the message is ok
> and the contents is shown as expected in the e-mail client.
>
> Example of problematic block-report - notice that MIME markup is
doubled:
>
> Return-path:<[email protected]>
> Envelope-to: [email protected]
> [...]
> To: [email protected]
> From:<[email protected]>
> Subject: ASSP-Block-Report fÃŒr [email protected]
> MIME-Version: 1.0
> Content-Type: multipart/related;
> boundary="=======_00_ASSP_1298347655_======"
> Message-Id:<[email protected]>
> Date: Fri, 13 Aug 2010 08:00:08 +0200 (CEST)
>
> --=======_00_ASSP_1298347655_======
> Content-Type: multipart/alternative;
> boundary="=======_01_ASSP_1298347655_======"
>
> MIME-Version: 1.0
> Content-Type: multipart/related;
> boundary="=======_00_ASSP_1298347655_======"
>
> --=======_00_ASSP_1298347655_======
> Content-Type: multipart/alternative;
> boundary="=======_01_ASSP_1298347655_======"
>
>
> --=======_01_ASSP_1298347655_======
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: Quoted-Printable
>
> For a better view of this email - please enable html in your client!
>
> ASSP-Block-Bericht fuer die letzten 2 Tage vom mx1.safemail.at fuer
[email protected]
> [...]
>
>
> Example of well formed block-report:
>
> Return-path:<[email protected]>
> Envelope-to: [email protected]
> [...]
> To: [email protected]
> From: [email protected]
> Subject: ASSP-Block-Report für [email protected]
> MIME-Version: 1.0
> Content-Type: multipart/related;
> boundary="=======_00_ASSP_1298347655_======"
> Message-Id:<[email protected]>
> Date: Fri, 13 Aug 2010 09:17:23 +0200 (CEST)
>
> --=======_00_ASSP_1298347655_======
> Content-Type: multipart/alternative;
> boundary="=======_01_ASSP_1298347655_======"
>
>
> --=======_01_ASSP_1298347655_======
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: Quoted-Printable
>
> For a better view of this email - please enable html in your client!
>
> ASSP-Block-Bericht fuer die letzten 5 Tage vom mx1.safemail.at fuer
[email protected]
> [...]
>
> Thank you,
> 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
------------------------------------------------------------------------------
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
