Skip Menu |
 

This queue is for tickets about the MailTools CPAN distribution.

Report information
The Basics
Id: 26093
Status: resolved
Priority: 0/
Queue: MailTools

People
Owner: Nobody in particular
Requestors: robertojimenoca [...] terra.es
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Documentation for "Remove last newline from $entity->head->get('Subject')"
MIME-Version: 1.0
X-Mailer: MIME-tools 5.418 (Entity 5.418)
Content-Type: text/plain; charset="utf8"
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 788
Download (untitled) / with headers
text/plain 788b
ON Bug#26087 MARKOV wrote: Show quoted text
> The removal of \n\s+ from the header field content is the removal of > field folding, as desribed in the RFC. Folding can appear unexpectedly, > introduced by mail transfer agents, and is therefore automatically > removed. > > Actually, unfolding should only remove \n\s (without a \s*), but that's > an historical mistake, which I cannot repair without breaking existing > applications. For the same reason, I cannot remove the \n after the > field content when it is returned: it will break existing code, and it > is not worth that. > > If you want code which is RFC compliant and which does chomp for you, > use MailBox, not MailTools.
Could you include exactly what you said in the $entity->head->get() documentation so nobody has to ask for it again?
MIME-Version: 1.0
X-Mailer: MIME-tools 5.418 (Entity 5.418)
Content-Disposition: inline
Message-Id: <rt-3.6.HEAD-29880-1176190238-905.26093-0-0 [...] rt.cpan.org>
Content-Type: text/plain; charset="utf8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
Content-Length: 46
I have included these two remarks in the docs.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.