9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Quintile <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9 Atom - installation troubles
Date: Sat,  6 Dec 2014 10:28:48 +0000	[thread overview]
Message-ID: <E35BA905-7569-4A29-9004-3F61F50D81EA@quintile.net> (raw)
In-Reply-To: <ba67805906ab3b43ba3e51dc84ebe04b@proxima.alt.za>

by submission do you jest mean a different port?

did you try adding a port to the SMTP attribute in your /lib/nab/local

smtp=host!987

-Steve





On 6 Dec 2014, at 09:09, lucio@proxima.alt.za wrote:

>> I can't be certain but looks like proxima.alt.za delegates
>> actual email delivery to turo-smtp.net.
> 
> There's a transparent proxy just the other side of my long-distance
> wi-fi link, I'm not sure why my ISP feels they have to pay a third
> party to interfere with email, but I think there may be a national
> intelligence issue involved: our government has mooted digital
> communication interception regulations for a while, but I haven't
> followed the details.  I know whom to ask, though.
> 
> In the meantime, I note that the transparent interception does not
> apply to the "submission" TCP port, port 587, so I think I'll hack
> smtp to use that instead.  Right now, I'm going to build a copy of
> smtp with a modified mxdial.c, but I wonder what a consensus here
> would be: an option to smpt that invokes a "submit" function that only
> differs from mxdial() in the use of the service argument, or a generic
> port number on smtp's command line with a more complex, but now common
> to both options, mxdial()?
> 
> Or maybe, as I'm doing now, a distinct "submit" command instead of
> "smtp"?
> 
> Lucio.
> 
> 
> -------------------------------------------------------------------------------------
> This email has been scanned by the MxScan Email Security System.
> -------------------------------------------------------------------------------------



  parent reply	other threads:[~2014-12-06 10:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-05 10:02 lucio
2014-12-05 14:20 ` erik quanstrom
2014-12-05 17:47   ` lucio
2014-12-06 19:02     ` erik quanstrom
2014-12-07  4:26       ` lucio
2014-12-07  5:15       ` lucio
2014-12-07  7:26         ` erik quanstrom
2014-12-07  7:33         ` erik quanstrom
2014-12-05 18:04   ` lucio
2014-12-05 18:15     ` lucio
2014-12-05 20:38       ` Wes Kussmaul
2014-12-05 21:23         ` Skip Tavakkolian
2014-12-06  4:43           ` lucio
2014-12-05 22:21       ` Bakul Shah
2014-12-06  4:57         ` lucio
2014-12-06 16:34           ` erik quanstrom
2014-12-06 18:12             ` lucio
2014-12-06 18:53               ` erik quanstrom
2014-12-06  5:06         ` lucio
2014-12-06  9:09         ` lucio
2014-12-06  9:27           ` Bakul Shah
2014-12-06 10:28           ` Quintile [this message]
2014-12-06 13:40             ` lucio
2014-12-06 16:29               ` erik quanstrom
2014-12-06 16:42                 ` Kurt H Maier
2014-12-06 17:47                   ` lucio
2014-12-06 13:43             ` lucio
2014-12-06 14:06               ` lucio
2014-12-06 14:30             ` lucio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E35BA905-7569-4A29-9004-3F61F50D81EA@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).