Re: login_auto, embedding in custom page

Please do not erase the thread context.  Keep the relevant parts of
the conversation.  Don't assume you are the only person we are having
conversations with on the mailing list and that we remember every last
detail of your environment and problem.  Keep context, and post
in-line with your replies.

On 11/29/07, kriswarner <kriswarner <at> solidaritymail.com> wrote:
>
> I discovered the problem.  The code from my last post works, it's just that
> the cookies are stored in mail/ rather than the root folder of my site.

For the plugin to work, that is exactly where the cookie belongs.  All
the other SM cookies should also be placed there.  If your login page
is storing cookies *outside* the SM directory, then that might be a
problem, although a bit strange since the plugin uses $base_dir, which
should be correct.... although maybe when it is run from an embedded
login page it is not (test it and print it out and let us know so we
can ponder other ways to deal with that).  A hack to get it back in
the SM directory would be to go in the plugin and replace $base_uri in
the functions file for all the setcookie() calls with the actual path
you need, such as "/mail/".

If your problem is that cookies ARE being created against the SM
directory, I am not sure I understand what your issue is.  Seems right
to me.

>  So
> if I put my login form in, say, mail/src/, it works.  I'd rather not move
> all of my site files into the mail/ subdirectory though, so is there a way
> that I can access these cookies from the directory above mail/?  Or can I

Re: login_auto, embedding in custom page

Paul Lesniewski wrote:
> 
> Please do not erase the thread context.  Keep the relevant parts of
> the conversation.  Don't assume you are the only person we are having
> conversations with on the mailing list and that we remember every last
> detail of your environment and problem.  Keep context, and post
> in-line with your replies.
> 
My deepest apologies.

Paul Lesniewski wrote:
> 
> 
> On 11/29/07, kriswarner <kriswarner <at> solidaritymail.com> wrote:
>>
>> I discovered the problem.  The code from my last post works, it's just
>> that
>> the cookies are stored in mail/ rather than the root folder of my site.
> 
> For the plugin to work, that is exactly where the cookie belongs.  All
> the other SM cookies should also be placed there.  If your login page
> is storing cookies *outside* the SM directory, then that might be a
> problem, although a bit strange since the plugin uses $base_dir, which
> should be correct.... although maybe when it is run from an embedded
> login page it is not (test it and print it out and let us know so we
> can ponder other ways to deal with that).  A hack to get it back in
> the SM directory would be to go in the plugin and replace $base_uri in
> the functions file for all the setcookie() calls with the actual path
> you need, such as "/mail/".

Re: login_auto, embedding in custom page

> > On 11/29/07, kriswarner <kriswarner <at> solidaritymail.com> wrote:
> >>
> >> I discovered the problem.  The code from my last post works, it's just
> >> that
> >> the cookies are stored in mail/ rather than the root folder of my site.
> >
> > For the plugin to work, that is exactly where the cookie belongs.  All
> > the other SM cookies should also be placed there.  If your login page
> > is storing cookies *outside* the SM directory, then that might be a
> > problem, although a bit strange since the plugin uses $base_dir, which
> > should be correct.... although maybe when it is run from an embedded
> > login page it is not (test it and print it out and let us know so we
> > can ponder other ways to deal with that).  A hack to get it back in
> > the SM directory would be to go in the plugin and replace $base_uri in
> > the functions file for all the setcookie() calls with the actual path
> > you need, such as "/mail/".
> >
> > If your problem is that cookies ARE being created against the SM
> > directory, I am not sure I understand what your issue is.  Seems right
> > to me.
> >
>
> Yes, this last part is the problem. The issue is that my custom login form
> isn't located in the subdirectory of mail/ (the SM directory), but the
> directory above that, so the cookies that are set by the login_auto plugin
> aren't available to my custom login page.

Oh right.  That's my fault - I was thinking *setting* cookies, which
should work if you want to set them for another directory, but of
course the directory where you are trying to *retrieve* them from

Problem Logging In

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Re: Problem Logging In

Kaplan, Andrew H. wrote:
>
> Hi there –
>
> I have recently set up a server running MailScanner, SpamAssassin, and 
> Clam AntiVirus with Sendmail. Additionally, I have installed
>
> the Dovecot IMAP/POP server. I did not make any changes to the 
> /etc/dovecot.conf file, and I was able to start the daemon up without a
>
> problem. I ran a netstat –l command, and the server has imap, imaps, 
> pop3, and pop3s listed in LISTEN states.
>
> The problem is as follows: When I try to log into SquirrelMail, I get 
> the following error message:
>
> Error connecting to IMAP server: localhost.
> 13 : Permission denied
>
> What is causing this error, and what step(s) do I need to take to 
> correct it? Thanks.
>
hosts.allow file maybe .. have you had any successful imap connections 
to this setup from any imap client?
what does "telnet localhost 143" give you?

/sd
>
> The information transmitted in this electronic communication is intended only
> for the person or entity to whom it is addressed and may contain confidential
> and/or privileged material. Any review, retransmission, dissemination or other
> use of or taking of any action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited. If you received this
> information in error, please contact the Compliance HelpLine at 800-856-1983 and
> properly dispose of this information.
>
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> ------------------------------------------------------------------------
>
> -----
> squirrelmail-plugins mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squirrelmail-plugins <at> lists.sourceforge.net
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
> List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

spam_buttons move to non-existent folder

Hi,

I've recently been testing the spam_buttons plugin, but I ran into a
small problem.
When the mail folder that has been configured as destination for a copy
or move action does not exist, the current version gives an error.
In my setup these folders are optional, so an unsuspecting user could
run into this.

Included is a patch for this against spam_buttons-2.0-1.4.0

This options should probably be configurable if released.

Thanks,

Herman van Rink

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Re: spam_buttons move to non-existent folder

On Dec 3, 2007 12:27 PM, Herman van Rink <helmo <at> initfour.nl> wrote:
> Hi,
>
> I've recently been testing the spam_buttons plugin, but I ran into a
> small problem.
> When the mail folder that has been configured as destination for a copy
> or move action does not exist, the current version gives an error.

Seems like that is what *should* happen - it indicates a setup
problem.  But I suppose, if made configurable, your patch could help
save the users who have clueless administrators   

Thank you

> In my setup these folders are optional, so an unsuspecting user could
> run into this.
>
> Included is a patch for this against spam_buttons-2.0-1.4.0
>
> This options should probably be configurable if released.
>
> Thanks,
>
> Herman van Rink
>
>

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Re: Problem Logging In

Hi there --

It does not appear that I have had any successful imap connections to this
setup. 

When I do a telnet localhost 143, I get the following response:

$ telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK Dovecot ready.

The hosts.allow file does not have any entries in it except the commented lines
at the beginning of the file. The same goes for the hosts.deny file. 

-----Original Message-----
From: squirrelmail-plugins-bounces <at> lists.sourceforge.net
[mailto:squirrelmail-plugins-bounces <at> lists.sourceforge.net] On Behalf Of Steve
Devine
Sent: Monday, December 03, 2007 3:17 PM
To: Squirrelmail Plugins Mailing List
Subject: Re: [SM-PLUGINS] Problem Logging In

Kaplan, Andrew H. wrote:
>
> Hi there -
>
> I have recently set up a server running MailScanner, SpamAssassin, and 
> Clam AntiVirus with Sendmail. Additionally, I have installed
>
> the Dovecot IMAP/POP server. I did not make any changes to the 
> /etc/dovecot.conf file, and I was able to start the daemon up without a
>
> problem. I ran a netstat -l command, and the server has imap, imaps, 
> pop3, and pop3s listed in LISTEN states.
>
> The problem is as follows: When I try to log into SquirrelMail, I get 
> the following error message:
>
> Error connecting to IMAP server: localhost.
> 13 : Permission denied
>
> What is causing this error, and what step(s) do I need to take to 
> correct it? Thanks.
>
hosts.allow file maybe .. have you had any successful imap connections 
to this setup from any imap client?
what does "telnet localhost 143" give you?

/sd
>
> The information transmitted in this electronic communication is intended only
> for the person or entity to whom it is addressed and may contain confidential
> and/or privileged material. Any review, retransmission, dissemination or other
> use of or taking of any action in reliance upon this information by persons or
> entities other than the intended recipient is prohibited. If you received this
> information in error, please contact the Compliance HelpLine at 800-856-1983
and
> properly dispose of this information.
>
>
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> ------------------------------------------------------------------------
>
> -----
> squirrelmail-plugins mailing list
> Posting guidelines: http://squirrelmail.org/postingguidelines
> List address: squirrelmail-plugins <at> lists.sourceforge.net
> List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
> List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options):
https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Re: Problem Logging In

Why did you top post?  Surely, because the link was sent when you
subscribed to the mailing list, and because it is at the bottom of all
messages on this list, you ALREADY read the posting guidelines.
Right?  So why did you top-post?

> > > I have recently set up a server running MailScanner, SpamAssassin, and
> > > Clam AntiVirus with Sendmail. Additionally, I have installed
> > >
> > > the Dovecot IMAP/POP server. I did not make any changes to the
> > > /etc/dovecot.conf file, and I was able to start the daemon up without a
> > >
> > > problem. I ran a netstat -l command, and the server has imap, imaps,
> > > pop3, and pop3s listed in LISTEN states.
> > >
> > > The problem is as follows: When I try to log into SquirrelMail, I get
> > > the following error message:
> > >
> > > Error connecting to IMAP server: localhost.
> > > 13 : Permission denied
> > >
> > > What is causing this error, and what step(s) do I need to take to
> > > correct it? Thanks.
> >
> > hosts.allow file maybe .. have you had any successful imap connections
> > to this setup from any imap client?
> > what does "telnet localhost 143" give you?
>
> It does not appear that I have had any successful imap connections to this
> setup.
>
> When I do a telnet localhost 143, I get the following response:
>
> $ telnet localhost 143
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> * OK Dovecot ready.
>
> The hosts.allow file does not have any entries in it except the commented lines
> at the beginning of the file. The same goes for the hosts.deny file.

READ the posting guidelines.  Then post the system information it
requests.  It is possible you are running with SELinux turned on -
check your system message log file - but that's a wild guess because
you didn't do your homework first.

> > The information transmitted in this electronic communication is intended only

<snip>

When you send a message to this list, it becomes public domain, thus
disclaimers like this are completely meaningless - and not welcomed
here.

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins

Re: spam_buttons move to non-existent folder

Paul Lesniewski wrote:
> On Dec 3, 2007 12:27 PM, Herman van Rink <helmo <at> initfour.nl> wrote:
>   
>> Hi,
>>
>> I've recently been testing the spam_buttons plugin, but I ran into a
>> small problem.
>> When the mail folder that has been configured as destination for a copy
>> or move action does not exist, the current version gives an error.
>>     
>
> Seems like that is what *should* happen - it indicates a setup
> problem.  But I suppose, if made configurable, your patch could help
> save the users who have clueless administrators   
>   
What about this then?
The default value if off.

> Thank you
>
>   
>> In my setup these folders are optional, so an unsuspecting user could
>> run into this.
>>
>> Included is a patch for this against spam_buttons-2.0-1.4.0
>>
>> This options should probably be configurable if released.
>>
>> Thanks,
>>
>> Herman van 

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4

-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins <at> lists.sourceforge.net
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins