Premise: When sending messages to a user who has an away message set (/AWAY), you will receive that away message from the server (RAW 301). You will receive it each time, over and over, when you message and respond to the user as long as they have an away set. A conversation will become interleaved with these away messages, and so it becomes obnoxious.

I wish to suggest that mIRC automatically suppresses these messages after the first one is displayed.

Getting into technicalities, Away Message Suppression should be based on these conditions:

- The target's nickname remains unchanged.
- The away message contents remains unchanged.
- Suppression expires after 7200 minutes (2 hours) since the last 301 was received.
- Suppression is temporarily disabled while performing a /WHOIS on the user, between RAW 311 and RAW 318, because RAW 301 is also displayed in /WHOIS.

I have written an example mIRC script to demonstrate this behavior. The intent of this feature request is not to require all mIRC users to utilize this script to enjoy its benefits.

Code:
#MuteAwayMsg on
RAW 301:*: {
  var %nick = $2, %awaymsg = $3-
  if ($hget(miscellaneous,MuteAwayMsg. $+ $cid $+ %nick) == %awaymsg) { halt }
  hadd -mu7200 miscellaneous MuteAwayMsg. $+ $cid $+ %nick %awaymsg
} ; by Raccoon 2017
#MuteAwayMsg end
RAW 311:*: .disable #MuteAwayMsg
RAW 318:*: .enable #MuteAwayMsg

Well. At least I won lunch.
Good philosophy, see good in bad, I like!