Forums Bug Reports Passive dcc-send filetype rejected

I searched and didn't find anything about this. I'm not sure if it's a bug or not, it depends on whether there's a reason why mIRC should reject an ignored filetype on a passive send it's making, which doesn't happen on a non-passive dcc-send. It would be nice if mIRC would differentiate between a 'normal' dcc send and the pseudo-send reply coming back from a passive recipient.

When you have dccignore set to only accept a few filetypes, and *.dat is not on the accepted list, you expect to not be able to receive .dat files, but normal dcc-send allows you to send them, but:

/dcc passive on
* Passive DCC is on
/write test.dat test
/dcc send receiver test.dat

DCC Send from receiver rejected (test.dat, file type ignored)

Fails even though the receiver is accepting filetype *.dat

Are you sure he has removed you from ignore list?

Are you sure he has unchecked "turn ignore back on after n minutes"

I think what is happening is that when maroon sends a file to reciever, maroon's client spits out the error and it all fails.

Omen is correct. Sender is set up to make only passive sends, but accepts only a list of filetypes that does not include *.dat. Receiver has dcc ports opened, and ignores only a list of filetypes that does not include ignoring *.dat. Sender can send test.txt, test.jpg etc to Receiver, but Sender's own dccignore settings are blocking it from passively sending test.dat

It probably is a bug. The reason this is happening is because of how the passive DCC send protocol works. Normally a CTCP (which is actually a PRIVMSG) is replied to with a CTCP REPLY (which is actually a NOTICE). This is to prevent loops and the like. But the "passive" DCC protocol requires three messages, so the first CTCP is replied to with another CTCP. mIRC is checking it against the DCC ignore list before it is checking whether it is actually an incoming DCC send or a response to an outgoing passive DCC send.

Thanks this has been fixed for the next version.