Re: Send authenticated mail with MIME::Lite
Mail::Sender handles sending via authenticated smtp. Carl
Re: XML::Simple install problems
On 11/9/05, Shawn O'Donnell [EMAIL PROTECTED] wrote: Another question: I've a lot of bad luck with cpan not installing modules. If I install OS X 10.4, will I get a clean perl installation to work with? I didn't bother with the default Apple install of perl (mostly because I knew I'd botch it eventually), so I installed perl for my primary user on my powerbook. It took a bit of reading through the install docs, but the options to install a local, personal perl weren't that bad. I couldn't figure out how to install a system-wide perl without running my administration account, so I've got perl under chris/opt/perl-5.8.7/... Do an interactive install, give it a path to install to, say yes a lot, watch it go. Good luck. -- Chris Cantrall [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Send authenticated mail with MIME::Lite
the easiest fix for this issue is to go to the SBC DSL site and file the request to have the ports unblocked for your account. =) it takes about a day for them to open them up, and it's just a simple web form to fill out. - brian
Re: Send authenticated mail with MIME::Lite
Hi Brian, Yes, I did that, but mail is still not going through. Does anyone know what happens to the mail when it is doesn't go through? Thanks, Mark On Nov 10, 2005, at 6:39 AM, brian pink wrote: the easiest fix for this issue is to go to the SBC DSL site and file the request to have the ports unblocked for your account. =) it takes about a day for them to open them up, and it's just a simple web form to fill out. - brian
Re: Send authenticated mail with MIME::Lite
On Thu, November 10, 2005 11:43 am, Mark Wheeler said: Hi Brian, Yes, I did that, but mail is still not going through. Does anyone know what happens to the mail when it is doesn't go through? In theory it should keep trying until the timeout period expires, which is normally set for around 3 days on SMTP servers. After that, an error should be bounced back saying it didn't go through. Some servers will send a message earlier (commonly at the end of 12/24 hours), confirming that they are still trying. That assumes everyone is playing nice. If someone is blocking selected SMTP connections, they are already not playing nice. They could fake an acceptance and just drop the message, or do something else... And, this assumes you've actually got it to the SMTP transport on your end. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
Re: Send authenticated mail with MIME::Lite
OK Well... I checked out another part of my setup, namely PostFix Enabler, which I used to set things up to send out mail. I added the SBC smtp server, login, and password and bingo! Mail is going through again. So apparently, I don't have to do the authentication through my script, but just set it up though postfix. Thanks again for all you help. I will check out Mail::Sender, though. Looks interesting. Thanks again. Mark On Nov 10, 2005, at 8:58 AM, Daniel T. Staal wrote: On Thu, November 10, 2005 11:43 am, Mark Wheeler said: Hi Brian, Yes, I did that, but mail is still not going through. Does anyone know what happens to the mail when it is doesn't go through? In theory it should keep trying until the timeout period expires, which is normally set for around 3 days on SMTP servers. After that, an error should be bounced back saying it didn't go through. Some servers will send a message earlier (commonly at the end of 12/24 hours), confirming that they are still trying. That assumes everyone is playing nice. If someone is blocking selected SMTP connections, they are already not playing nice. They could fake an acceptance and just drop the message, or do something else... And, this assumes you've actually got it to the SMTP transport on your end. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. ---
print 3 up labels
Greetings, I want to print Avery 6140 labels with name and address from a mac. Is there a library. If not, does anyone know how to set a font and tab a certain number of inches to print 3 columns? Joe Alotta
Re: print 3 up labels
On 11/10/05, Joseph Alotta [EMAIL PROTECTED] wrote: Greetings, I want to print Avery 6140 labels with name and address from a mac. Is there a library. If not, does anyone know how to set a font and tab a certain number of inches to print 3 columns? Joe Alotta A CPAN search is your best friend here. Avery label turns up PostScript::MailLabels, labels, and Paper::Specs. Other search terms will undoubtedly turn up other results. Take a look and see what works for you. -- jay -- This email and attachment(s): [ ] blogable; [ x ] ask first; [ ] private and confidential daggerquill [at] gmail [dot] com http://www.tuaw.com http://www.dpguru.com http://www.engatiki.org values of β will give rise to dom!
Re: XML::Simple install problems
On Nov 9, 2005, at 2:27 PM, Chris Cantrall wrote: user on my powerbook. It took a bit of reading through the install docs, but the options to install a local, personal perl weren't that bad. Reading the docs is a *good* thing, and I don't mean to imply otherwise by saying this... :-) Even if you hadn't read the docs, or read them very closely, you would have been OK. The default is to install under /usr/local, well out of harm's way. You actually have to work at it to screw things up now - although that wasn't always the case. I couldn't figure out how to install a system-wide perl without running my administration account Use sudo for the final step. I.e: sudo make install Naturally, if Perl's installed this way, you'll also need to use sudo to install modules: sudo /usr/local/bin/perl -MCPAN -e shell sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org
Re: XML::Simple install problems
At 05:32 PM 11/9/2005, Sherm Pendley wrote: On the other hand, because it's configured to use a different architecture, many of the CPAN modules you've installed for this Perl will not work with the standard Tiger Perl. And if problems do happen to crop up, they'll be obscure and difficult to diagnose and debug. Thanks. I'll pay more attention next time I mess with the installation. I guess I told cpan to do the wrong thing last time I upgraded. Besides README.macosx, do you know of other good documentation on perl installation hygiene? --Shawn
Re: print 3 up labels
On Nov 10, 2005, at 2:46 PM, Jay Savage wrote: On 11/10/05, Joseph Alotta [EMAIL PROTECTED] wrote: Greetings, I want to print Avery 6140 labels with name and address from a mac. Is there a library. If not, does anyone know how to set a font and tab a certain number of inches to print 3 columns? Joe Alotta A CPAN search is your best friend here. Avery label turns up PostScript::MailLabels, labels, and Paper::Specs. Other search terms will undoubtedly turn up other results. Take a look and see what works for you. Or AddressBook can print mailing labels in lots of Avery formats natively. You could create some data in a format that it can import, then print there. -Ken
Re: XML::Simple install problems
On Nov 10, 2005, at 3:54 PM, Shawn O'Donnell wrote: At 05:32 PM 11/9/2005, Sherm Pendley wrote: On the other hand, because it's configured to use a different architecture, many of the CPAN modules you've installed for this Perl will not work with the standard Tiger Perl. And if problems do happen to crop up, they'll be obscure and difficult to diagnose and debug. Thanks. I'll pay more attention next time I mess with the installation. I guess I told cpan to do the wrong thing last time I upgraded. It's not really a question of the right vs. wrong configuration. It's just options, whether you want Perl to support multi-threading or not, 32- or 64-bit, etc. A module that was compiled for a multi- threaded Perl isn't compatible with one that was compiled for a single-threaded Perl. Same thing with 32- vs. 64-bit, 5.6.x vs. 5.8.x, etc. But Perl's installer knows all about that, so it very rarely causes problems. It's why some modules are installed in specific subdirectories such as 5.8.6/darwin-thread-multi-2level. Only a that specific version and configuration of perl will include that subdir in @INC by default. A few years ago, the problem was much worse - Apple's installation of 5.6.0 on 10.0, 10.1, and 10.2 omitted the version subdirectory, and the configure script for 5.8.0 had problems of its own. That resulted in a lot of problems for folks who tried to upgrade. But that's all ancient history now. Besides README.macosx, do you know of other good documentation on perl installation hygiene? The generic README is pretty thorough, and now that we're using a *nix system it's virtually all relevant. The first part of the ExtUtils::MakeMaker man page is very informative about what module pieces are installed where. sherm-- Cocoa programming in Perl: http://camelbones.sourceforge.net Hire me! My resume: http://www.dot-app.org
Re: CamelBones on Intel
On 11/10/05 Sherm Pendley wrote: To the future and beyond! Is that from a movie, tv show, book, etc.? It sounds familiar, but I can't quite place it... it's been bugging me for days... ;-) To infinity and beyond! was from Toy Story. Best, - Bruce __bruce__van_allen__santa_cruz__ca__
Re: CamelBones on Intel
On 11/10/05 Bruce Van Allen wrote: On 11/10/05 Sherm Pendley wrote: To the future and beyond! Is that from a movie, tv show, book, etc.? It sounds familiar, but I can't quite place it... it's been bugging me for days... ;-) To infinity and beyond! was from Toy Story. And let me add that I genuinely think my variation belongs to you (Sherm) and Camelbones -- both because you've bridged to the new Mac chipset, and also in the bigger sense that Camelbones provides a path to the future for Perl programmers to do cool things with Cocoa and OS X. To the future and beyond! - Bruce __bruce__van_allen__santa_cruz__ca__
