<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
Bob:<BR>
<BR>
This is also the way I have my station setup.<BR>
<BR>
My Linux uses POSTFIX as the MTA and all mail "for" and "from" my JNOS first gets routed there. <BR>
<BR>
POSTFIX can do a great job of all my filtering needs, plus POSTFIX can be configured to work with many other filter sources, such as blacklists.<BR>
<BR>
Plus, outgoing mail from jnos gets dumped into POSTFIX, then POSTFIX sends it on using current RFC standards so places like HOTMAIL wont reject it based on non-complient RFC's.<BR>
<BR>
But..... I don't believe Michaels (LINUX) box even uses an MTA. I (think ??) Michaels jnos only uses jnos as the MTA and nothing else.<BR>
<BR>
I could be wrong about that setup, but Michael will have to clarify that.<BR>
<BR>
Bill<BR>
KG6BAJ <BR>
<BR> <BR>
<DIV>
> Date: Tue, 6 Dec 2011 08:44:57 -0500<BR>> From: bobtenty@gmail.com<BR>> To: nos-bbs@tapr.org<BR>> Subject: Re: [nos-bbs] smtp gateway control<BR>> <BR>> Because the smtp server in jnos is not up to the standards anymore.<BR>> jnos isn't always talking to another jnos (or tnos) over an amprnet connection.<BR>> Some people receive all their mail in linux and process it there or whatever<BR>> mail server they are using. <BR>> <BR>> The behaviour I'm after is the same behaviour if your define a (smart) smtp gateway (relay)<BR>> in postfix or exim, etc.<BR>> <BR>> Bob VE3TOK<BR>> <BR>> <BR>> <BR>> On 06/12/2011 3:37 AM, Michael Fox - N6MEF wrote:<BR>> > Why would you "always" want it to use the gateway when it's faster and more<BR>> > efficient to send directly (when possible)? It puts an extra store and<BR>> > forward hop in the path for every message and creates a single point of<BR>> > failure.<BR>> > <BR>> > Regardless, if you still prefer that, then the syntax below would still<BR>> > work. The default behavior if a gateway is configured and there are no<BR>> > "smtp direct" commands configured should be so send everything to the<BR>> > gateway.<BR>> > <BR>> > M<BR>> > <BR>> > -----Original Message-----<BR>> > <BR>> > <BR>> > I also don't like the behaviour of jnos with the "smtp gateway x.x.x.x"<BR>> > setting.<BR>> > (I hate it)<BR>> > It should always deliver to the smtp gateway without fuss and at the first<BR>> > try.<BR>> > <BR>> > <BR>> > <BR>> > 73,<BR>> > <BR>> > Bob VE3TOK<BR>> > <BR>> > <BR>> > <BR>> > <BR>> > <BR>> > <BR>> > On 06/12/2011 12:34 AM, Michael Fox - N6MEF wrote:<BR>> >> We've configured an e-mail gateway to allow packet users to send to<BR>> >> Internet email addresses. But JNOS has no way to control when the<BR>> >> gateway is used. We really need a way to control when the smtp gateway<BR>> >> is used (and not used).<BR>> >><BR>> >> Background:<BR>> >><BR>> >> JNOS can talk SMTP just fine with other JNOS systems. But it evidently<BR>> >> does not adhere to the current protocol very well which makes it<BR>> >> problematic when talking with non-JNOS SMTP mailers. For example, I<BR>> >> get this message in the log ever time JNOS connects to a current SMTP<BR>> > mailer:<BR>> >><BR>> >> Dec 5 20:58:31 cpk postfix/smtpd[10138]: improper command pipelining<BR>> >> after HELO from w6xsc-4.ampr.org[44.4.50.4]<BR>> >><BR>> >> Another problem with the JNOS SMTP server is a complete lack of<BR>> >> security mechanisms, such as checks, filters, etc. which are part of<BR>> >> any typical internet mail gateway. This isn't a complaint, just a fact.<BR>> >><BR>> >> Scenario:<BR>> >><BR>> >> I'd like to allow JNOS to talk directly to any machine in my<BR>> >> domain.txt, and any machine with either a 44.x address or an ampr.org<BR>> > domain name.<BR>> >> Anything else should go to the smtp gateway for handling.<BR>> >><BR>> >> Problem:<BR>> >><BR>> >> The "smtp gateway" command is described in the manual as:<BR>> >><BR>> >> Displays or sets the host to be used as a "smart" mail relay. Any mail<BR>> >> sent to a host not in the domain.txt file or not found via a<BR>> >> nameserver query, will instead be sent to the gateway for forwarding.<BR>> >><BR>> >> The problem with this is that JNOS does a DNS query for any mail<BR>> >> destination that is not in domain.txt. We can turn off MX queries<BR>> >> (with smtp usemx no) but JNOS still performs an A record query. When<BR>> >> it receives the answer, it attempts to connect directly to the remote<BR>> > host.<BR>> >> With "smtp usemx yes" it will attempt to connect directly to the MX<BR>> >> for the remote host. So there's no way to control when JNOS uses the<BR>> >> smtp gateway. In fact, as long as DNS is configured, and you're<BR>> >> sending to a proper internet email address, JNOS will NEVER use the<BR>> >> gateway since it will always get an answer from the nameserver. That's<BR>> > just not right.<BR>> >><BR>> >> Workaround:<BR>> >><BR>> >> I currently have iptables set to disallow SMTP connections on the<BR>> >> JNOS-to-Linux tunnel that are from JNOS to anything other than the<BR>> >> SMTP gateway. This means that JNOS will try over and over, but will be<BR>> >> unsuccessful in contacting the remote host. It will then try to send<BR>> >> to the gateway.<BR>> >><BR>> >> However, this workaround has a problem. Since it relies on a<BR>> >> connection failure, it can end up being used unintentionally, such as<BR>> >> when the remote system is another JNOS system. If that remote system<BR>> >> is down temporarily, JNOS tries and fails to connect, so it ships it<BR>> >> to the gateway. The gateway then tries to deliver it via the internet<BR>> >> (out to the internet, back in via the UCSD gateway, etc.) which is not<BR>> >> allowed on many JNOS systems.<BR>> >><BR>> >> Solution:<BR>> >><BR>> >> What we really need is a way to tell JNOS when and when not to use the<BR>> >> "smtp gateway". I think the easiest approach would be to define when<BR>> >> JNOS should attempt a direct connect and then let the SMTP gateway<BR>> >> handle anything else. It seems that the best approach would be to<BR>> >> allow either IP address or domain name nomenclature. Here's one example:<BR>> >><BR>> >> smtp direct local # host is in domain.txt<BR>> >><BR>> >> smtp direct address 44.0.0.0/8<BR>> >><BR>> >> smtp direct domain ampr.org<BR>> >><BR>> >> Instead of "direct", something like "nogateway" could be used.<BR>> >><BR>> >> This basically says, if the host is in domain.txt or it has an address<BR>> >> of 44.x or it has a domain of ampr.org, then send it direct.<BR>> >> Otherwise, use the gateway.<BR>> >><BR>> >> Is this doable?<BR>> >><BR>> >> Michael<BR>> >><BR>> >><BR>> >><BR>> >> _______________________________________________<BR>> >> nos-bbs mailing list<BR>> >> nos-bbs@tapr.org<BR>> >> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs<BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > nos-bbs mailing list<BR>> > nos-bbs@tapr.org<BR>> > https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs<BR>> > <BR>> > <BR>> > _______________________________________________<BR>> > nos-bbs mailing list<BR>> > nos-bbs@tapr.org<BR>> > https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs<BR>> <BR>> <BR>> _______________________________________________<BR>> nos-bbs mailing list<BR>> nos-bbs@tapr.org<BR>> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs<BR></DIV> </div></body>
</html>