How to use GlockApps: a controlled first test

Prepare one reproducible question

Choose a representative message and the production sending route you are authorized to test. Record the visible From address, sending platform, template version and time. Do not upload customer lists, passwords or private correspondence. The official help page describes manual, smart and automatic modes; start with the smallest mode that answers your question.

• Use a non-sensitive representative message.
• Keep the sender and route constant.
• Write one expected observation and one stop condition.
• Assign a person who can investigate configuration warnings.

Run a manual Inbox Insight test

The official workflow says to sign in, open Inbox Insight, start a spam test and select a manual test. GlockApps then provides a unique identifier and seed list. Follow the live instructions exactly: place the identifier where the interface requires it and send through the route being investigated. The interface can change, so the provider help page—not this summary—is the operational source of truth.

Read the report by signal

Separate mailbox placement, authentication observations and content/filter warnings. A warning can suggest where to investigate; it is not proof of the only cause. Compare the result with headers and sending logs. If a test is waiting for data, verify the identifier, recipient list and sending route before creating another test.

Retest one meaningful change

State the proposed explanation, change one relevant variable and repeat an equivalent test. If the sending platform changes the IP pool or tracking domain, document that uncertainty. Stop when the original question is answered or when access to DNS, logs or platform settings is required.