From madcityzen at gmail.com Sat Jan 2 15:44:00 2016 From: madcityzen at gmail.com (Doug Bell) Date: Sat, 2 Jan 2016 17:44:00 -0600 Subject: [Chicago-talk] Looking for a Perl 6 talk In-Reply-To: <50039F39-ECFA-4F39-97A9-B07B12623263@petdance.com> References: <50039F39-ECFA-4F39-97A9-B07B12623263@petdance.com> Message-ID: <115C5305-4A4D-4B85-9046-34F8B3ACE3D1@gmail.com> I'm also only partially following Perl 6 (was hard keeping up enthusiasm after the first 5 years), but I'd be willing to take a few weeks to refresh on things to be able to give an introduction and answer questions (especially the ones concerning p5 vs. p6 we've been fielding for years). Rob Hoelz was down here last Spring to give a talk about working on the Rakudo Perl 6 project, he might be in a better position to give a talk on general Perl 6. I can ask if he's interested (I'm not sure if he's on this list). Doug Bell madcityzen at gmail.com > On Dec 30, 2015, at 12:30 PM, Andy Lester wrote: > > Wayne Schneideman from Uniforum Chicago (http://uniforum.chi.il.us/ ) emailed me asking if I would like to do a talk on Perl 6. Since I only tangentially follow Perl 6, I told him I would not be a good person to do this, but that I would post to the Perl Mongers mailing list and see if anyone there is interested. > > His original email to me says: ?Would you be interested in doing a presentation before UniForum Chicago on Perl 6? Maybe going over why we should care, and what is different between Perl 5 and Perl 6... can perl 5 code run on Perl 6 etc.? > > If you can help out, please email him at wayne.schneidman at gmail.com > > Thanks, > Andy > > -- > Andy Lester => www.petdance.com > _______________________________________________ > Chicago-talk mailing list > Chicago-talk at pm.org > http://mail.pm.org/mailman/listinfo/chicago-talk -------------- next part -------------- An HTML attachment was scrubbed... URL: From lembark at wrkhors.com Sat Jan 2 21:18:39 2016 From: lembark at wrkhors.com (Steven Lembark) Date: Sat, 2 Jan 2016 23:18:39 -0600 Subject: [Chicago-talk] Looking for a Perl 6 talk In-Reply-To: <50039F39-ECFA-4F39-97A9-B07B12623263@petdance.com> References: <50039F39-ECFA-4F39-97A9-B07B12623263@petdance.com> Message-ID: <20160102231839.4491e8a4.lembark@wrkhors.com> -- Steven Lembark 3646 Flora Pl Workhorse Computing St Louis, MO 63110 lembark at wrkhors.com +1 888 359 3508 From richard at rushlogistics.com Fri Jan 8 06:20:00 2016 From: richard at rushlogistics.com (richard at rushlogistics.com) Date: Fri, 08 Jan 2016 08:20:00 -0600 Subject: [Chicago-talk] Perl Mail Client recomendations sought Message-ID: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> I am currenly receiving and sending a very low volume of emails (sending with via scripts with Mail::Message) to and from a my digitalocean sight. Right now my method for checking my emails to this sight is ls -lt /var/mail and then purusing through which ever file has new mail. This barebones setup was the result of me follwing a digitalocean tutorial to setup up postfix and sendmail. I know next to nothing about mail servers and was wondering if someone could recommend a solution that will make it a bit easier to respond to emails sent to the domain. Looking for something with a not steep learning curve. ? Is there any such perl module that can help? Doesn't have to be something super comprehensive just something to get me out of the dark ages. Thanks From briank at kappacs.com Fri Jan 8 06:42:47 2016 From: briank at kappacs.com (Brian Katzung) Date: Fri, 08 Jan 2016 08:42:47 -0600 Subject: [Chicago-talk] Perl Mail Client recomendations sought In-Reply-To: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> References: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> Message-ID: <15221b09658.274c.7e190a8529e75912abb8474118927f1f@kappacs.com> I suggest either aliasing all the relevant addresses to one mailbox, or if it's literally every address in the domain, configure whichever MTA to always deliver to one mailbox. - Brian On January 8, 2016 08:20:27 richard at rushlogistics.com wrote: > I am currenly receiving and sending a very low volume of emails (sending > with via scripts with Mail::Message) to and from a my digitalocean sight. > Right now my method for checking my emails to this sight is ls -lt > /var/mail and then purusing through which ever file has new mail. This > barebones setup was the result of me follwing a digitalocean tutorial to > setup up postfix and sendmail. I know next to nothing about mail servers > and was wondering if someone could recommend a solution that will make it a > bit easier to respond to emails sent to the domain. Looking for something > with a not steep learning curve. ? Is there any such perl module that can > help? Doesn't have to be something super comprehensive just something to > get me out of the dark ages. > > Thanks > _______________________________________________ > Chicago-talk mailing list > Chicago-talk at pm.org > http://mail.pm.org/mailman/listinfo/chicago-talk From amead2 at alanmead.org Fri Jan 8 09:09:24 2016 From: amead2 at alanmead.org (Alan Mead) Date: Fri, 8 Jan 2016 11:09:24 -0600 Subject: [Chicago-talk] Perl Mail Client recomendations sought In-Reply-To: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> References: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> Message-ID: <568FED44.8080909@alanmead.org> Richard, So the email ends up on a Linux|BSD server and you want to read it on the command line? I'd install mailx or mutt. Neither is terribly complex. I prefer mailx for simple emails (but then I like vi/vim as well) but mutt has a lot more functionality. You could also drop a .forward file into the home directory of the user(s) who receive(s) the email, which should forward the email to the mailbox of your choice (including at other domains, e.g., your rushlogistics.com address). You can also (as root) drop an alias into /etc/aliases (and then with some email servers, you need to run newaliases as root to get your mail program to pick up the new alias). Both of these will forward the email of those users (which may not be desirable), but with the advantage that your email comes to one place that you check using your favorite/familiar email client. Finally, you can probably configure your digitalocean host to serve email to clients and then use a client like Thunderbird to pick up that email. I've never done this so I don't know the details but you could search for POP or IMAP as those are the protocols you would use (POP generally downloads the email to your client; IMAP generally leaves the email on the server). For example, "POP or IMAP linux server" provides some useful-looking links. Or install a package like SquirrelMail, Roundcube, etc. on your digitalocean host, which will allow you to read your emails through a web interface. This approach may be the riskiest because it means exposing this service to the wild Internet. Or, if I misunderstood your problem, maybe you could restate it... I don't see how Perl is likely to be of use here.... -Alan On 1/8/2016 8:20 AM, richard at rushlogistics.com wrote: > I am currenly receiving and sending a very low volume of emails (sending with via scripts with Mail::Message) to and from a my digitalocean sight. Right now my method for checking my emails to this sight is ls -lt /var/mail and then purusing through which ever file has new mail. This barebones setup was the result of me follwing a digitalocean tutorial to setup up postfix and sendmail. I know next to nothing about mail servers and was wondering if someone could recommend a solution that will make it a bit easier to respond to emails sent to the domain. Looking for something with a not steep learning curve. Is there any such perl module that can help? Doesn't have to be something super comprehensive just something to get me out of the dark ages. > > Thanks > _______________________________________________ > Chicago-talk mailing list > Chicago-talk at pm.org > http://mail.pm.org/mailman/listinfo/chicago-talk -- Alan D. Mead, Ph.D. President, Talent Algorithms Inc. science + technology = better workers +815.588.3846 (Office) +267.334.4143 (Mobile) http://www.alanmead.org Announcing the Journal of Computerized Adaptive Testing (JCAT), a peer-reviewed electronic journal designed to advance the science and practice of computerized adaptive testing: http://www.iacat.org/jcat From richard at rushlogistics.com Mon Jan 11 09:33:47 2016 From: richard at rushlogistics.com (Richard Reina) Date: Mon, 11 Jan 2016 11:33:47 -0600 Subject: [Chicago-talk] Perl Mail Client recomendations sought In-Reply-To: <20160109105316.6e351f70.lembark@wrkhors.com> References: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> <20160109105316.6e351f70.lembark@wrkhors.com> Message-ID: <23FE9A61-175B-4572-849E-BC38BC7DA6B6@rushlogistics.com> Thank you for the great answers Alan and Steve. I don't think I want to mess with my own mail server. I have poked around at some or the perl Mail modules but not sure that's what I want. In the end I would love to find an online mail client (meaning that I can access it from anywhere) that would always make sure my responses are from my domain -- something a forward situations sometimes fails at because I've noticed that my wife's replies sometimes show her gmail.com domain and not her company domain. > El ene 9, 2016, a las 10:53 AM, Steven Lembark escribi?: > > > Sanity check: > > You are runninng your own mail server (i.e., > the mail is housed on a machine you run)? > > If so I can show you how to set up basic mail handling, but it is > going to be more work than you really want to deal with keeping the > mail server up and running. > > Best approach is to find any mail service you like (gmail is a pain > to use, yahoo is easier, I use one in CT that also handles my DNS > records). At that point you can have an MX record in DNS for the mail > that gets all mail sent to foobar at runshlogictics -> foobar at theservice. > > After that you can use any email client you like to access the mail > or use Perl modules with IMAP protocol to automate processing of the > email. > > If you really, truly want to run your own email server I can send > you instructions for setting up a postfix, procmail, and dovecot > (all of which come standard on *NIX) that will work nicely for > your purposes. The real problem is maintaining proper security with > the email service -- which is why it's better to have the mail sent > to an outside service and either read it there or pull it with > fetchmail onto the local system; which I can show you how to do > also if you like. > > -- > Steven Lembark 3646 Flora Pl > Workhorse Computing St Louis, MO 63110 > lembark at wrkhors.com +1 888 359 3508 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cjhamil at gmail.com Mon Jan 11 09:45:08 2016 From: cjhamil at gmail.com (Chris Hamilton) Date: Mon, 11 Jan 2016 11:45:08 -0600 Subject: [Chicago-talk] Perl Mail Client recomendations sought In-Reply-To: <23FE9A61-175B-4572-849E-BC38BC7DA6B6@rushlogistics.com> References: <20160108082000.8bqnyua9fogcoosk@hostingemail.xo.com> <20160109105316.6e351f70.lembark@wrkhors.com> <23FE9A61-175B-4572-849E-BC38BC7DA6B6@rushlogistics.com> Message-ID: > I would love to find an online mail client (meaning that I can access it from anywhere) that would always make sure my responses are from my domain Not a perl-related answer, but Zoho mail is free for up to 10 users (you only need one, and can setup as many distribution list addresses that auto-forward to your main one, and you can reply from any of those as well). https://www.zoho.com/mail/ It's extremely easy to just point your MX records to the Zoho mail account for whatever domain you want and you can set that up as an account in Gmail (to send and receive as) or you can autoforward or whatever you like. I'm pretty sure you can even map multiple domains to the same Zoho account. I'm sure other comparable services exist as well, this is just one I've used for a couple domains and was extremely painless to setup. After the few minutes of setup and configuration, I've never really needed to login to the Zoho account itself ever again (everything is sent/received via my Gmail account after configuring it properly), but of course you could use their online mail client as well, if you preferred. -Chris On Mon, Jan 11, 2016 at 11:33 AM, Richard Reina wrote: > Thank you for the great answers Alan and Steve. I don't think I want to > mess with my own mail server. I have poked around at some or the perl Mail > modules but not sure that's what I want. In the end I would love to find an > online mail client (meaning that I can access it from anywhere) that would > always make sure my responses are from my domain -- something a forward > situations sometimes fails at because I've noticed that my wife's replies > sometimes show her gmail.com domain and not her company domain. > > > El ene 9, 2016, a las 10:53 AM, Steven Lembark > escribi?: > > > Sanity check: > > You are runninng your own mail server (i.e., > the mail is housed on a machine you run)? > > If so I can show you how to set up basic mail handling, but it is > going to be more work than you really want to deal with keeping the > mail server up and running. > > Best approach is to find any mail service you like (gmail is a pain > to use, yahoo is easier, I use one in CT that also handles my DNS > records). At that point you can have an MX record in DNS for the mail > that gets all mail sent to foobar at runshlogictics -> foobar at theservice. > > After that you can use any email client you like to access the mail > or use Perl modules with IMAP protocol to automate processing of the > email. > > If you really, truly want to run your own email server I can send > you instructions for setting up a postfix, procmail, and dovecot > (all of which come standard on *NIX) that will work nicely for > your purposes. The real problem is maintaining proper security with > the email service -- which is why it's better to have the mail sent > to an outside service and either read it there or pull it with > fetchmail onto the local system; which I can show you how to do > also if you like. > > -- > Steven Lembark 3646 Flora Pl > Workhorse Computing St Louis, MO 63110 > lembark at wrkhors.com +1 888 359 3508 > > > _______________________________________________ > Chicago-talk mailing list > Chicago-talk at pm.org > http://mail.pm.org/mailman/listinfo/chicago-talk > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jtk at depaul.edu Tue Jan 19 16:02:37 2016 From: jtk at depaul.edu (John Kristoff) Date: Wed, 20 Jan 2016 00:02:37 +0000 Subject: [Chicago-talk] Speeding up DBI::Pg do,commit (UPSERT) Message-ID: <20160120000237.GC7418@aharp.iorc.depaul.edu> Hello friends, I'm not using the most current version of PostgreSQL so a native UPSERT SQL statement for some database (DBD::Pg) statements are implemented using a technique like the one described here (with the SAVEPOINT feature): I have to roll through a loop a fairly significant amount of times (maybe a million or two), which on my system can take a significant amount of time. NYTProf shows an extensive amount of time is taken up with calls to DBI::db::do and DBD::db:commit. I might be able to optimize my code by assuming there will be no race condition so I might be able to risk just doing an INSERT if an UPDATE fails as shown at the top of the page linked above and just ensure only this is the only process that will ever write to the table and it only runs once. Dangerous perhaps, but I could do this and performance will probably improve. I might go that route if my options to improve performance aren't available. I cannot easily convert this process to a bulk COPY since I'd potentially be updating some rows and not just inserting them. I'd prefer to have a single table with rows that I can just update if possible. So my question is, short of making fundamental database changes, does anyone have any general strategies for doing UPSERTs in a performance-efficient way, better than I'm currently using of course. Thank you, John