When a time-driven Input Agent of type Mail retrieves the contents of a mailbox, it is forced to take all emails in the mailbox. This happens regardless of whether the emails are processed by the current profile. Afterwards, a processing profile has to be found for each email.

Something similar applies to the input agent of type SMTP. An email sent to Lobster_data via SMTP must be accepted by Lobster_data (not a profile). If an email has been received by Lobster_data, a processing profile has to be found for that the email.

Best Practice

Due to these circumstances, it is advisable to use a dispatcher profile for the sake of clarity (even though you do not have to).

For the Input Agent Mail (POP3(S), IMPAP(S), X.400), i.e. if you actively pick up emails from a server, there is an explicit mechanism for this with the distribution rules. Important note: If you want to test a profile with such an Input Agent (manual restart), it must be active so that emails are not moved to the Unresolved area. In addition, you should switch to Trigger/another profile in the Times tab (other time specifications only work if the profile itself is not entered as the processing profile).
For the Input Agent SMTP, i.e. if Lobster_data acts as an email server, the profile that uses this Input Agent should forward the emails to other profiles via Message. See section Profile Chains.