Ƙara SOCKS zuwa abokin ciniki na IMAP na Indy ba tare da maye gurbin mai sarrafa TLS ba

Don Indy 10 IMAPClient da ke da IOHandler da ya fito daga TIdIOHandlerStack, haɗa bayanin SOCKS kafin kira Connect:

ProxyInfo := TIdSocksInfo.Create(IMAPClient);
ProxyInfo.Version := svSocks5;
ProxyInfo.Host := 'proxy.example';
ProxyInfo.Port := 1080;

(IMAPClient.IOHandler as TIdIOHandlerStack).TransparentProxy := ProxyInfo;

Nau'in sun fito daga IdSocks da IdIOHandlerStack. Idan babu IOHandler tukuna, fara ƙirƙira ka sanya mai sarrafa da ya dace da haɗin wasiƙa.

Ka kiyaye IOHandler na SSL da aka riga aka saita. Maye gurbinsa da mai sarrafa stack na fili na iya cire TLS; TransparentProxy yana ba da tattaunawar wakili kawai, ba TLS na ɓoye a kan 993 ko STARTTLS a kan 143 ba.

Sashin yana ɗauka SOCKS5 ba tare da tabbatarwa ba. Don uwar garken wasiƙa na jama'a, jerin wakilan SOCKS5 yana ba da 'yan takara; tabbatar da cewa ƙarshen da aka zaɓa yana ba da izinin IMAP host da port da ake buƙata. Don asusun wakili, saita tabbatarwa, sunan mai amfani da kalmar sirri na TIdSocksInfo dabam da asusun IMAP.

ProxyInfo.Host yana ambaton mai shiga tsakani. IMAPClient.Host ya kasance sabis ɗin wasiƙa da shaida ta TLS da ake nufi da manufar tabbatar da takardar shaida.