9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: santucco@gmail.com
To: plan9port-dev@googlegroups.com
Cc: 9fans@9fans.net
Subject: "Re: [go-nuts] [ANN] amail - a new mail client for Acme"
Date: Sat, 18 Jan 2014 22:50:12 +0400	[thread overview]
Message-ID: <4b93b918f73a2b8d770d668bf4b5df09@YOURDOMAIN.DOM> (raw)

Hi,

I have made a support of TLS in p9p's upas/smtp and remade the support of TLS in p9p's upas/nfs (stunnel is not needed anymore). 
The sources are avaliable in my working copy of plan9port: https://bitbucket.org/santucco/plan9port
I have made changes in amail to fix some problems with sending of mails and to add signatures support.

Also I have changes of p9p's upas/nfs to support monitoring of all mailboxes, not only INBOX. The code is working, but it is not very elegant and I hope to find better solution of the problem. But if someone is interesting I can commit changes in the same place.

If you can see this message then the TLS support of upas/smtp is working - I have sent the message via amail :-) 


> Hi,
> 
> I glad there are potential users of amail except me :-).
> 
> (1) Actually, 'go get bitbucket.org/santucco/amail' should be enough to
> install amail. Other way is to run 'make' in amail's directory.
> Some problems can be with my clone of goplan9 (
> http://code.google.com/r/santucco-goplan9). I don't know why 'go get' can't
> work with this package, so it has to be cloned manually.
> (2) Amail sends messages exact the same way as Mail does. So it works out
> of the box if you can send messages from Mail.
> Yes, p9p's smtp doesn't support tls yet. I tested this code on a non-tls
> smtp gateway and haven't yet tuned my system to send messages to tls one.
> But I believe it can be made via $PLAN9/mail/lib/ scripts.
> 
> Best regards,
>   santucco
> 
> On Mon, Oct 28, 2013 at 2:19 PM, Kostarev Ilya <uvelichitel@gmail.com>wrote:
> 
> > Hi Alexander. Thanks. 'amail' works on p9p OSX 10.8. Some observations.
> > (1) It was not intuitive to compile and there are no instructions in
> > Readme. (2) p9p smtp dose not care about 'tls', so I personally use
> > 'stunnel' to send to, say imap.gmail.com. What machinery you use to send
> > when 'tls' required? Dose it work out of the box?
> > Once more thanks, since 'acme' is my editor of choice I'm very appreciate
> > all improvements in this area.
> >      Uvelichitel.
> >
> >
> > On Mon, Oct 28, 2013 at 10:41 AM, Alexander Sychev <santucco@gmail.com>wrote:
> >
> >> Hi,
> >>
> >> Amail is a new mail client for Acme
> >>
> >> go get bitbucket.org/santucco/amail
> >>
> >> It is "literate programmed"  in pure Go.
> >> It supports a navigation through mailboxes, threads,  switching between
> >> unread/all messages, a search in mailboxes, composing and sending new
> >> messages.
> >> Html-messages can be sent to a web-browser. Threads can be navigated from
> >> messages.
> >> A full description can be found in a README file.
> >> If you have the original Mail is working, Amail will work too.
> >>
> >> For the moment it is working with p9p version of Acme.
> >>
> >> --
> >> Best regards,
> >>   santucco
> >>
> >> --
> >> You received this message because you are subscribed to the Google Groups
> >> "golang-nuts" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to golang-nuts+unsubscribe@googlegroups.com.
> >> For more options, visit https://groups.google.com/groups/opt_out.
> >>
> >
> >
> 
> 
> -- 
> Best regards,
>   santucco
> 

--
Best regards,
  santucco


-- 

--- 
You received this message because you are subscribed to the Google Groups "plan9port-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plan9port-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


                 reply	other threads:[~2014-01-18 18:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4b93b918f73a2b8d770d668bf4b5df09@YOURDOMAIN.DOM \
    --to=santucco@gmail.com \
    --cc=9fans@9fans.net \
    --cc=plan9port-dev@googlegroups.com \
    /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).