Re: [Mutt] #2995: Mutt is folding subject line folds using a tab,

#2995: Mutt is folding subject line folds using a tab, which appears to be against RFC 2822 --+- Reporter: frnkblk | Owner: mutt-dev Type: defect | Status: new

Re: [Mutt] #3220: memory leak in mutt_edit_headers()

#3220: memory leak in mutt_edit_headers() -+-- Reporter: int-e | Owner: mutt-dev Type: defect | Status: closed Priority: minor | Milestone: Component: mutt| Version: 1.5.1

Re: [Mutt] #3221: Detect modified In-Reply-To headers and clear

#3221: Detect modified In-Reply-To headers and clear References header. --+- Reporter: int-e| Owner: mutt-dev Type: enhancement | Status: new Priority: major| Milestone:

Re: [Mutt] #3080: incorrect display of headers related to folding

#3080: incorrect display of headers related to folding --+- Reporter: vinc17 | Owner: pdmef Type: defect | Status: assigned Priority: minor| Milestone: 1.6 Component: display |

Re: [Mutt] #2995: Mutt is folding subject line folds using a tab,

Hi, * Derek Martin wrote: > Actually, taking another look at this, I don't understand why this > function exists at all... As far as I can tell, there are no > circumstances under which a header should *ever* contain any > characters other than 7-bit ASCII. RFC (2)822 clearly states so, and > t

Re: [Mutt] #3222: compilation of snapshot from 20090419 fails on

#3222: compilation of snapshot from 20090419 fails on Solaris --+- Reporter: grobian | Owner: mutt-dev Type: defect | Status: closed Priority: major| Milestone: Component: mutt

Re: [Mutt] #3217: mutt-1.5.19: compile with gpgme backend fails on

#3217: mutt-1.5.19: compile with gpgme backend fails on systems with missing mkdtemp --+- Reporter: Thomas Wiegner | Owner: mutt-dev Type: defect | Status: closed Priority:

Re: [Mutt] #2995: Mutt is folding subject line folds using a tab,

#2995: Mutt is folding subject line folds using a tab, which appears to be against RFC 2822 --+- Reporter: frnkblk | Owner: mutt-dev Type: defect | Status: new