Forums Bug Reports notify doesn't work on some servers. (from 7.74)

Hi, I'm a mirc version 7.75, I've noticed that since the last version (7.74), with the latest updates, notify doesn't work on some servers.
I don't see notify icons, I don't see messages that tell me whether the users I've chosen are online or not.
It's practically as if it wasn't there.

However, this only happens on SOME servers, not on all.
for example: irc.simosnap.com DOES NOT WORK
for example: irc.rispettiinformatiche.it IT WORKS

I don't know if it's a question of watch and monitor, perhaps when a server supports both the mirc chooses one of the two and then blocks.
It would be nice to have the ability to CHOOSE whether to use the watch or monitor function depending on the server we are chatting on.
This is to always have the notify function working!
To make it work on all servers I have to downgrade and install a version of mirc prior to 7.74 (for example 7.73 works fine on all servers).
Can it be solved?

I tried connecting to "simosnap", but it did not like my IP address/country. "rispettiinformatiche" does not resolve.

Can you paste the command into your server/status window and paste the responses from both networks?

I write /server irc.simosnap.com
|2023-11-29/ 09:07:51| * Connecting to irc.simosnap.com (+6697)
-
|2023-11-29/ 09:07:52| -gra2.simosnap.com- *** Looking up your hostname...
|2023-11-29/ 09:07:52| -gra2.simosnap.com- *** Found your hostname (net-2-40-102-226.cust.vodafonedsl.it)
-
|2023-11-29/ 09:07:52| Caps supported: account-notify account-tag away-notify batch cap-notify chghost draft/relaymsg=/ echo-message extended-join extended-monitor inspircd.org/poison invite-notify labeled-response message-tags multi-prefix sasl=EXTERNAL,PLAIN server-time standard-replies sts=duration=5184000,preload userhost-in-names

|2023-11-29/ 09:07:52| Caps set: account-notify account-tag away-notify batch cap-notify chghost extended-join extended-monitor invite-notify labeled-response message-tags multi-prefix server-time standard-replies userhost-in-names

/server irc.risposteinformatiche.it
|2023-11-29/ 09:09:49| * Connecting to irc.risposteinformatiche.it (6667)
-
|2023-11-29/ 09:09:50| * Using STS secure port +6697
-
|2023-11-29/ 09:09:50| -s2.risposteinformatiche.it- *** Looking up your hostname...
|2023-11-29/ 09:09:50| -s2.risposteinformatiche.it- *** Checking ident...
|2023-11-29/ 09:09:50| -s2.risposteinformatiche.it- *** No ident response; username prefixed with ~
|2023-11-29/ 09:09:50| -s2.risposteinformatiche.it- *** Found your hostname (cached)
-
|2023-11-29/ 09:09:53| Caps supported: * sts=port=6697,duration=15552000 unrealircd.org/link-security=2 unrealircd.org/plaintext-policy=user=allow,oper=deny,server=deny unrealircd.org/history-storage=memory draft/metadata-notify-2 draft/metadata=maxsub=20 away-notify invite-notify extended-join userhost-in-names multi-prefix cap-notify setname tls chghost account-notify message-tags batch server-time account-tag echo-message labeled-response draft/chathistory extended-monitor standard-replies
|2023-11-29/ 09:09:53| Caps supported: unrealircd.org/json-log

Thanks for your bug report. I was able to reproduce this issue on the simosnap server.

Newer versions of mIRC use MONITOR instead of WATCH when a server supports both because MONITOR is the newer, and better, implementation, in the same way that WATCH is used over ISON when available.

mIRC expects hostnames to be sent in WATCH and MONITOR replies. For some reason, the simosnap server is sending user hostnames in WATCH replies - but not in MONITOR replies.

Technically, user hostnames are not required in MONITOR replies but I have never come across a case where a server has not sent this, since the usefulness of user hostnames is one of the reasons why these notify protocols were created over the older ISON protocol. So this is an odd MONITOR configuration choice by the simosnap server administrator.

In any case, I will make a change to allow MONITOR to work without user hostnames. This change should be in the next beta version.

Thank you very much Khaled. You're the best!