How do I update my data on a profiles subprofile?
The resource url's on both pages are very different and I don't know how to specifically update / PUT, for example, data for user 65 on subprofile 18, like I can with the post method.

Are the url's for the docs wrong or am I just missing something?
POST url: https://www.copernica.com/en/documentation/restv2/rest-post-profile-subprofiles
PUT url: https://www.copernica.com/en/documentation/restv2/rest-put-profile-subprofiles

There's an issue with the get() method vs. documentation/restv2/rest-fields-parameter:
You cannot pass a fields parameter into the example client and have it be handled correctly, because the '[]' part of 'fields[]' will always be encoded.

Replacement for the http_build_query() call: $this->encodeParams(), as in:

  /**
   * Converts parameters into an encoded string.
   *
   * An example of passing the 'fields' parameter into this function:
   * ['fields' => ['land==netherlands', 'age>16']]
   *
   * @param array $parameters
   *   An array with key-value pairs, where the value can also be an array. In
   *   the latter case, the key will be present multiple times in the resulting
   *   query string, as 'key[]'.
   *
   * @return string
   *   The encoded URL parameters, including a leading '?'.
   */
  private function encodeParams(array $parameters)
  {
      $encoded_parts = [];

      foreach ($parameters as $key => $value) {
          if (is_array($value)) {
              // This will come out as key[]=subvalue1&key[]=subvalue2; the
              // keys inside $value are ignored. The important thing here is
              // that the [] are NOT URL-encoded.
              foreach ($value as $subvalue) {
                  // Testing with a value containing spaces suggests that both
                  // urlencode() and rawurlencode() are good for Copernica.
                  $encoded_parts[] = rawurlencode($key) . '[]=' . rawurlencode($subvalue);
              }
          } else {
              $encoded_parts[] = rawurlencode($key) . '=' . rawurlencode($value);
          }
      }

      return $encoded_parts ? '?' . implode('&', $encoded_parts) : '';
  }

New version of mailerQ 4.0.x has a totals box in the Overview section of the web UI titled "Strange". No documentation found.

smtp logins not working

showing the following error

Transaction failed. The server response was: 5.7.1 Relay access denied

docs proper not updated to troubleshoot

From release notes at https://www.mailerq.com/product/releasenotes#5.9.1

REST API: add support for HTTP and Socks proxy in External MTAs.

But is not documented how should be indicate to use in the rest api.
I assume that could be put the value http or socks in the protocol field of the request.

The Makefile is different in the downloadable demo archive from the example on this page: https://www.php-cpp.com/documentation/your-first-extension

The demo archive seems to contain an older version only for php 5.

Here's the actual diff:

 #
 #   Php.ini directories
 #
@@ -28,9 +27,22 @@ NAME             =   yourextension
 #   PHP installations use a conf.d directory that holds a set of config files,
 #   one for each extension. Use this variable to specify this directory.
 #
+#   In Ubuntu 14.04 Apache 2.4 is used, which uses the mods-available directory
+#   instead of a conf.d directory. In 16.04 the directory changed yet again.
+#   This has to be checked.
+#
 
-INI_DIR                =   /etc/php5/conf.d
+UBUNTU_MAJOR  := $(shell /usr/bin/lsb_release -r -s | cut -f1 -d.)
+OVER_SIXTEEN  := $(shell echo "${UBUNTU_MAJOR} >= 16" | bc)
+OVER_FOURTEEN := $(shell echo "${UBUNTU_MAJOR} >= 14" | bc)
 
+ifeq (${OVER_SIXTEEN}, 1)
+    INI_DIR     =   /etc/php/7.0/mods-available/
+else ifeq (${OVER_FOURTEEN}, 1)
+    INI_DIR     =   /etc/php5/mods-available/
+else
+    INI_DIR     =   /etc/php5/conf.d/
+endif

I found some result json message that indicate the idle state, but is not documented in https://www.mailerq.com/documentation

I just noticed that some dutch translation is missing.
REST API v2 Documentation: De Fields Parameter

The page: https://www.copernica.com/en/topuseragents

simply shows no data, and heading is white as background is so content is not visible.

Currently I'm able to select profiles based on their unique ID or their Email.

My flow now requires that I get alle profiles with either the given ID or Email.
For example:

        $parameters = array(
            'limit'     =>  1000,
            'fields'    =>  array(
                'rw_id==123',
                '[email protected]'
            )
        );

If the profile with ID 123 does not have [email protected] than it will not show in the response data.

If this is already possible, please let me how.

I followed the below documentation.
https://www.copernica.com/nl/documentation/restv2/rest-fields-parameter

Sorry, no PR.

I just noticed a difference in the return value between https://www.copernica.com/en/documentation/restv2/rest-get-publisher-emailings and https://www.copernica.com/en/documentation/restv2/rest-get-publisher-emailings -- in v3 these are missing in the docs:

* errors: Number of errors for this mailing
* unsubscribes: Number of unsubscribes for this mailing
* abuses: Number of abuses for this mailing

...however they are actually returned. Not sure if they were deleted by accident, or restored in a later version or v3, or ....

The "publisher/destinations" call (i.e. a full list of destinations from/to a certain date) works, but is not documented in the list at https://www.copernica.com/en/documentation/restv3/rest-api.

This unlike the "ms/destinations" call which is documented.

(AFAICT this call is fairly crucial for getting MS statistics and less crucial for Publisher, but it's still nice to know it exists.
Though I could also be wrong on the "less crucial" part; getting to know the differences between the two systems, is a bit of a challenge at first sight :) )

(OK, I think this is my last question.)

https://www.copernica.com/en/documentation/restv2/rest-requests says

DELETE requests can also result in a "204 No Content" response in case the data that was meant to be deleted could not be located.

... and I don't see that. Maybe there are some entities where this is true (I'm just testing profiles and subprofiles), but I see a HTTP 400 with a standard JSON 'error/message' body being returned. (Containing either "This profile has already been removed" or "No profile with supplied ID".)

Maybe that particular edit in #f32cbca was only meant for v1 of the API? (In that case, it seems like that sentence can just be deleted... because the message about the 400 response is still on the page.)