16 Apr
2019
16 Apr
'19
6 p.m.
Everyone happy with this? Any comments?
It would be nice if the mail had some info about what a gateway is and why you (don't)
want it,
e.g. with a pointer to the wiki page.
I have found that some people add a gateway entry because they think this is some form of
registration
of their existing (not IPIP mesh) router e.g. connected via radio or via one of the other
VPN types
we support. They think it would be useful to be registered in some list. That is how the
problematic
gateway came into existance, and there are several others like that registered in the
Netherlands,
that did not become problematic only because they had no subnets.
When being listed is what they actually want, of course they should not register a
gateway. But it is what
they do, partly because there is a lack of higher-level explanation of concepts. And
after receiving
that mail message they probably still don't understand what they are doing wrong.
Maybe a pointer to HamnetDB could be useful. Registering there is probably what they
want.
Rob
16 Apr
16 Apr
6:29 p.m.
New subject: RIP problems?
If you want to suggest some text I can add it to the template…
Thanks,
Chris
On 16 Apr 2019, at 18:00, Rob Janssen
<pe1chl(a)amsat.org> wrote:
Everyone happy with this? Any comments?
It would be nice if the mail had some info about what a gateway is and why you
(don't) want it,
e.g. with a pointer to the wiki page.
I have found that some people add a gateway entry because they think this is some form of
registration
of their existing (not IPIP mesh) router e.g. connected via radio or via one of the other
VPN types
we support. They think it would be useful to be registered in some list. That is how
the problematic
gateway came into existance, and there are several others like that registered in the
Netherlands,
that did not become problematic only because they had no subnets.
When being listed is what they actually want, of course they should not register a
gateway. But it is what
they do, partly because there is a lack of higher-level explanation of concepts. And
after receiving
that mail message they probably still don't understand what they are doing wrong.
Maybe a pointer to HamnetDB could be useful. Registering there is probably what they
want.
Rob
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net 
18 Apr
18 Apr
9:35 a.m.
New subject: RIP problems?
It think there is a small issue on the mailing part to the coordinator.
The mail system sends the message as originating from the sender. This is actually wrong
and will lead to delivery failures like:
<marius(a)yo2loj.ro>ro>: host mail.yo2loj.ro[89.33.44.100] said: 554 5.7.1
<marius(a)yo2loj.ro>ro>: Sender address rejected: Sending from this domain
outside the internal network is prohibited! (in reply to MAIL FROM command)
So please use 'MAIL FROM' with something like mailer(a)portal.ampr.org (preferably
with a valid DNS and MX entry) and use the originator mail in the 'From:' field
(this will make that address show as the originator).
Marius, YO2LOJ
11:12 a.m.
New subject: RIP problems?
Marius,
Even that isn't enough; if the Author ('From:') and Sender (SMTP
'Mail From') don't match, the resulting mail will wind up often
being filed as 'spam' by Gmail and others. I have this problem
when sending mail as "From: brian(a)ampr.org" quite often.
Google says it's my fault; I say Google has its collective head up
its ass in marking a valid email as spam. Their official word is
"Don't act like the bad guys" and you won't have problems. Never
mind that it's 100% RFC-compliant, they say it's bad guy behaviour.
- Brian
On Thu, Apr 18, 2019 at 08:35:04AM +0000, marius(a)yo2loj.ro wrote:
It think there is a small issue on the mailing part to
the coordinator.
The mail system sends the message as originating from the sender. This is actually wrong
and will lead to delivery failures like:
<marius(a)yo2loj.ro>ro>: host mail.yo2loj.ro[89.33.44.100] said: 554 5.7.1
<marius(a)yo2loj.ro>ro>: Sender address rejected: Sending from this domain
outside the internal network is prohibited! (in reply to MAIL FROM command)
So please use 'MAIL FROM' with something like mailer(a)portal.ampr.org (preferably
with a valid DNS and MX entry) and use the originator mail in the 'From:' field
(this will make that address show as the originator).
Marius, YO2LOJ
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
12:44 p.m.
New subject: RIP problems?
Yeah, sorry, that was a bug on my part. It has now been fixed. Emails will originate from
postmaster(a)ampr.org <mailto:postmaster@ampr.org>
Chris
On 18 Apr 2019, at 09:35, marius(a)yo2loj.ro wrote:
It think there is a small issue on the mailing part to the coordinator.
The mail system sends the message as originating from the sender. This is actually wrong
and will lead to delivery failures like:
<marius(a)yo2loj.ro>ro>: host mail.yo2loj.ro[89.33.44.100] said: 554 5.7.1
<marius(a)yo2loj.ro>ro>: Sender address rejected: Sending from this domain
outside the internal network is prohibited! (in reply to MAIL FROM command)
So please use 'MAIL FROM' with something like mailer(a)portal.ampr.org (preferably
with a valid DNS and MX entry) and use the originator mail in the 'From:' field
(this will make that address show as the originator).
Marius, YO2LOJ
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
1846
days inactive
1848
days old
5 comments
5 participants
participants (5)
-
Bill Vodall -
Brian Kantor -
G1FEF -
marius＠yo2loj.ro -
Rob Janssen