Hi Chris,Sorry about the delay. Was out of town for a few days.Yes, the userland in Mac is quite a bit different. It is based on the BSD userland rather than the GNU one. In the case of ping, the only difference from the commands you are using is that the "-w" option needs to be replaced by "-W" (uppercase). The rest of the options work fine and mean the same things as GNU ping.And yeah, I agree my particular requirement is nowhere close to mainstream. Does not make sense to add that to "msmtpq", but I just thought I'd put my script out there in case someone else shares my specific needs. :)As for running the queue on Mac, you *could* use launchd, but it won't be as clean a solution as using if-up.d. However, if there is interest in having this work on the Mac, I can have a go at using the KeepAlive/NetworkState properties of launchd.plist(5) to sorta simulate if-up.d.Also, in general, if you need help testing your changes on Mac, feel free to get in touch with me.And thanks for msmtpq! Though I'm not using it right now, it heavily influenced my design for msmtp-offline.Cheers,Venky.On 27 April 2015 at 02:56, cg <namtok@...135...> wrote:Hello Venky,
Am Chris, currently maintaining / developing msmtpq.
Yes, the connection tests have been fixed and, so far, no one here has
complained...
First, sorry, I didn't know about the differences with the Mac
platform 'ping', assuming that they run a GNU userland. I really know
nothing about the Mac platform; as a specialised case it would likely
be best for you to modify the parameters relevant 'ping' line(s)
yourself. However, please, then, send me your mods so that I can
incorporate them into the general msmtpq docs. (Thanks in advance.)
As to your new script - great! - thanks for it. I hope it's useful to
others. As to msmtpq for your case, I would have suggested that you
modify it for your specific needs (connection testing on a per server
basis) - but your new script is a better solution yet. My original
purpose in writing msmtpq was to make a simple utility function for
generalised use; your use is very specific; it would be a serious
development project to attempt to generalise msmtpq for many specific
cases.
Finally, as to running the queue, it can be done manually with
msmtp-queue -r . Under Debian(-based) systems one could investigate
inserting a simple script in a place like /etc/network/if-up.d (or
even /etc/ppp/if-up.d) to check the queue and 'run' (flush) it if
necessary (and desired). The script would contain 'msmtp-queue -r' and
run as the current user. I'm not sure where such a script would be
placed on RedHat(-based) systems, although it shouldn't be very
difficult to discover. On the Mac, sorry but I have no idea. (But
there must be such a facility available...) So thanks for this idea,
I'll explore it as a possible msmtpq enhancement. Any feedback from
the list as to this would be welcome...
Best,
Chris
> ------------------------------------------------------------------------------
On Sun 19.Apr'15 at 8:54:21 +0530, Venky TV wrote:
> Hi,
>
> I tried using msmtpq for offline use on my Mac, and found that the script
> has a couple of platform dependencies (ping command line options, for
> instance) and even with those fixed, has issues with connection tests which
> Allen mentioned here:
>
> http://sourceforge.net/p/msmtp/mailman/message/33502912/
>
> (Sounds like at least some of these have been fixed in the latest version
> though, but Homebrew on Mac has still not pulled in the latest code.)
>
> In any case, I also have a couple of other requirements:
>
> - I use msmtp with multiple accounts and while on VPN to my office network,
> and depending on where I am, I sometimes want my personal mail to get
> queued but my office mail to get sent out immediately, etc. The connection
> tests in msmtpq are all-or-nothing right now, while I need the queue
> manager to try connecting to the appropriate SMTP server before deciding
> whether to queue or send each email.
>
> - I need the queued mail to get flushed as soon as I get back online, and
> not stay in the queue (as seems to be the case with msmtpq currently) until
> I send another email.
>
> Wrote a replacement Ruby script which does these and a couple of other
> things. It also has some basic queue management features, though not as
> comprehensive as msmtpq. The script is available here:
> https://github.com/venkytv/msmtp-offline
>
> Maybe some of you might find it useful.
>
> Cheers,
> Venky.
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> _______________________________________________
> msmtp-users mailing list
> msmtp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/msmtp-users
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
msmtp-users mailing list
msmtp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/msmtp-users