I was trying to keep the naming consistent with the naming of the functions in the
c-client lib. The actual c-client function called is mail_fetch_header, so it became
imap_fetch_header. It seems to be the general way in which the original imap module
developers named their functions. But, I
Sorry, I'm just catching up with email backlog, so this email might be
irrelevant by now, but just in case it isn't:
imap_fetch_header() is probably not a very good name because we already have
imap_fetchheader() and I believe they might be a bit too similar in names (I don't
know what the pro
OK, did a little digging and it seems that it is not (necessarily) PHP that
doesn't support the x.HEADER/x.TEXT syntax... The c-client function called
by imap_fetchbody function calls mail_fetchbody_full (alias for
mail_fetch_body) which _does not_ support the above syntax since it only
expects i
On Wed, Feb 27, 2002 at 12:16:47PM +0900, Yasuo Ohgaki wrote :
> Brad Fisher wrote:
> >This is a function I wrote a while back so I could access more of the
> >headers available in a mail message. The imap_headers and
> >imap_fetchheaders functions work fine for retrieving headers for the
> >mai
Here is my attempt at a unified diff against the current CVS. Let me
know if I need to do anything differently.
-Brad
-- diff for php_imap.c ---
--- php_imap.c
+++ php_imap.c Tue Feb 26 23:00:58 2002
@@ -91,6 +91,7 @@
PHP_FE(imap_bodystruct,
NULL)
P
Brad Fisher wrote:
> This is a function I wrote a while back so I could access more of the
> headers available in a mail message. The imap_headers and
> imap_fetchheaders functions work fine for retrieving headers for the
> main body of a given message, but if you receive an email with an
> attac