Hi there. Since the charset doesn't seem to be the problem, maybe this will
help.
Did some digging and found a bug report against redhat version 8 concerning
terminal codes in perldoc output.
There were comments about this being a bug in groff.
https://bugzilla.redhat.com/show_bug.cgi?id=72125
T
On Fri, Jan 9, 2009 at 6:30 PM, Adam Jimerson wrote:
> Gunnar Hjalmarsson wrote:
>
> > Adam Jimerson wrote:
> >>
> >> According to perlsec I need to use it as a key in a hash or reference a
> >> substring. The example given is
> >>
> >> ,[ ]
> >> if ($data =~ /^([...@\w.]+)$/) {
> >> $data
matt wrote:
>
> This is usually the result of a mismatch between the character set
> used by your ssh client and the locale settings of your session.
> Here's a link that discusses:
> http://help.lockergnome.com/linux/high-ascii-characters-linux-terminal-
ssh-ftopict487060.html
>
> [u...@host ~]
Gunnar Hjalmarsson wrote:
> Adam Jimerson wrote:
>>
>> According to perlsec I need to use it as a key in a hash or reference a
>> substring. The example given is
>>
>> ,[ ]
>> if ($data =~ /^([...@\w.]+)$/) {
>> $data = $1; # $data now untainted
>> } else {
>> die "Bad data in '$data'";
Adam Jimerson wrote:
Gunnar Hjalmarsson wrote:
There is only one suspected variable to consider, i.e. $name, which is
probably tainted. Untaint it, and you are done. ( You remember where to
find out how, right? ;-) )
According to perlsec I need to use it as a key in a hash or reference a
sub
On Jan 8, 8:55 pm, vend...@charter.net (Adam Jimerson) wrote:
> "Mike Williams" wrote:
>
> > You can read the output of perldoc perlsec on the web at:
> >http://perldoc.perl.org/perlsec.html
>
> That will help, thanks!
>
> > What version of perl are you using? What OS?
>
> > I've seen similar prob
Gunnar Hjalmarsson wrote:
> Adam Jimerson wrote:
>> Gunnar Hjalmarsson wrote:
>>> Adam Jimerson wrote:
Do I need to specify anything for the $ENV{PATH} or do I just leave it
blank
>>>
>>> It depends. You have to take into consideration whether your program
>>> relies on any of the paths.
> I wasn't able to remember what it exactly said, but yes it is about
> $ENV{PATH}, on my machine perldoc perlsec is riddled with formating problems
> it looks like, here is a copy of what I mean:
>
> "Perl automatically enables a set of special security checks, called
> ESC[4mtaintESC[24
> m ESC[4
> Is a discussion about taintedness off topic on a Perl-CGI list? Don't
> think so.
'Sending email via SMTP' is off-topic for CGI.
Cross-posting is bad form on any list. Bad boy Fulivo.
Adam pointed out on Wednesday that the thread was slipping OT.
> > and the thread is running strongly on per
Dermot Paikkos wrote:
This is all very OT
Is a discussion about taintedness off topic on a Perl-CGI list? Don't
think so.
and the thread is running strongly on perl-beginners.
:-/
And...?
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
--
To unsubscribe, e-mail: be
Adam Jimerson wrote:
Gunnar Hjalmarsson wrote:
Adam Jimerson wrote:
Do I need to specify anything for the $ENV{PATH} or do I just leave it
blank
It depends. You have to take into consideration whether your program
relies on any of the paths. If not, it's fine to leave it blank.
The only ti
This is all very OT and the thread is running strongly on
perl-beginners.
:-/
--
To unsubscribe, e-mail: beginners-cgi-unsubscr...@perl.org
For additional commands, e-mail: beginners-cgi-h...@perl.org
http://learn.perl.org/
"Mike Williams" wrote:
>
> You can read the output of perldoc perlsec on the web at:
> http://perldoc.perl.org/perlsec.html
>
That will help, thanks!
> What version of perl are you using? What OS?
>
> I've seen similar problems with perldoc a few years ago while using perl
> 5.6.1 on early v
Gunnar Hjalmarsson wrote:
>> I wasn't able to remember what it exactly said, but yes it is about
>> $ENV{PATH}, on my machine perldoc perlsec is riddled with formating
>> problems
>
> You can always read it online: http://perldoc.perl.org/perlsec.html
>
>> Do I need to specify anything for the $
Adam Jimerson wrote:
> I wasn't able to remember what it exactly said, but yes it is about
> $ENV{PATH}, on my machine perldoc perlsec is riddled with formating
> problems it looks like, here is a copy of what I mean:
>
Ok adding $ENV{PATH} = ''; or even $ENV{PATH} = '/usr/bin'; (in case it
nee
On Thu, Jan 8, 2009 at 2:17 PM, Adam Jimerson wrote:
> >
> > Please read more about Perl security in "perldoc perlsec".
> >
>
> I wasn't able to remember what it exactly said, but yes it is about
> $ENV{PATH}, on my machine perldoc perlsec is riddled with formating
> problems
> it looks like, her
Adam Jimerson wrote:
Gunnar Hjalmarsson wrote:
Adam Jimerson wrote:
are you using the -T switch on your
script? When I tried to open "/usr/bin/mail" with that switch on I get a
error message about an insecure environment command.
Did it just say "insecure environment"? On my box it says: "In
Gunnar Hjalmarsson wrote:
> Adam Jimerson wrote:
>>> I solved my problem using the sendmail with the code below in my script:
>>>
>>> open (MAIL, "|/usr/sbin/sendmail -t ");
>>> print MAIL "From: someaddr...@somedomain\n";
>>> print MAIL "To: someaddre...@somedomain\n";
>>> print MAIL "Content-Typ
Adam Jimerson wrote:
I solved my problem using the sendmail with the code below in my script:
open (MAIL, "|/usr/sbin/sendmail -t ");
print MAIL "From: someaddr...@somedomain\n";
print MAIL "To: someaddre...@somedomain\n";
print MAIL "Content-Type: text/plain\n";
print MAIL "Subject: Very simple
"F??lvio Figueir??a" wrote:
> Hi Sean,
> I think there is a firewall, but I don't have access to it because I am on
> work.
> I solved my problem using the sendmail with the code below in my script:
>
> open (MAIL, "|/usr/sbin/sendmail -t ");
> print MAIL "From: someaddr...@somedomain\n";
> print
Hi Sean,
I think there is a firewall, but I don't have access to it because I am on
work.
I solved my problem using the sendmail with the code below in my script:
open (MAIL, "|/usr/sbin/sendmail -t ");
print MAIL "From: someaddr...@somedomain\n";
print MAIL "To: someaddre...@somedomain\n";
print
On Tue, Jan 6, 2009 at 7:17 AM, Fúlvio wrote:
> Hi Jody,
>
> I use your code bellow but the the following error message happens:
>
> "Can't call method "domain" on an undefined value at "
Works for me. Are you behind a firewall by any chance?
Sean
>
>
> On 5 jan, 21:16, jody_rrhq_fa...@
Hi Jody,
I use your code bellow but the the following error message happens:
"Can't call method "domain" on an undefined value at "
Thanks,
Fúlvio
On 5 jan, 21:16, jody_rrhq_fa...@yahoo.com (Jody Fanto) wrote:
> The problem is that you are using an invalid smtp server address. You
> proba
The problem is that you are using an invalid smtp server address. You probably
want "smtp.mail.yahoo.com". For example, this works for me --
#!perl
use strict;
use warnings;
use Net::SMTP;
my $smtp = Net::SMTP->new("smt
Hi all,
I am trying to send an email using the following code:
use Net::SMTP;
$smtp = Net::SMTP->new("smtp.yahoo.com");
$smtp->mail('fulviocg');
but the error below is happening:
Can't call method "mail" on an undefined value at
Can someone help me?
Thanks
Fúlvio
--
To unsubscribe,
On Wed, 17 Apr 2002, Bill Lyles wrote:
> How can I change this to smtp?
Bill:
Try using Mail::Mailer:
#!/usr/bin/perl -w
use Mail::Mailer;
my $To = $ARGV[0];
my $mailer = Mail::Mailer->new('smtp', 'your.smtp.host');
$mailer->open({
From => "[EMAIL PROTECTED]",
T
I have a script that I'm trying to edit to use smtp because it only calls
for a mail program.
this is the code
if ($found) {
open (MAILME, "|$mailprog -t") or &dienice("Can't access $mailprog!\n");
print MAILME "To: $email\n";
print MAILME "From: $adminmail\n";
print MAILME "Subject: Your userna
27 matches
Mail list logo
