squirrelmail-plugins — SquirrelMail Plugins Mailing List

Re: Mail Filter Plugin request

[Joshua P. <par...@of...>]

> That is to say, I don't think that sendmail normally delivers to the 
spool.
> 

I don't know about sendmail, but I do know qmail delivers directly to the 
user's maildir.

> In fact, RedHat uses procmail out of the box, whether or not you set up a
> .procmailrc.
> 
> -Peter
> 
> 
> > I think this is very desireable, especially because it means all the
> > filtering is done before SM even sees the mail, and that means SM 
doesn't
> > have to make tons of extra connections to the IMAP server. One question
> > though: This means administrators have to make their SMTP server use
> > procmail, rather than just deliver the mail directly to the mailbox,
> > correct? Or does procmail work on the users mailbox?
> >
> > > Mail filtering is one of the primary reasons that the plugin 
architecture
> > was
> > > implemented.
> > >
> > > Mail filtering really belongs in the MDA.  That said, there is an 
extremly
> > > powerful MDA that does all the things you want and much more.  
Procmail.
> > >
> > > It seems that an optional component for SM could be devised, that 
would
> > allow
> > > users to configure their .procmailrc (with permissions set to 720 and
> > group set
> > > to the webserver's gid (of course this would allow anyone who owned 
the
> > > webserver to change email filtering, but I think that is a tolerable
> > risk.))
> > > from within SM, but still allow fitering to be done at the correct 
place.
> > >
> > > This would reduce the amount of repeated effort and would build upon 
the
> > > extensive work of the Procmail folks.
> > >
> > > What do you all think?
> > >
> > > -Peter
> > >
> > >
> > > > I need a way to filter by this header pretty bad...some emails I 
get can
> > > > only be identified that way.  I'd be *very* greatful for it.
> > > >
> > > > As far as future requests?  Well I have a few of those too :)
> > >
> 
> --
> Get my PGP key at http://www.hutnick.com/pgp
> 
> --
> SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> Archives: http://www.squirrelmail.org/plug_archives.php 
> Unsubscribe: http://www.squirrelmail.org/plug_admin.php 
> 

Re: Mail Filter Plugin request

[Peter H. <pe...@hu...>]

Let me start by saying that I am not absolutely sure about any of this.

My understanding is that mail works something like this:


MUA (SM, Outlook, etc.) -----> MTA (sendmail, qmail, etc.)@ inernet @--

---->MTA (at receiving end)----> LDA (procmail, mail, etc.) ----> mailspool--

----|--->MUA
    |or
    |
    ---->pop/imap--->MUA

That is to say, I don't think that sendmail normally delivers to the spool.

In fact, RedHat uses procmail out of the box, whether or not you set up a
.procmailrc.

-Peter


> I think this is very desireable, especially because it means all the
> filtering is done before SM even sees the mail, and that means SM doesn't
> have to make tons of extra connections to the IMAP server. One question
> though: This means administrators have to make their SMTP server use
> procmail, rather than just deliver the mail directly to the mailbox,
> correct? Or does procmail work on the users mailbox?
>
> > Mail filtering is one of the primary reasons that the plugin architecture
> was
> > implemented.
> >
> > Mail filtering really belongs in the MDA.  That said, there is an extremly
> > powerful MDA that does all the things you want and much more.  Procmail.
> >
> > It seems that an optional component for SM could be devised, that would
> allow
> > users to configure their .procmailrc (with permissions set to 720 and
> group set
> > to the webserver's gid (of course this would allow anyone who owned the
> > webserver to change email filtering, but I think that is a tolerable
> risk.))
> > from within SM, but still allow fitering to be done at the correct place.
> >
> > This would reduce the amount of repeated effort and would build upon the
> > extensive work of the Procmail folks.
> >
> > What do you all think?
> >
> > -Peter
> >
> >
> > > I need a way to filter by this header pretty bad...some emails I get can
> > > only be identified that way.  I'd be *very* greatful for it.
> > >
> > > As far as future requests?  Well I have a few of those too :)
> >

--
Get my PGP key at http://www.hutnick.com/pgp

Re: Mail Filter Plugin request

[Joshua P. <par...@of...>]

I think this is very desireable, especially because it means all the 
filtering is done before SM even sees the mail, and that means SM doesn't 
have to make tons of extra connections to the IMAP server. One question 
though: This means administrators have to make their SMTP server use 
procmail, rather than just deliver the mail directly to the mailbox, 
correct? Or does procmail work on the users mailbox?

> Mail filtering is one of the primary reasons that the plugin architecture 
was
> implemented.
> 
> Mail filtering really belongs in the MDA.  That said, there is an extremly
> powerful MDA that does all the things you want and much more.  Procmail.
> 
> It seems that an optional component for SM could be devised, that would 
allow
> users to configure their .procmailrc (with permissions set to 720 and 
group set
> to the webserver's gid (of course this would allow anyone who owned the
> webserver to change email filtering, but I think that is a tolerable 
risk.))
> from within SM, but still allow fitering to be done at the correct place.
> 
> This would reduce the amount of repeated effort and would build upon the
> extensive work of the Procmail folks.
> 
> What do you all think?
> 
> -Peter
> 
> 
> > I need a way to filter by this header pretty bad...some emails I get can
> > only be identified that way.  I'd be *very* greatful for it.
> >
> > As far as future requests?  Well I have a few of those too :)
> 
> 
> --
> SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> Archives: http://www.squirrelmail.org/plug_archives.php 
> Unsubscribe: http://www.squirrelmail.org/plug_admin.php 
> 

Re: Mail Filter Plugin request

[Peter H. <pe...@hu...>]

Mail filtering is one of the primary reasons that the plugin architecture was
implemented.

Mail filtering really belongs in the MDA.  That said, there is an extremly
powerful MDA that does all the things you want and much more.  Procmail.

It seems that an optional component for SM could be devised, that would allow
users to configure their .procmailrc (with permissions set to 720 and group set
to the webserver's gid (of course this would allow anyone who owned the
webserver to change email filtering, but I think that is a tolerable risk.))
from within SM, but still allow fitering to be done at the correct place.

This would reduce the amount of repeated effort and would build upon the
extensive work of the Procmail folks.

What do you all think?

-Peter


> I need a way to filter by this header pretty bad...some emails I get can
> only be identified that way.  I'd be *very* greatful for it.
>
> As far as future requests?  Well I have a few of those too :)

Mail Filter Plugin request

[Casey A. S. <cs...@ai...>]

X-Mailing-List: <km...@ma...>

I need a way to filter by this header pretty bad...some emails I get can 
only be identified that way.  I'd be *very* greatful for it.

As far as future requests?  Well I have a few of those too :)

Something like these choices:

DROPDOWN I        DROPDOWN II         INPUT FIELD   HREFS
----------        -----------         -----------   -----
From              Contains            whatever      AND
To                Does not contain                  OR
CC                Equals
To or CC
Reply-To
<custom header>

and underneath a:

Checkboxes        INPUT FIELD II
------------      --------------
[ ]Forward To     Entry box
[ ]Transfer To    Entry box
etc.

Shown like this:

|  Dropdown I  |  Dropdown II  |  Input Field  |  and/or   <--hrefs
THEN
|  CheckboxArray  |

If you clicked 'and' on the first row, the page would reload like this:

Dropdown I  |  Dropdown II  |  Input Field  |  AND
Dropdown I  |  Dropdown II  |  Input Field  |  and/or   <--hrefs
THEN
|  CheckboxArray  |

...and so on, same thing for the lower line.  Underneath all of this should 
be a simple link that says 'custom header(s)' or something, where the 
Dropdown I would become a Text-Entry field so that I could enter custom 
headers.

Hell, if anybody's willing to go through that much trouble, I'd pay for 
it :)

I'd be able to sit down and with a couple filters say, Well, if an email 
comes from X-Mailing-List containing kmail@, but not having a From field 
containing cshobe@, then forward it to my work account and delete the 
original.  Oh, and if it has my name in the CC, hold on to a copy of that 
just in case.  Put it a folder called "Important"

This would be done as:

|  X-Mailing List  |  Contains          |  kmail@   |  and
|  From            |  Does Not Contain  |  cshobe@  |  and
|  CC              |  Does Not Contain  |  cshobe@  |
THEN
[X]Forward To     cs...@ai...
[X]Transfer To    Trash

|  X-Mailing List  |  Contains          |  kmail@   |  and
|  CC              |  Contain           |  cshobe@  |
THEN
[ ]Forward To     cs...@ai...
[X]Transfer To    Important

Please contact me if you think this is a possibility...

-- 
Casey Allen Shobe
cs...@ai...
http://aixos.net

**Using AixOS.net Webmail Interface**

WARNING!!!---abook_import_export

[Lewis B. <lbe...@ab...>]

This weekend XS4ALL discovered a vulnerability in the import/export plugin.
This is a major jole that allows most any file on your system to be read. Until
this is resolved I strongly recommend removing this plugin and deleting it.

I will be working on a resolution. If someone wants to help with this I would
gladly take the assistance. I expect a fix in a couple of days.

-- 

--
Lewis Bergman
Texas Communications
4309 Maple St.
Abilene, TX 79602
915-695-6962

Mail-Fetch 0.3

[Joshua P. <par...@of...>]

Hello all,

The latest MF is now available. It now has support for 'leave mail on 
server' and uses the POP3 UIDL command to determine what the last message 
it downloaded was, and which messages it should download.

I've only tested this a few times, so YMMV. Please let me know of any 
problems. I'm almost positive you won't lose any mail because of MF, more 
likely is that you will get messages more than once.

Anyway, if there are any bugs or comments, please let me know. I'm going to 
start working on other things now if there are no problems with MF, so if 
someone wants to start working on supporting multiple servers, IMAP, or 
checking mail on startup, please do.

OH, BTW, Tyler, I replaced your POP3 parsing code with a POP3 object class 
I found at thewebmasters.net. I didn't go out searching for it, but I ran 
accross it and thought it would be useful. It turns out it made the code 
much shorter and simpler. ;)

-Josh

The plugin is available at the link below. Please update the plugins page!

http://www.offthehill.org/mail_fetch-0.3.tar.gz

Re: Plugin: Mail_fetch 0.2

[Tyler A. <ty...@bo...>]

[UIDL]
> Anyway, I've been experimenting, and I have mf getting the UIDL
> of the last message, I just need to stick a SavePref() call in 
> so it gets saved.
> 
> The pain is going to be writing a FindFirstMessage($pop_stream, $uidl)
> that  returns: either 1 if the saved uidl is not found in the list of
> messages,  or the uidl's message number + 1 if it is.

What might work for you is something like this:

- Find all UIDLs of each message
- Get list of UIDLs from last fetch (or none if not available)
- for each message in old list
  - If it is in the new list, don't download that message
- for each message in the new list
  - if it isn't marked as "don't download", then download
  - optionally delete
- save new list of UIDLs for the next fetch.

This way people can delete random messages in the box (including the most recent), and the mail fetch thing should still work fine...  right?

-- 
Tyler Akins                    ty...@bo...

Re: Plugin: Mail_fetch 0.2

[Joshua P. <par...@of...>]

> I like the changes you made to the Mail_fetch plugin.  I just ran out of 
time.  I still don't have a lot, but it's cool that you are running with 
the idea.
> 

Well, I know its not the 'idea' solution, but it seems to be the best 
option right now. ;)

> I would like to allow an infinite amount of other servers, each with 
their own settings as to whether to delete the messages upon downloading, 
the username, and the password.
> 

I agree, and I noticed you had a copy of Luke's filtering code in the mf 
directory.. I didn't feel like dealing with it right away, but its a good 
idea. Its also a pain to get an overall view of the code when your 
programming with ae on a terminal, rather than a nice editor on a gui, so I 
hesitate to make large code changes. Please don't suggest emacs, I hate it.
:)

> I don't think that having the user pick which messages are deleted is 
>wise, since it would be a big pain when you have ten servers with lots of 
>messages and each one prompts you for which ones to delete and download.  
>It would be easier to just have a global kind of thing.
>

Oops, sorry, we are in agreement here, if my README changes indicated that 
I wanted to let the user choose message by message, its wrong (It was very 
late)... I meant for it to be a server by server option. BTW, I finished 
this already (delete or leave on server), but I'm saving it till I've 
finished the UIDL stuff.

> Play with the UIDL command's output and try that, but I think that those 
> things might be messed with if you also access that account with IMAP.  
>Not sure, but my little pop mail client for my palm pilot sure screams 
>bloody murder when I try it.

From what I understand from reading the POP3 RFC's, UIDL is entirely client 
side. I'm not sure how an IMAP access would mess with it at all, but 
perhaps it does. If your palm pop client uses the pop3 LAST command, I 
think that is server-side, so I could see how that would interact badly. 
I'm not really sure how to do it, and I don't want to get into the science 
of writing a good mail client (um, a mail-client inside a mail-client... 
creepy.... soon MF will have plugins....) Anyway, I've been experimenting, 
and I have mf getting the UIDL of the last message, I just need to stick a 
SavePref() call in so it gets saved.

The pain is going to be writing a FindFirstMessage($pop_stream, $uidl) that 
returns: either 1 if the saved uidl is not found in the list of messages, 
or the uidl's message number + 1 if it is.

Re: Plugin: Mail_fetch 0.2

[Tyler A. <ty...@bo...>]

I like the changes you made to the Mail_fetch plugin.  I just ran out of time.  I still don't have a lot, but it's cool that you are running with the idea.

:-)

About the things mentioned in the README file ...

I would like to allow an infinite amount of other servers, each with their own settings as to whether to delete the messages upon downloading, the username, and the password.

I don't think that having the user pick which messages are deleted is wise, since it would be a big pain when you have ten servers with lots of messages and each one prompts you for which ones to delete and download.  It would be easier to just have a global kind of thing.

Play with the UIDL command's output and try that, but I think that those things might be messed with if you also access that account with IMAP.  Not sure, but my little pop mail client for my palm pilot sure screams bloody murder when I try it.

-- 
Tyler Akins                    ty...@bo...

Re: Plugin: Mail_fetch 0.2

[Tyler A. <ty...@bo...>]

> Also, I'm trying to implement storing the UIDL of the last-message 
> downloaded for the mail_fetch plugin, so that a "leave mail on server" 
> option can be added. Tyler, I hope you don't mind me hacking with 
> mail_fetch.

Not at all.

-- 
Tyler Akins                    ty...@bo...

Re: Plugin: Mail_fetch 0.2

[Joshua P. <par...@of...>]

I was just reading the fetchmail man page. There are three problems:

1) .fetchmailrc must have at most permissions of 710
2) fetchmail must run as the user who's .fetchmailrc file you are reading.
3) Write permissions to the users's home directory. This can be solved by 
putting the file under group control of www-data (or nobody, depending), 
with write access only.

It seems that a completely new utility (or a major hack of fetchmail) would 
be required to do what is needed, namely perform pop3/imap retrieval server-
side, for all users.

Also, I'm trying to implement storing the UIDL of the last-message 
downloaded for the mail_fetch plugin, so that a "leave mail on server" 
option can be added. Tyler, I hope you don't mind me hacking with 
mail_fetch.

-Josh

> From what I've ready, if the permissions on .fetchmailrc are not 400, 
> fetchmail will not use the file... :( I'll check into it though. Its a 
> possibility.
> 
> You could use FTP to upload the file and possibly change it's mode to 400 
(depending on the FTP server).  You just need to make sure PHP is compiled 
with --enable-ftp to use the cool functions.
> 
> -- 
> Tyler Akins                    ty...@bo...
> 
> --
> SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> Archives: http://www.squirrelmail.org/plug_archives.php 
> Unsubscribe: http://www.squirrelmail.org/plug_admin.php 
> 

Re: Plugin: Mail_fetch 0.2

[Tyler A. <ty...@bo...>]

From what I've ready, if the permissions on .fetchmailrc are not 400, 
fetchmail will not use the file... :( I'll check into it though. Its a 
possibility.

You could use FTP to upload the file and possibly change it's mode to 400 (depending on the FTP server).  You just need to make sure PHP is compiled with --enable-ftp to use the cool functions.

-- 
Tyler Akins                    ty...@bo...

Re: Plugin: Mail_fetch 0.2

[Chris W. <c.d...@re...>]

How about using FTP to upload a .fetchmailrc generated by PHP? I did 
something like this for .forward and also hacked the filters plugin to 
generate an Exim filters file. I'm not sure whether the FTP would set the 
file permissions to the satisfaction of fetchmail, though. I prefer to 
restrict IMAP to the ~/mail directory.

Chris

On Wed, 1 Nov 2000 09:51:56 -0500 (EST) Joshua Pollak 
<par...@of...> wrote:

> >From what I've ready, if the permissions on .fetchmailrc are not 400, 
> fetchmail will not use the file... :( I'll check into it though. Its a 
> possibility.
> 
> > > I really, really tried to use fetchmail to solve this problem, but I 
> > want 
> > > each user to be able to configure their own .fetchmailrc file, and 
> > then 
> > > have fetchmail run transparently to them all the time (IE, via a 
> > daemon). I 
> > > can't figure out a secure way to have fetchmail use each users own 
> > > ~/.fetchmailrc, and having one huge monolithic /etc/fetchmailrc is 
> > crazy! 
> > 
> > How about:
> > 
> > [peter@wherever /home/peter]$ls -la
> > -rw--w----   1 peter   nobody   275 Oct  4 09:23 .fetchmailrc
> >      ^-------------------^
> >                |=> Nobody (ie the webserver and, by 
> >                    extension, PHP) may write to it.
> > 
> > The obvious problem with this is administrative overhead.
> > 
> > Clearly this would have to be set up by hand (by "advanced" users with 
> > shell access or the admin) or some sort of "tool" would need to come 
> > with the plugin (smfetchmailusersetup.pl anyone?)
> > 
> > -Peter
> > 
> > --
> > SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> > Archives: http://www.squirrelmail.org/plug_archives.php 
> > Unsubscribe: http://www.squirrelmail.org/plug_admin.php 
> > 
> 
> 
> --
> SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> Archives: http://www.squirrelmail.org/plug_archives.php 
> Unsubscribe: http://www.squirrelmail.org/plug_admin.php 

--+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+--
Christopher Wakelin,                                c.d...@re...
IT Services Centre, The University of Reading,       Tel: +44 (0)118 931 6630
Whiteknights, Reading, RG6 2AF, UK                   Fax: +44 (0)118 975 3094

Re: Plugin: Mail_fetch 0.2

[Joshua P. <par...@of...>]

From what I've ready, if the permissions on .fetchmailrc are not 400, 
fetchmail will not use the file... :( I'll check into it though. Its a 
possibility.

> > I really, really tried to use fetchmail to solve this problem, but I 
> want 
> > each user to be able to configure their own .fetchmailrc file, and 
> then 
> > have fetchmail run transparently to them all the time (IE, via a 
> daemon). I 
> > can't figure out a secure way to have fetchmail use each users own 
> > ~/.fetchmailrc, and having one huge monolithic /etc/fetchmailrc is 
> crazy! 
> 
> How about:
> 
> [peter@wherever /home/peter]$ls -la
> -rw--w----   1 peter   nobody   275 Oct  4 09:23 .fetchmailrc
>      ^-------------------^
>                |=> Nobody (ie the webserver and, by 
>                    extension, PHP) may write to it.
> 
> The obvious problem with this is administrative overhead.
> 
> Clearly this would have to be set up by hand (by "advanced" users with 
> shell access or the admin) or some sort of "tool" would need to come 
> with the plugin (smfetchmailusersetup.pl anyone?)
> 
> -Peter
> 
> --
> SquirrelMail Plugins Mailing List (http://www.squirrelmail.org) 
> Archives: http://www.squirrelmail.org/plug_archives.php 
> Unsubscribe: http://www.squirrelmail.org/plug_admin.php 
> 

Re: Plugin: Mail_fetch 0.2

[Peter H. <pe...@hu...>]

> I really, really tried to use fetchmail to solve this problem, but I 
want 
> each user to be able to configure their own .fetchmailrc file, and 
then 
> have fetchmail run transparently to them all the time (IE, via a 
daemon). I 
> can't figure out a secure way to have fetchmail use each users own 
> ~/.fetchmailrc, and having one huge monolithic /etc/fetchmailrc is 
crazy! 

How about:

[peter@wherever /home/peter]$ls -la
-rw--w----   1 peter   nobody   275 Oct  4 09:23 .fetchmailrc
     ^-------------------^
               |=> Nobody (ie the webserver and, by 
                   extension, PHP) may write to it.

The obvious problem with this is administrative overhead.

Clearly this would have to be set up by hand (by "advanced" users with 
shell access or the admin) or some sort of "tool" would need to come 
with the plugin (smfetchmailusersetup.pl anyone?)

-Peter

Plugin: Mail_fetch 0.2

[Joshua P. <par...@of...>]

Hello,

Well, you guys probably think I can't code PHP after that huge error I made 
yesterday, but I'd like to present some code for your rejection anyway.

I have hacked around with Mail Fetch, and the new version is available at:

http://www.offthehill.org/mail_fetch.2.tar.gz

It now has an options page that saves the server/user/password, and 
clicking fetch just grabs the email without prompting the user. It also 
deletes the mail off the pop server, but only if it was sucessful in adding 
it to the Squirrelmail IMAP server.

I've updated the README file, and added some ideas to the TODO list.

I don't know how to have a pop client remember the last message it 
downloaded, etc, so that it can download new messages without downloading 
old ones, but when I figure that out, I'll implement it (if someone doesn't 
beat me too it) so mail_fetch can have a "leave mail on server" option.

Oh, and so we can rekindle the old 'plugin vs. fetchmail' thread:

I really, really tried to use fetchmail to solve this problem, but I want 
each user to be able to configure their own .fetchmailrc file, and then 
have fetchmail run transparently to them all the time (IE, via a daemon). I 
can't figure out a secure way to have fetchmail use each users own 
~/.fetchmailrc, and having one huge monolithic /etc/fetchmailrc is crazy! 
If anyone can help me with a suggestion for this, I'll start working on a 
SM plugin to configure fetchmail.

-Josh

Re: Spell Checking Bug

[Konstantin R. <gr...@re...>]

On Thu, Oct 19, 2000 at 05:00:01PM -0700, Melissa Anderson wrote:
> Mostly an FYI--With Netscape 4.6 on the Macintosh, when SpellCheck is
> complete, the replacement text gets stuffed into the Subject: line instead
> of the message body.  

Hmm... This is interesting. I mean, disgusting... I will take a
look. Would you care to run some tests if I send them to you? I don't have
a Mac available, unfortunately...

-- 
 0>  Konstantin Riabitsev   -> te...@ni...
/ )  Nicodemus Project Tech -> http://www.nicodemusproject.com/
 ~   XMMS playing -> Aerosmith - I Don't Want to Miss a Thing

Spell Checking Bug

[Melissa A. <and...@eu...>]

Mostly an FYI--With Netscape 4.6 on the Macintosh, when SpellCheck is
complete, the replacement text gets stuffed into the Subject: line instead
of the message body.  

Plugin Retrieve User Data bug fixed

[Ralf K. <ra...@ab...>]

Hello,
fixed a bug in my plugin which prevented users without a preferences
file from login. Other parts of the plugin work stable in our environment.
Version changed from 0.1 to 0.2.
Regards,
Ralf

Filters Plugins Bug

[<jo...@se...>]

Hi,

I found that Filters plugins fail to move message to the folder that contain
"[" or "]". The example if I define the rule "To or CC = squir" -> "Move to
folder [SquirrelMail]", then it just do nothing.

I don't know if it's bad idea to create folder w/ "[","]" in the name.
but SquirrelMail allow to do that.

btw, How does the plugins move messages ? (sorry, haven't look
at the code yet :-). If it simply insert message in the new box and then del.
message in the original box, then I think it should be a problem on the quota.

Regards,
Joomy.

Mail Fetch Plugin (pre-release beta)

[Tyler A. <ty...@bo...>]

This plugin ONLY steals messages from POP servers.  It doesn't delete.

It also isn't "release quality" yet, since I want a dozen more changes before I want it submitted.  It is here just for everyone's use -- for people who always wanted this kind of functionality.

-- 
Tyler Akins                    ty...@bo...

SquirrelSpell-0.1.1.tar.gz

[Konstantin R. <gr...@re...>]

This is SquirrelSpell-0.1.1. Minor changes, but added instructions on
how to make it work with Aspell (a much better spellchecker, but still 
lacking a good international support that ispell has). 

-- 
 0>  Konstantin Riabitsev   -> te...@ni...
/ )  Nicodemus Project Tech -> http://www.nicodemusproject.com/
 ~   

attachment_common plugin

[Tyler A. <ty...@bo...>]

This plugin now finds application/octet-stream files and tries to determine the correct mime type (for ones it can view) based on the extension...  just in case some dumb mail program tried to send you a file.

To use it, you need today's CVS (or later).

-- 
Tyler Akins                    ty...@bo...

New plugin: password_forget

[Tyler A. <ty...@bo...>]

This plugin changes the login form to use random names for the text and password boxes, and then changes them back to normal with webmail.php.

It is released as a plugin because I didn't want to add it as a standard feature to SquirrelMail.  If you want it, then you add it.  :-)

It's a pretty lame plugin, and I don't see it changing much in the future.  It has no options, nothing to configure, and it has only about a dozen lines or so of "real" code.

I also haven't tested it with IE nor Mozilla, but it should foil their methods of remembering passwords.

-- 
Tyler Akins                    ty...@bo...