| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This also affected imap_reopen().
Add a supplementary test that the CL_EXPUNGE flag does have
the intended effect.
Closes GH-6732
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
UIDs in PHP 8.0.0
Checking for a valid Unique ID (UID) cannot use the convenience macro as they might
be larger than the message number which has for maximum value the total number of
current messages available in the mailbox.
|
|
|
|
|
|
| |
Small drive by refactoring to use HashTables
Closes GH-6371
|
|
|
|
| |
Apply patch which was attached to the bug in July 2018
|
| |
|
|\
| |
| |
| |
| | |
* PHP-7.4:
Fix #80242: imap_mail_compose() segfaults for multipart with rfc822
|
| |\
| | |
| | |
| | |
| | | |
* PHP-7.3:
Fix #80242: imap_mail_compose() segfaults for multipart with rfc822
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
libc-client expects `TYPEMESSAGE` with an explicit subtype of `RFC822`
to have a `nested.msg` (otherwise there will be a segfault during
free), but not to have any `contents.text.data` (this will leak
otherwise).
Closes GH-6345.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Add char* cast to avoid compiler warnings
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Add char* cast to avoid compiler warnings
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In libc-client 2007f `data` is declared as `unsigned char *`; there may
be variants which declare it as `void *`, but in any case picky
compilers may warn about a pointer type mismatch in the conditional
(and error with `-W-error`), so we're adding a `char *` cast for good
measure.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Properly fix #80220
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Properly fix #80220
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The original fix for that bug[1] broke the formerly working composition
of message/rfc822 messages, which results in a segfault when freeing
the message body now. While `imap_mail_compose()` does not really
support composition of meaningful message/rfc822 messages (although
libc-client appears to support that), some code may still use this to
compose partial messages, and using string manipulation to create the
final message.
The point is that libc-client expects `TYPEMESSAGE` with an explicit
subtype of `RFC822` to have a `nested.msg` (otherwise there will be a
segfault during free), but not to have any `contents.text.data` (this
will leak otherwise).
[1] <http://git.php.net/?p=php-src.git;a=commit;h=0d022ddf03c5fabaaa22e486d1e4a367ed9170a7>
Closes GH-6343.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix broken fix for #80239
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix broken fix for #80239
|
| | |
| | |
| | |
| | | |
No idea why that `git am` failed that badly.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80239: imap_rfc822_write_address() leaks memory
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80239: imap_rfc822_write_address() leaks memory
|
| | |
| | |
| | |
| | | |
We have to free the address when we're finished with it.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #64076: imap_sort() does not return FALSE on failure
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #64076: imap_sort() does not return FALSE on failure
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If unsupported `$search_criteria` are passed to `imap_sort()`, the
function returns an empty array, but there is also an error on the
libc-client error stack ("Unknown search criterion: UNSUPPORTED
(errflg=2)"). If, on the other hand, unsupported `$criteria` or
unsupported `$flags` are passed, the function returns `false`. We
solve this inconsistency by returning `false` for unsupported
`$search_criteria` as well.
Closes GH-6332.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Ignore memory leaks reported for some libc-client functions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At least on Windows, some static variables are lazily initialized
during `mail_open()` and `mail_lsub()`, which are reported as memory
leaks. We suppress these false positives.
Closes GH-6326.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80226: imap_sort() leaks sortpgm memory
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80226: imap_sort() leaks sortpgm memory
|
| | |
| | |
| | |
| | |
| | |
| | | |
We need to free what we have allocated.
Closes GH-6327.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These are typical boolean parameters, so we shouldn't advertize them as
integers. For the `$reverse` parameter that even fixes expectations,
because the `reverse` member is a bitfield of 1 bit, so assigning any
even integer would not set it.
Closes GH-6328.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80216: imap_mail_compose() does not validate types/encodings
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80216: imap_mail_compose() does not validate types/encodings
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to check whether the given `type`s and `encoding`s are within
bounds to avoid segfaults and out-of-bound reads.
Closes GH-6323.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80223: imap_mail_compose() leaks envelope on malformed bodies
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80223: imap_mail_compose() leaks envelope on malformed bodies
|
| | |
| | |
| | |
| | |
| | |
| | | |
We have to clean up even on failure.
Closes GH-6322.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80220: imap_mail_compose() may leak memory
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80220: imap_mail_compose() may leak memory
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Unless `topbod` is of `TYPEMULTIPART`, `mail_free_body()` does not free
the `nested.part`; while we could do this ourselves, instead we just
ignore additional bodies in this case, i.e. we don't attach them in the
first place.
Closes GH-6321.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80215: imap_mail_compose() may modify by-val parameters
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80215: imap_mail_compose() may modify by-val parameters
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We separate the input arrays and all sub-arrays to avoid modification
of the passed parameters.
This should be rewritten to use `zend_string`s for the "master" branch.
Closes GH-6316.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-7.4:
Fix #80213: imap_mail_compose() segfaults on certain $bodies
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.3:
Fix #80213: imap_mail_compose() segfaults on certain $bodies
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have to cater to non-associative arrays where the key may be `NULL`;
we just skip these elements.
Closes GH-6315.
|
| | |
| | |
| | |
| | |
| | | |
`rpath` may be `NULL` here, in which case we must not access its
members.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Drop some dependencies on argc at the same time
Closes GH-6164
|
| | |
| | |
| | |
| | | |
Closes GH-6179
|
| | | |
|