Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 2427  |
|  Jay Harris to Nicholas Boel  |
|  Re: Another change  |
|  17 Mar 24 12:58:28  |
 MSGID: 1:229/664 22545ed1 REPLY: 1:154/10 65f6f8e6 TZUTC: -0400 TID: hpt/lnx 1.9 2024-03-02 On 17 Mar 2024, Nicholas Boel said the following... NB> Also, in the paragraph above it tells you "*" supercedes the rest of what NB> follows, so *127.0.0.1 is actually just "*", and with that said... Ah, I missed that part. No wonder it works! :) NB> I don't think "*" should be a default example in any case, since that NB> could potentially cause problems. so I think the '127.0.0.1' is and NB> always has been just a placeholder for people to change. Before I just had 127.0.0.1 as I only want to allow connections from nginx running on the same VPS. What would I put in smapinntpd.allow if I wanted to restrict access to a single IPv4 address? I don't have port 5000 exposed to the public internet, so it's not really much of a concern, more of a belt & suspenders approach. Jay ... I have an inferiority complex but it's not a very good one --- Mystic BBS v1.12 A49 2023/04/30 (Linux/64) * Origin: Northern Realms (1:229/664) SEEN-BY: 15/0 90/1 105/81 106/201 128/260 135/225 153/7715 218/700 SEEN-BY: 226/30 227/114 229/110 112 113 206 307 317 426 428 470 664 SEEN-BY: 229/700 266/512 282/1038 291/111 320/219 322/757 342/200 SEEN-BY: 396/45 460/58 633/280 712/848 PATH: 229/664 426 |
[ << oldest | < older | list | newer > | newest >> ]