Remote peer will be unable connect to my peer as I have no external IP address. For some reason I won't use mail as channel feed. Any idea how
to peer under such conditions?
Hi.
Remote peer will be unable connect to my peer as I have no external
IP address. For some reason I won't use mail as channel feed. Any
idea how to peer under such conditions?
Remote peer will be unable connect to my peer as I have no
external IP address. For some reason I won't use mail as channel
feed. Any idea how to peer under such conditions?
On 3/26/22 10:37 AM, Miner wrote:
Hi.
Hi Miner,
Remote peer will be unable connect to my peer as I have no
external IP address. For some reason I won't use mail as
channel feed. Any idea how to peer under such conditions?
As Russ suggested, UUCP would be an option.
Though I'm not sure what the best method would be to get UUCP
bag files attached to email and off to you. I suppose there's
some room for automation to attach the UUCP bag files and send
them.
Do you /need/ to use email (SMTP) as the transport? Or can you
connect out from -- I presume -- behind NAT to a server and
pull data?
There's also something like a Tor hidden service to allow peers
that support Tor to connect to you. Or other similar VPNs.
I'm curious and like the thought experiment about how to make
this work.
I'd be happy to peer with you, be it UUCP bag files, UUCP pull
initiated from your end, or something else yet to be
determined. -- Please send me an email directly so we can
discuss details.
On 3/26/22 10:37 AM, Miner wrote:
Hi.
Hi Miner,
Remote peer will be unable connect to my peer as I have no external
IP address. For some reason I won't use mail as channel feed. Any
idea how to peer under such conditions?
As Russ suggested, UUCP would be an option.
Though I'm not sure what the best method would be to get UUCP bag files >attached to email and off to you. I suppose there's some room for
automation to attach the UUCP bag files and send them.
Do you /need/ to use email (SMTP) as the transport? Or can you connect
out from -- I presume -- behind NAT to a server and pull data?
There's also something like a Tor hidden service to allow peers that
support Tor to connect to you. Or other similar VPNs.
I'm curious and like the thought experiment about how to make this work.
I'd be happy to peer with you, be it UUCP bag files, UUCP pull initiated
from your end, or something else yet to be determined. -- Please send
me an email directly so we can discuss details.
--
Grant. . . .
unix || die
Miner <john@doe.invalid> writes:
Remote peer will be unable connect to my peer as I have no
external IP address. For some reason I won't use mail as channel
feed. Any idea how to peer under such conditions?
Rent a VPS for a few dollars a month and peer from that instead.
I would like to avoid using email at all for this purpose. Most
email services tend to impose unacceptable conditions and
restrictions.
It seems to me that Tox is more preferred as a channel feed
solution than email. Look on FIFO based Tox client "ratox" https://github.com/pranomostro/ratox
Yes, I can connect to remote server.
Good solution. Thanks to my friend you may read my message. We peer
over I2P network.
Ok. Do you have valid GnuPG key? 9864F8EC1A79AAA0 expired since
2018-01-01.
I'd be happy to peer with you, be it UUCP bag files, UUCP pull
initiated from your end, or something else yet to be
determined. -- Please send me an email directly so we can
discuss details.
A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:
gtaylor@tnetconsulting.net
host tncsrv06.tnetconsulting.net [2600:3c00:e000:1e9::8849]
SMTP error from remote mail server after RCPT TO:<gtaylor@tnetconsulting.net>:
550 5.7.1 <gtaylor@tnetconsulting.net>... Fix reverse DNS for IPv6:2a02:180:2:92:3:4:5:6
On 3/31/22 5:05 AM, Miner wrote:
host tncsrv06.tnetconsulting.net
[2600:3c00:e000:1e9::8849]
SMTP error from remote mail server after RCPT
The last five words of the message tell you what you need to do.
Fix reverse DNS for IPv6:2a02:180:2:92:3:4:5:6
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 67:43:55 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,356,426 |