June 04, 2020
Table of Contents
- Preface
- 1. Application-level Gateway log messages
- 1.1.
- 1.1.1. Established connection
- 1.1.2. Error calling AuthenticationProvider method
- 1.1.3. Failed to parse URL filter database
- 1.1.4. Error opening socket
- 1.1.5. Error connecting UDP socket (nf)
- 1.1.6. Error querying local address (nf)
- 1.1.7. Error during setsockopt(IPPROTO_IP, IP_RECVORIGADDRS)
- 1.1.8. Error during setsockopt(IPPROTO_IPV6, IPV6_RECVORIGADDRS)
- 1.1.9. Cannot create socket
- 1.1.10. Dispatch thread starting
- 1.1.11. Accept queue stats
- 1.1.12. Dispatch thread exiting
- 1.1.13. Error creating dispatch thread, falling back to non-threaded mode
- 1.1.14. Incoming connection
- 1.1.15. Nobody was interested in this connection
- 1.1.16. Transparent listener connected directly, dropping connection
- 1.1.17. Error registering dispatch, previous entry specified accept_one
- 1.1.18. Internal error, dispatch entry not found (chain exists)
- 1.1.19. Internal error, dispatch entry not found (no chain)
- 1.1.20. Module successfully loaded
- 1.1.21. Module loading failed
- 1.1.22. eofmask updated
- 1.1.23. Packet stats timeout elapsed, and no timeout callback specified
- 1.1.24. Session ID not found for authorization
- 1.1.25. calling event
- 1.1.26. calling __destroy__() event
- 1.1.27. Internal error, trying to look up a non-ZProxyIface compatible interface
- 1.1.28. Error creating proxy thread
- 1.1.29. User initiated proxy termination request received
- 1.1.30. Trying verification without CRL check as directed by the policy
- 1.1.31. CRL has invalid nextUpdate field
- 1.1.32. CRL is expired
- 1.1.33. CRL not found for certificate
- 1.1.34. CRL not found for certificate
- 1.1.35. Error creating client socketpair for stacked proxy
- 1.1.36. Error creating server socketpair for stacked proxy
- 1.1.37. Stacking subproxy
- 1.1.38. Stacking subproxy
- 1.1.39. Error creating control socketpair for stacked proxy
- 1.1.40. Stacking program
- 1.1.41. Connecting to remote host
- 1.1.42. Connection denied by policy
- 1.1.43. Dispatcher on address
- 1.1.44. Error opening policy file
- 1.1.45. Error parsing policy file
- 1.1.46. Cannot find proxy module
- 1.1.47. Cannot find proxy module
- 1.1.48. Attribute fetched
- 1.1.49. Attribute changed
- 1.1.50. Error parsing satyr command
- 1.1.51. Internal error in z_policy_stream_new: input ZStream is NULL
- 1.1.52. Error connecting to satyrd
- 1.1.53. Satyr authentication failed, unable to determine target address
- 1.1.54. Satyr authentication failed, cannot connect to client
- 1.1.55. Error connecting to satyr, SSL handshake failed
- 1.1.56. Satyr authentication failed, unknown address family
- 1.1.57. Satyr authentication failed, unable to write request information
- 1.1.58. Satyr authentication failed, error reading answer
- 1.1.59. Invalid maximum aggregator, no source node
- 1.1.60. Invalid maximum aggregator, no source node
- 1.1.61. Failed to parse interval from node name
- 1.1.62. Invalid average aggregator, no source node
- 1.1.63. Failed to create SZIG socket
- 1.1.64. Error writing zas stream
- 1.1.65. Error booting & parsing policy
- 1.1.66. Error initializing policy
- 1.1.67. Error loading initial policy, exiting
- 1.1.68. Reloading policy
- 1.1.69. Error reloading policy, reverting to old
- 1.1.70. Unexpected EOF while transferring from server
- 1.1.71. I/O error opening error file
- 1.1.72. Eofmask is updated
- 1.1.73. Data transfer timed out
- 1.1.74. Data transfer interrupted by progress
- 1.1.75. Error reading request
- 1.1.76. Request details
- 1.1.77. Parse error, dropping request
- 1.1.78. Invalid character, dropping request
- 1.1.79. Username too long, dropping request
- 1.1.80. One hostname is too long in hostname chain, dropping request
- 1.1.81. Error write request
- 1.1.82. Error write request
- 1.1.83. Error write request
- 1.1.84. Error write request
- 1.1.85. Policy violation, abort session
- 1.1.86. Policy violation, drop session
- 1.1.87. fetching request
- 1.1.88. asking policy
- 1.1.89. connecting server
- 1.1.90. sending request
- 1.1.91. copying response
- 1.1.92. everything is done
- 1.1.93. Data connection accepted on client side
- 1.1.94. Data connection accepted on server side
- 1.1.95. Data connection established on client side
- 1.1.96. Connected to client, but connection is not expected
- 1.1.97. Data connection established on server side
- 1.1.98. Connected to server, but connection is not expected
- 1.1.99. Internal error, previous dispatcher not unregistered
- 1.1.100. Internal error, previous attach not unregistered
- 1.1.101. Internal error, previous attach not unregistered
- 1.1.102. Internal error, previous dispatcher not unregistered
- 1.1.103. Resetting data connection
- 1.1.104. Internal error, previous data connection is not closed properly
- 1.1.105. Internal error, cannot start data proxy because peers are not yet connected
- 1.1.106. Internal error, current command descriptor does not specify data transfer
- 1.1.107. Data connection established
- 1.1.108. Possible bounce attack
- 1.1.109. Possible bounce attack
- 1.1.110. Possible bounce attack
- 1.1.111. Possible bounce attack
- 1.1.112. Internal error, client side not connected
- 1.1.113. Internal error, server side not connected
- 1.1.114. Max_line_length above upper limit
- 1.1.115. Max_username_length above max_line_length
- 1.1.116. Max_password_length above max_line_length
- 1.1.117. Max_hostname_length above max_line_length
- 1.1.118. Error parsing valid_chars_username
- 1.1.119. Internal error in stream write, side is wrong
- 1.1.120. Cannot write full line
- 1.1.121. Server answer doesn't begin with number
- 1.1.122. Response arrived
- 1.1.123. Error reading from server
- 1.1.124. Line is too short to be a valid answer
- 1.1.125. Server answer has wrong continuation mark
- 1.1.126. Rejected answer
- 1.1.127. Error reading from client
- 1.1.128. Request fetched
- 1.1.129. Empty command. Aborting
- 1.1.130. Unknown command. Aborting
- 1.1.131. Internal error, known command but command parse is unset
- 1.1.132. This command not allowed in non-transparent mode
- 1.1.133. Request rejected
- 1.1.134. Proxy answer
- 1.1.135. Rejected command (aborting)
- 1.1.136. Bad policy type, aborting
- 1.1.137. Too many continuous lines in the answer
- 1.1.138. Reading from peer
- 1.1.139. Invalid port specified in non-transparent destination
- 1.1.140. Invalid character in username
- 1.1.141. Hostname specified in username is too long
- 1.1.142. Username too long
- 1.1.143. Username too long
- 1.1.144. Invalid character in username
- 1.1.145. Internal error, proxy in unknown state
- 1.1.146. Internal error, proxy in unknown state
- 1.1.147. Password too long
- 1.1.148. Password too long
- 1.1.149. Internal error, proxy in unknown state
- 1.1.150. Internal error, proxy in unknown state
- 1.1.151. Internal error, proxy in unknown state
- 1.1.152. Unexpected response to data transfer command
- 1.1.153. Internal error, proxy in unknown state
- 1.1.154. Invalid parameter for command
- 1.1.155. Invalid parameter for command
- 1.1.156. Internal error, proxy in unknown state
- 1.1.157. Missing parameter for the TYPE command
- 1.1.158. Valid, but unsupported transfer type specification
- 1.1.159. Unknown transfer type specification
- 1.1.160. Missing parameter to the MODE command
- 1.1.161. Invalid parameter to the MODE command
- 1.1.162. Missing parameter to the STRU command
- 1.1.163. Invalid parameter to the STRU command
- 1.1.164. Error preparing server-side data connection (PORT)
- 1.1.165. There was an error binding a server-side listener
- 1.1.166. Error parsing PASV response
- 1.1.167. Error preparing data connection to the server (PASV)
- 1.1.168. Error preparing server-side data connection listener (EPRT)
- 1.1.169. Cannot bind to the given address (EPRT)
- 1.1.170. Missing parameter (EPSV)
- 1.1.171. Bad parameter (EPSV), not beginning with bracket
- 1.1.172. Bad parameter (EPSV), not closing with bracket
- 1.1.173. Error parsing EPSV response
- 1.1.174. Bad parameter (EPSV), invalid port
- 1.1.175. Internal error, cannot detect server address
- 1.1.176. Unknown protocol type (EPSV)
- 1.1.177. Error preparing data connection to the server (EPSV)
- 1.1.178. Invalid parameters to the PORT command
- 1.1.179. Connection mode not supported
- 1.1.180. Error preparing client-side data connection (PORT-<;PASV)
- 1.1.181. Error parsing the server answer to the PASV command (PORT-<;PASV)
- 1.1.182. Error preparing client-side data connection (PORT)
- 1.1.183. Error parsing the server answer to the PORT command
- 1.1.184. Connection mode not supported
- 1.1.185. Error preparing client-side data connection listener (PASV)
- 1.1.186. Error preparing client-side data connection listener (PASV)
- 1.1.187. Error preparing client-side data connection listener (PASV-<;PORT)
- 1.1.188. Error preparing client-side data connection listener (PASV-<;PORT)
- 1.1.189. Error parsing the server answer to the PORT command (PASV-<;PORT)
- 1.1.190. Missing parameter (EPRT)
- 1.1.191. Bad parameter (EPRT)
- 1.1.192. Bad port parameter (EPRT)
- 1.1.193. Unknown protocol method (EPRT)
- 1.1.194. Bad host address (EPRT)
- 1.1.195. Connection mode not supported
- 1.1.196. Error preparing client connect (EPRT)
- 1.1.197. Bad server answer (EPRT)
- 1.1.198. Error preparing client connect (EPRT)
- 1.1.199. Connection mode not supported
- 1.1.200. Error preparing client listen (EPSV)
- 1.1.201. Error preparing client listen (EPSV)
- 1.1.202. Error preparing client listen (EPSV)
- 1.1.203. Error preparing client listen (EPSV)
- 1.1.204. Bad server answer (EPSV)
- 1.1.205. Error parsing command (ALLO)
- 1.1.206. Invalid stacking tuple returned by policy
- 1.1.207. Invalid stacking type
- 1.1.208. Invalid request, data transfer failed
- 1.1.209. Data transfer failed
- 1.1.210. Stacked proxy decision
- 1.1.211. Stacked proxy accepted data
- 1.1.212. Policy does not contain this request, using hard-coded default
- 1.1.213. Policy type invalid
- 1.1.214. Cannot parse policy line
- 1.1.215. Error in policy calling
- 1.1.216. Can't parsing return code
- 1.1.217. Policy does not contain this response, using hard-coded default
- 1.1.218. Answer type invalid
- 1.1.219. Bad policy line
- 1.1.220. Error in policy calling
- 1.1.221. Return code invalid from policy function
- 1.1.222. Policy does not contain this feature, dropping
- 1.1.223. Policy value invalid
- 1.1.224. Internal error, error code out of range
- 1.1.225. An error occurred, would serve error file, but silent mode is enabled
- 1.1.226. An error occurred, serving error file
- 1.1.227. Error writing stream, stream is NULL
- 1.1.228. Error writing stream
- 1.1.229. Only Basic authentication is supported
- 1.1.230. Invalid base64 encoded username:password pair
- 1.1.231. No colon is found in the decoded username:password pair
- 1.1.232. Invalid HTTP request received
- 1.1.233. Found category match for URL
- 1.1.234. CONNECT method without version specification
- 1.1.235. This request type is not permitted in transparent mode
- 1.1.236. No host header in transparent request, 'unknown' is used instead
- 1.1.237. 'Host:' header is required, and HTTP/0.9 can't transfer headers
- 1.1.238. No 'Host:' header in request, and policy requires this
- 1.1.239. Error parsing URL
- 1.1.240. Error parsing URL
- 1.1.241. Client attempted to use FTP over HTTP, which is currently disabled
- 1.1.242. Unsupported scheme in URL
- 1.1.243. Too long hostname in URL
- 1.1.244. Accounting
- 1.1.245. Invalid item in request hash
- 1.1.246. Error parsing HTTP_REQ_POLICY tuple in request hash
- 1.1.247. Error parsing HTTP_REQ_REJECT in request hash
- 1.1.248. Unknown request hash item
- 1.1.249. Policy requested to send custom response
- 1.1.250. Request not permitted by policy
- 1.1.251. Request not permitted by policy
- 1.1.252. Connecting to this port is prohibited by policy
- 1.1.253. Internal error initializing server stream
- 1.1.254. Error in HTTP/0.9 compatibility code, line buffer full
- 1.1.255. Server falled back to HTTP/0.9 which is prohibited by policy
- 1.1.256. Invalid HTTP response heading
- 1.1.257. Error parsing response version
- 1.1.258. Unsupported protocol version
- 1.1.259. Invalid response hash item
- 1.1.260. Error parsing HTTP_RSP_POLICY in response hash
- 1.1.261. Error parsing HTTP_RSP_REJECT in response hash
- 1.1.262. Invalid response hash item
- 1.1.263. Response not permitted by policy
- 1.1.264. Missing port number in CONNECT request
- 1.1.265. Parent proxy refused our CONNECT request
- 1.1.266. Starting connect method
- 1.1.267. Internal error, connectMethod is expected to return a proxy instance
- 1.1.268. Fetching request and headers
- 1.1.269. processing request and headers
- 1.1.270. Maximum keep-alive request reached, setting connection mode to close
- 1.1.271. Filtering request and headers
- 1.1.272. Reprocessing filtered request
- 1.1.273. Sending request and headers, copying request data
- 1.1.274. Fetching response and headers
- 1.1.275. Processing response and headers
- 1.1.276. Filtering response and headers
- 1.1.277. Copying response and headers, copying response data
- 1.1.278. Internal error, invalid server_protocol
- 1.1.279. exiting keep-alive loop
- 1.1.280. Chunk length line too long
- 1.1.281. Invalid chunk length
- 1.1.282. Invalid chunk length
- 1.1.283. Chunk too large
- 1.1.284. Unexpected EOF while dechunking stream
- 1.1.285. Chunk footer is not an empty line
- 1.1.286. Stacked proxy sent a content-length hint, using it
- 1.1.287. Invalid stacking tuple returned by policy
- 1.1.288. Invalid stacking type
- 1.1.289. The header 'Content-Length' was present, but is not a number
- 1.1.290. Invalid request, data transfer failed
- 1.1.291. Data transfer failed
- 1.1.292. Stacked proxy decision
- 1.1.293. Stacked proxy accepted data
- 1.1.294. Invalid FTP response, line too short
- 1.1.295. Invalid FTP response, response code not numeric
- 1.1.296. Invalid FTP response, continuation line contains different status code
- 1.1.297. FTP server returned an unhandled status code for the login request
- 1.1.298. Error logging in
- 1.1.299. Error in FTP greeting, expecting 220
- 1.1.300. Error changing directory on server
- 1.1.301. Error changing directory on server
- 1.1.302. Error changing directory on server
- 1.1.303. Error sending RETR or LIST command to FTP server
- 1.1.304. Error establishing data connection to FTP server
- 1.1.305. Error reading data channel confirmation from FTP server
- 1.1.306. Error reading 226 from FTP server
- 1.1.307. Invalid HTTP_HDR_CHANGE_NAME rule in header processing
- 1.1.308. Invalid HTTP_HDR_CHANGE_VALUE rule in header processing
- 1.1.309. Invalid HTTP_HDR_CHANGE_BOTH rule in header processing
- 1.1.310. Invalid value in header action tuple
- 1.1.311. Error reading from peer while fetching headers
- 1.1.312. First header starts with white space
- 1.1.313. Invalid HTTP header
- 1.1.314. Too many header lines
- 1.1.315. Request method empty, or too long
- 1.1.316. URL missing, or too long
- 1.1.317. Protocol version missing, or too long
- 1.1.318. Request details
- 1.1.319. Invalid HTTP status line
- 1.1.320. Response version empty or too long
- 1.1.321. Response code empty or too long
- 1.1.322. Response details
- 1.1.323. Unknown protocol version
- 1.1.324. Unknown protocol version
- 1.1.325. Invalid return value of packetStats(), integer required
- 1.1.326. packetStats() requested to abort session
- 1.1.327. Response line too long
- 1.1.328. Response status is invalid
- 1.1.329. Response fetched with parameter
- 1.1.330. Response fetched
- 1.1.331. Data transfer failed
- 1.1.332. Request line too long
- 1.1.333. Request fetched with parameter
- 1.1.334. Request fetched
- 1.1.335. Unknown request command
- 1.1.336. Request command not allowed in this state
- 1.1.337. Dropping request parameter, no parameter allowed
- 1.1.338. The required numerical parameter of the request is missing
- 1.1.339. The numerical parameter of the request is not in the given range
- 1.1.340. The numerical parameter of the request is negative
- 1.1.341. The numerical parameter of the request is zero
- 1.1.342. The numerical parameter of the request contains junk after the number
- 1.1.343. The first numerical parameter of the request is not in the given range
- 1.1.344. The first numerical parameter of the request is negative
- 1.1.345. Only one numerical argument in request
- 1.1.346. The second numerical parameter of the request is not in the given range
- 1.1.347. The second numerical parameter of the request is a negative number
- 1.1.348. The numerical parameter of the request contain junk after the number
- 1.1.349. Username is too long
- 1.1.350. Password is too long
- 1.1.351. The username parameter is too long or the digest parameter is missing
- 1.1.352. Error parsing the MD5 digest
- 1.1.353. The required numerical parameter of the response is missing
- 1.1.354. The numerical parameter of the response is not in the given range
- 1.1.355. The numerical parameter of the response is a negative number
- 1.1.356. The numerical parameter of the response contains junk after the number
- 1.1.357. The numerical parameter of the response is not in the given range
- 1.1.358. The required numerical parameter of the response is missing
- 1.1.359. The numerical parameter of the response is a negative number
- 1.1.360. The second numerical parameter of the response is not in the given range
- 1.1.361. The required second numerical parameter of the response is missing
- 1.1.362. The second numerical parameter of the response is a negative number
- 1.1.363. The second numerical parameter of the response contains junk after the number
- 1.1.364. Stacked proxy rejected contents
- 1.1.365. Policy does not contain this request, using hard-coded default
- 1.1.366. Policy type is invalid
- 1.1.367. Cannot parse policy line
- 1.1.368. Error in policy call
- 1.1.369. Cannot parse the return code
- 1.1.370. Policy does not contain this request, using hard-coded default
- 1.1.371. Policy type is invalid
- 1.1.372. Cannot parse policy line
- 1.1.373. Error in policy call
- 1.1.374. Cannot parse return code
- 1.1.375. Stack policy type is invalid
- 1.1.376. Cannot parse stack policy line
- 1.1.377. Cannot parse stack policy line
- 1.1.378. Error in policy call
- 1.1.379. Cannot parse return code
- 1.1.380. Invalid command verb in request
- 1.1.381. Request parsed
- 1.1.382. Fetching request
- 1.1.383. Request line too long
- 1.1.384. Processing request
- 1.1.385. Command not permitted in this state
- 1.1.386. Unknown command
- 1.1.387. Copying request to server
- 1.1.388. Error sending request
- 1.1.389. Fetching authentication request
- 1.1.390. Auth request line too long
- 1.1.391. Copying authentication request to server
- 1.1.392. Error sending authentication request
- 1.1.393. SMTP reply contains non-numeric characters
- 1.1.394. Invalid continuation character
- 1.1.395. Fetching response
- 1.1.396. Response line too long
- 1.1.397. Invalid SMTP reply, reply code changed
- 1.1.398. Response parsed
- 1.1.399. Processing response
- 1.1.400. Copying response to client
- 1.1.401. Error sending SMTP reply
- 1.1.402. Invalid policy ignored, allowing 250 response to NOOP is required
- 1.1.403. Invalid policy ignored, allowing 354 response to DATA is required
- 1.1.404. Invalid contents
- 1.1.405. Error occurred while scanning contents
- 1.1.406. Rejecting empty message
- 1.1.407. Error sending RSET to the server
- 1.1.408. Exiting SMTP loop
- 1.1.409. Error parsing local part
- 1.1.410. Local part does not end in '@'
- 1.1.411. Invalid domain name in path
- 1.1.412. Path does not start with '>;'
- 1.1.413. Invalid source route information
- 1.1.414. Invalid address information
- 1.1.415. Path does not begin with '>;' but ends with '<;'
- 1.1.416. Path begins with '>;' but does not end with '<;'
- 1.1.417. Invalid SIZE extension in the MAIL command
- 1.1.418. Invalid BODY extension in the MAIL command
- 1.1.419. Invalid AUTH sender, not an xtext
- 1.1.420. Invalid extension in the MAIL command
- 1.1.421. Invalid request policy type
- 1.1.422. Error in request policy
- 1.1.423. Error in request policy
- 1.1.424. The verdict returned by the policy is not an int
- 1.1.425. Invalid response policy
- 1.1.426. Error in response policy
- 1.1.427. Error in response policy
- 1.1.428. The verdict returned by the policy is not an int
- 1.1.429. Buffer overflow during protocol decoding, aborting session
- 1.1.430. Internal error, not enough literals
- 1.1.431. Internal error, too many literals
- 1.1.432. Error while writing policy response
- 1.1.433. Error while writing policy response
- 1.1.434. Failed to parse command
- 1.1.435. Error writing to client
- 1.1.436. Reconstructed request
- 1.1.437. Illegal tag
- 1.1.438. Duplicate tag
- 1.1.439. Command not allowed in this state
- 1.1.440. Error parsing command
- 1.1.441. Request denied by policy
- 1.1.442. Dropping request
- 1.1.443. Policy responds to client
- 1.1.444. Aborting connection due to request
- 1.1.445. Too many pending requests
- 1.1.446. Error writing to server
- 1.1.447. Stray continuation response
- 1.1.448. Error writing to server
- 1.1.449. Error writing to server
- 1.1.450. Error writing to server
- 1.1.451. Server returned untagged line during authentication exchange, dropping it
- 1.1.452. Aborting connection due to a response
- 1.1.453. Dropping response
- 1.1.454. Invalid response
- 1.1.455. Error writing to client
- 1.1.456. Response arrived for unknown request
- 1.1.457. Aborting connection due to a response
- 1.1.458. Dropping response
- 1.1.459. Invalid response
- 1.1.460. Error writing to client
- 1.1.461. Complete response arrived
- 1.1.462. Reconstructed response
- 1.1.463. Reading literal
- 1.1.464. No free literal space
- 1.1.465. Illegal character
- 1.1.466. Illegal literal length form
- 1.1.467. Literal length attribute not closed
- 1.1.468. Stacked proxy rejected contents
- 1.1.469. Policy type is invalid
- 1.1.470. Cannot parse stack policy line
- 1.1.471. Cannot parse stack policy line
- 1.1.472. Error in policy call
- 1.1.473. Cannot parse return code
- 1.1.474. Response count for the request reached limit, drop packets
- 1.1.475. Response count for request reached limit, aborting connection
- 1.1.476. Invalid value for response_overrun_action, falling back to LDAP_RSP_DROP
- 1.1.477. Policy nesting do deep
- 1.1.478. Policy type invalid
- 1.1.479. Cannot parse policy line
- 1.1.480. Cannot parse policy line
- 1.1.481. Cannot parse policy line
- 1.1.482. Cannot parse policy line
- 1.1.483. Error in policy calling
- 1.1.484. Policy does not contain this header, using hard-coded default
- 1.1.485. Policy does not contain this mime-type, using hard-coded default
- 1.1.486. Answer type invalid
- 1.1.487. Bad policy line
- 1.1.488. Error in policy calling
- 1.1.489. Return code invalid from policy function
- 1.1.490. Policy does not contain this error, using hard-coded default
- 1.1.491. Cannot parse policy line
- 1.1.492. Error in policy calling
- 1.1.493. Error parsing return code
- 1.1.494. Stack policy type is invalid
- 1.1.495. Cannot parse stack policy line
- 1.1.496. Error in policy call
- 1.1.497. Cannot parse return code
- 1.1.498. Stacked proxy rejected contents
- 1.1.499. Invalid stacking type
- 1.1.500. Invalid stacking tuple returned by policy
- 1.1.501. Evaluating BACL rule
- 1.1.502. BACL result
- 1.1.503. Cache over shift-threshold, shifting
- 1.1.504. Server connection failure
- 1.1.505. Server connection established
- 1.1.506. Server connection failure, no destination
- 1.1.507. All destinations are down, clearing cache and trying again
- 1.1.508. Destination is down, skipping
- 1.1.509. Destination is down, keeping state
- 1.1.510. Side stacking failed, socketPair failed
- 1.1.511. Side-stacking proxy instance
- 1.1.512. Side-stacking failed
- 1.1.513. Unable to determine service, KZorp service lookup failed
- 1.1.514. No applicable service found for this client zone (cached)
- 1.1.515. No applicable service found for this client zone
- 1.1.516. No applicable service found for this client & server zone (cached)
- 1.1.517. No applicable service found for this client & server zone
- 1.1.518. Matching regexp found
- 1.1.519. Error opening match file
- 1.1.520. Error opening ignore file
- 1.1.521. Cached recipient match found
- 1.1.522. Recipient validity not cached, trying the direct way
- 1.1.523. SMTP sender was rejected, unable to verify user existence
- 1.1.524. Server accepted recipient
- 1.1.525. Server rejected recipient
- 1.1.526. SMTP error during recipient validity checking
- 1.1.527. Before NAT mapping
- 1.1.528. After NAT mapping
- 1.1.529. Proxy ending
- 1.1.530. Proxy destroy
- 1.1.531. Error while stacking child proxy
- 1.1.532. Stacking custom child
- 1.1.533. User authentication successful
- 1.1.534. Starting proxy instance
- 1.1.535. Ending proxy instance
- 1.1.536. Outbound connection not permitted
- 1.1.537. Error resolving hostname
- 1.1.538. Instance definition not found in policy
- 1.1.539. Error downloading KZorp configuration, Python traceback follows
- 1.1.540. Deinitialization requested for instance
- 1.1.541. Cleaning up instance
- 1.1.542. Error flushing KZorp configuration
- 1.1.543. Client foreign port below 1024
- 1.1.544. Server foreign port below 1024 in passive mode
- 1.1.545. Server foreign port is not good in active mode
- 1.1.546. Unknown side when calling bounceCheck
- 1.1.547. Http accounting
- 1.1.548. Request administratively prohibited
- 1.1.549. Sender address administratively prohibited
- 1.1.550. Sender check successful
- 1.1.551. Forbidden percent found in address local-part
- 1.1.552. Forbidden exclamation mark found in address local-part
- 1.1.553. Relaying denied
- 1.1.554. Relay check successful
- 1.1.555. Recipient address administratively prohibited
- 1.1.556. Recipient check successful
- 1.1.557. Relay check, checking client_zone
- 1.1.558. Relay check, checking mail domain
- 1.1.559. Signal received, stackdump follows
- 1.1.560. Invalid license file
- 1.1.561. Error initializing Python policy engine
- 2. Management Server log messages
- 2.1.
- 2.1.1. Module successfully loaded
- 2.1.2. Module loading failed
- 2.1.3. Module loading failed
- 2.1.4. Module loading failed
- 2.1.5. Module loading failed
- 2.1.6. Cannot open plugin directory
- 2.1.7. Module loading failed
- 2.1.8. Cannot open plugin directory
- 2.1.9. Signal received, stackdump follows
- 2.1.10. SIGHUP received, reloading config
- 3. MS Transfer Agent log messages
- 4. Authentication Server log messages
- 5. Authentication Agent log messages
- 6. Content Filtering log messages
- A. Creative Commons Attribution Non-commercial No Derivatives (by-nc-nd) License
List of Procedures
Published on June 04, 2020
© 2007-2019 BalaSys
Send your comments to support@balasys.hu
