From: Philippe LeCavalier <support@plecavalier.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] background or queue msg sending
Date: Thu, 17 Mar 2011 21:34:54 -0400 [thread overview]
Message-ID: <1300411900-sup-8374@plc.intranet.plecavalier.com> (raw)
In-Reply-To: <1300403212-sup-7826@plc.intranet.plecavalier.com>
Excerpts from Philippe LeCavalier's message of Thu Mar 17 19:08:41 -0400 2011:
> Excerpts from Sascha Silbe's message of Thu Mar 17 18:32:19 -0400 2011:
> > Excerpts from Philippe LeCavalier's message of Thu Mar 17 21:10:36 +0100 2011:
> >
> > > But some client have slower DSL links and when I'm at home -I'm in the
> > > country- I've got a 1.5Mps wireless and Sup makes me wait 5 to 10
> > > seconds while msmtp terminates. That pause drives me nuts. I want sup to
> > > leave that buffer in the background. Like what about someone on dial-up
> > > or a very slow DSL. It must be even longer.
> >
> > Give nullmailer a try. It will queue your message and deliver it in the
> > background. No need to hack sup and keep it running until the message
> > has been delivered.
> >
> > On my laptops I've integrated nullmailer with NetworkManager so I can
> > write mails while on the bus and have them delivered as soon as I enter
> > the reach of a wifi network that I have access to. A custom ssh based
> > transport tunnels the mails to my smarthost (the university network
> > blocks the SMTP ports).
> >
> > Sascha
> >
> That sounds just about perfect. These kinds of conversations always
> leave me wondering why I haven't heard of said program before, in this
> case it's nullmailer. I guess I should just be happy I'm learning
> something new every day! Thanks Sascha!
Sascha, would you be so kind as to post(or send me) your remotes file if
you use TLS? I can seem to get nullmailer working with my host. It's
timing out on the cert check since it's not a valid cert. In msmtp I
used to use:
tls on tls_certcheck off tls_starttls off But I can't seem to find
anything related to that for nullmailer.
--
Thanks,
Phil
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2011-03-18 1:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 14:17 Philippe LeCavalier
2011-03-17 15:32 ` Bruno d'Arcangeli
2011-03-17 19:15 ` Philippe LeCavalier
2011-03-17 19:55 ` Ben Walton
2011-03-17 20:16 ` Kevin Riggle
2011-03-17 23:10 ` Philippe LeCavalier
2011-03-17 19:54 ` Tero Tilus
2011-03-17 20:10 ` Philippe LeCavalier
2011-03-17 22:32 ` Sascha Silbe
2011-03-17 23:08 ` Philippe LeCavalier
2011-03-18 1:34 ` Philippe LeCavalier [this message]
2011-03-18 0:53 ` Tero Tilus
2011-03-18 1:31 ` Philippe LeCavalier
2011-03-17 22:42 ` Sean Escriva
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=1300411900-sup-8374@plc.intranet.plecavalier.com \
--to=support@plecavalier.com \
--cc=sup-talk@rubyforge.org \
/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