Zaahid Bateson

I had a look at this and unfortunately it may not be possible to rework this using guzzlehttp/psr7. I may be wrong and I still need to take a deeper...

Hi @thiagobit -- Message::getAllAttachments excludes only 'inline text' and 'multipart' parts, so an inline image should be returned. The documentation's not very clear on it though (working on improving that).

Yes, I think your examples are right -- there's also a convenience method in AddressHeader to get the email/name of the first header, so you could ``` $message->getHeader('from')->getPersonName() ``` or...

I still don't see the value in changing __toString or it's meaning (the "string" representation of the header). > There should be three functions to get: > > Subject: =?ISO-8859-1?Q?f=F6=F6b=E4r?=...

I get what you're saying about AddressHeader being inconsistent with its getValue and acknowledge that. In your example though, Subject, getValue would give result 3. I can think of quite...

I think you'd rarely care if 'from' contained more than one address, I think that's very uncommon.

I get it and am not disagreeing on this one as well. I feel like 'getValue' is so standard that it might be preferred even if there's a problem with...

The only deprecation I've done so far I've put up on the main readme (and main page of mail-mime-parser.org). I'd also put it up in the release notes for the...

Aah, I see what you're getting at -- yeah, I didn't do that. I only added an ``` @deprecated ``` annotation. That should be added to the deprecated functions I...

> so I think you're using getHeaderValue() for something like "give me the most important info from this header" Yeah, actually I think in that case it's different though too......