Avoiding ping-pong effects

Many companies use an automatic reply function to let their email communication partners know that an email has reached them. If this mechanism is configured on the communication partner’s server as well, an endless row of confirmations will be sent back and forth between the two – the so-called ping-pong effect. This is something to avoid, if only for performance reasons.

The following example shows how you can avoid this effect:

You want to give your communication partners feedback on every email that is sent to your domain and that you accept. You can do this with an iQ.Suite Wall or iQ.Suite action job. Whichever method you choose, the steps you take to avoid a confirmation mail being sent in response to a confirmation mail is always the same:

• Enter dedicated addresses for which you do not want to send a confirmation mail on the "Misc" tab under "Memo from" for the individual job.

• Create a mail address rule that defines these addresses as recipients.

• Include this rule in the list of "Dependence on negated rules" on the "Basics" tab.

Once you have saved the job, the mail grabber task restarts and all emails that are sent to one of the addresses you have listed are no longer automatically confirmed.

With regard to email handling and structured email processing, the ‘devil is often in the details’. At our training courses, we identify some of these "minor problems with major impact" and configure solutions with you in practical exercises.

Come and see. We look forward to your visit!