Logged In: NO
Browser: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Hi there,
I have installed an older version of acmemail
before and had no troubles (thanks to the
documentation) but I am trying now for a production-
level system (mysql, mod_perl, etc) and am having
progmes. I can get the login screen (with a bunch of
errors about variable declarations and uninitialized
values in AcmemailConf.pm. I am not a perl monger at
all. It looks like everything is installed but I may
have some other issues (RH 6.2). Here are some
examples of what perl -w spits into my webserver log:
[Thu Sep 28 23:54:48 2000] acmemail.pl:
Variable "$attachment" will not stay sha
red
at /home/httpd/webmail.llano.net/acmemail/acmemail.pl
line 794.
[Thu Sep 28 23:54:48 2000] null: Use of uninitialized
value at AcmemailConf.pm l
ine 227.
[Thu Sep 28 23:54:48 2000] acmemail.pl: "my" variable
$attachment masks earlier
declaration in same scope
at /home/httpd/webmail.llano.net/acmemail/acmemail.pl
line 161.
only there are a bunch of each of these. Anyone seen
that before? Is there a smack-in-the-head solution
that you had to think through? Or I could just be a
moron...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
mod_perl is fussier than straight CGI. For example,
it imposes some requirements on scripts and
variable definition which would explain the "...will
not stay shared" messages. An excellent source of
information for mod_perl is: http://perl.apache.org/guide/
I see two alternatives (neither of which is very good):
- use (the unacceptably slow) standard CGI
- rewrite the offending acmemail Perl scripts to conform
to mod_perl guidelines
Sorry I cannot be of more help...
Carl
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The warnings you are getting are from all the "my $var"
declarations outside of subfunctions. If you want to not see
these messages, try checking that the "-w" flag and "use
strict" are commented out in acmemail.cgi. It may work, but
on the other hand it might be Apache::Registry that's
printing out the error.
I don't think we'll bother fixing this for acmemail. The CVS
version (sparkle) has been totaly restructured and does not
have this issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The bug you filed long ago has been closed. Please try the
latest version (acmemail >= 2.2.3). If the issue persists,
reopen this bug.
Also a reminder on filing bugs to help as help you: Please
provide full details on your problem. Things to include:
-perl version
-operating system / distribution / version
-imap server version
-any errors / warnings in the Apache's error log
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: NO
Browser: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Hi there,
I have installed an older version of acmemail
before and had no troubles (thanks to the
documentation) but I am trying now for a production-
level system (mysql, mod_perl, etc) and am having
progmes. I can get the login screen (with a bunch of
errors about variable declarations and uninitialized
values in AcmemailConf.pm. I am not a perl monger at
all. It looks like everything is installed but I may
have some other issues (RH 6.2). Here are some
examples of what perl -w spits into my webserver log:
[Thu Sep 28 23:54:48 2000] acmemail.pl:
Variable "$attachment" will not stay sha
red
at /home/httpd/webmail.llano.net/acmemail/acmemail.pl
line 794.
[Thu Sep 28 23:54:48 2000] null: Use of uninitialized
value at AcmemailConf.pm l
ine 227.
[Thu Sep 28 23:54:48 2000] acmemail.pl: "my" variable
$attachment masks earlier
declaration in same scope
at /home/httpd/webmail.llano.net/acmemail/acmemail.pl
line 161.
only there are a bunch of each of these. Anyone seen
that before? Is there a smack-in-the-head solution
that you had to think through? Or I could just be a
moron...
Logged In: YES
user_id=97087
Browser: Mozilla/4.5 [en] (Win95; I)
mod_perl is fussier than straight CGI. For example,
it imposes some requirements on scripts and
variable definition which would explain the "...will
not stay shared" messages. An excellent source of
information for mod_perl is: http://perl.apache.org/guide/
I see two alternatives (neither of which is very good):
- use (the unacceptably slow) standard CGI
- rewrite the offending acmemail Perl scripts to conform
to mod_perl guidelines
Sorry I cannot be of more help...
Carl
Logged In: YES
user_id=165
Is this still an issue? I'd like to close this incident.
Logged In: YES
user_id=97087
This is not a bug; just a characteristic of using mod_perl vs. straight CGI.
Logged In: YES
user_id=165
Ahh.
The warnings you are getting are from all the "my $var"
declarations outside of subfunctions. If you want to not see
these messages, try checking that the "-w" flag and "use
strict" are commented out in acmemail.cgi. It may work, but
on the other hand it might be Apache::Registry that's
printing out the error.
I don't think we'll bother fixing this for acmemail. The CVS
version (sparkle) has been totaly restructured and does not
have this issue.
Logged In: YES
user_id=165
The bug you filed long ago has been closed. Please try the
latest version (acmemail >= 2.2.3). If the issue persists,
reopen this bug.
Also a reminder on filing bugs to help as help you: Please
provide full details on your problem. Things to include:
-perl version
-operating system / distribution / version
-imap server version
-any errors / warnings in the Apache's error log