mailserver
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 22
qinstall-src 2.0
qinstall-src is a source package collection along with a bash script that helps an administrator to compile a mail server. more>>
For those who want to build their own mailserver from sources on different GNU/Linux distributions like Slackware, Gentoo, CentOS, SuSe, Fedora Core or Debian, we created an universal package called qinstall-src.
qinstall-src is a source package collection along with a bash script that helps an administrator to compile, configure, install and run an e-mail server, based on qmail, together with all the programs required to run properly.
Main features:
- all perl modules required for optimum runtime;
- user administration web interface(qmailadmin);
- console-based user and domain administration (vpopmail, cqadmin);
- a bash script that eases the administration of queue pending messages (qmHandle);
- personalized webmail (SSL/TLS), activated quota, password changer (squirrelmail);
- ESMTP/SMTP, IMAP/POP3 SSL services activated by default (qmail, courier imap);
- e-mail autoresponder (autorespond);
- antivirus and antispam software (clamav, spamassassin);
- email filters (procmail);
- other programs that help running the e-mail server at optimum speed;
qinstall-src is tested on Slackware, Gentoo, Fedora Core, CentOS, openSuSe and Debian.
Enhancements:
- Many packages have been upgraded to the latest version.
- All packages have been ported to Bluewhite64 Linux (64-bit).
<<lessqinstall-src is a source package collection along with a bash script that helps an administrator to compile, configure, install and run an e-mail server, based on qmail, together with all the programs required to run properly.
Main features:
- all perl modules required for optimum runtime;
- user administration web interface(qmailadmin);
- console-based user and domain administration (vpopmail, cqadmin);
- a bash script that eases the administration of queue pending messages (qmHandle);
- personalized webmail (SSL/TLS), activated quota, password changer (squirrelmail);
- ESMTP/SMTP, IMAP/POP3 SSL services activated by default (qmail, courier imap);
- e-mail autoresponder (autorespond);
- antivirus and antispam software (clamav, spamassassin);
- email filters (procmail);
- other programs that help running the e-mail server at optimum speed;
qinstall-src is tested on Slackware, Gentoo, Fedora Core, CentOS, openSuSe and Debian.
Enhancements:
- Many packages have been upgraded to the latest version.
- All packages have been ported to Bluewhite64 Linux (64-bit).
Download (MB)
Added: 2007-07-20 License: GPL (GNU General Public License) Price:
530 downloads
Phpfw 0.4
Phpfw is a framework for PHP that provides a base on which various database backed applications can be built. more>>
Phpfw is a framework for PHP that provides a base on which various database backend applications can be built. Phpfw project allows for easy creation of CRUD applications - apps where most of the code is focussed on Create Read Update Delete operations on the database. It uses MVC-ish patterns to allow for simpler and cleaner organization of code.
Phpfw leverages popular PHP libraries so as to avoid reinventing the wheel. For example, the database abstraction layer is a thin wrapper that supports ADOdb and ADOdb Lite. Hence, Phpfw is able to support multiple databases thanks to these excellent libraries.
Phpfw requires minimal configuration. All the database information is directly obtained from the database itself. The configuration file is a simple .ini file and is adequately commented to explain the different elements.
Phpfw comes built in with an elementary templating class to generate HTML output. Further it also supports templating frameworks like Smarty and PHPTAL. The combination of these templating facilities provides adequate power to generate simple to complex output.
Phpfw is the result of several PHP projects I undertook over the years. It grew inside active projects and has finally taken a life of its own. It has been written from scratch based on all the code that was written over the years with a focus on simplifying the process of creating new applications with minimal effort. I hope this work proves useful to those of you who would like to put together applications quickly and easily.
Enhancements:
- Several enhancements were made in the core API such as AJAX support, database schema auto-load and optional database usage.
- New modules include Config, MailServer, and PelWrap.
- Enhancements were made to existing modules to allow login from file.
<<lessPhpfw leverages popular PHP libraries so as to avoid reinventing the wheel. For example, the database abstraction layer is a thin wrapper that supports ADOdb and ADOdb Lite. Hence, Phpfw is able to support multiple databases thanks to these excellent libraries.
Phpfw requires minimal configuration. All the database information is directly obtained from the database itself. The configuration file is a simple .ini file and is adequately commented to explain the different elements.
Phpfw comes built in with an elementary templating class to generate HTML output. Further it also supports templating frameworks like Smarty and PHPTAL. The combination of these templating facilities provides adequate power to generate simple to complex output.
Phpfw is the result of several PHP projects I undertook over the years. It grew inside active projects and has finally taken a life of its own. It has been written from scratch based on all the code that was written over the years with a focus on simplifying the process of creating new applications with minimal effort. I hope this work proves useful to those of you who would like to put together applications quickly and easily.
Enhancements:
- Several enhancements were made in the core API such as AJAX support, database schema auto-load and optional database usage.
- New modules include Config, MailServer, and PelWrap.
- Enhancements were made to existing modules to allow login from file.
Download (0.028MB)
Added: 2007-06-24 License: MIT/X Consortium License Price:
853 downloads
Openmailadmin 1.0.0
Openmailadmin is a little administration interface to every complete IMAP mail server daemon. more>>
Openmailadmin is a little administration interface to every complete IMAP mail server daemon. Openmailadmin supports every feature IMAP provides, and fits in most MTA configurations.
A key feature is the non-standard, generic administration hierarchy which not only seperates "normal users" from "administrators", but enables the mailserver-master to create instances between them.
You will be able to let other users create their own sub-users and thus either share a single mail server between different organizations or project your companys employee structure. It excels with features such as regex addresses and folder ACL management.
Installation:
1. Copy all the files into your DocumentRoot-folder.
2. Modify following files by changing usernames and passwords:
- samples/pam/imap
- inc/database.sql
And either of these:
- samples/postfix/*
- samples/oma_mail.daimon.*
3. Create the required database and users in MySQL. Modify database.sql and have it executed inside the new database.
4. Copy samples/pam/imap settings to your /etc/pam.d folder
{{{
chmod 600 samples/pam/imap
cp samples/pam/imap /etc/pam.d/imap
ln -s /etc/pam.d/imap /etc/pam.d/pop
ln -s /etc/pam.d/imap /etc/pam.d/sieve
ln -s /etc/pam.d/imap /etc/pam.d/smtp
}}}
5. For security reasons, remove these files from your DocumentRoot-folder:
{{{
rm inc/database.sql
rm -r samples/pam
rm samples/oma_mail.daimon.* samples/postfix
}}}
<<lessA key feature is the non-standard, generic administration hierarchy which not only seperates "normal users" from "administrators", but enables the mailserver-master to create instances between them.
You will be able to let other users create their own sub-users and thus either share a single mail server between different organizations or project your companys employee structure. It excels with features such as regex addresses and folder ACL management.
Installation:
1. Copy all the files into your DocumentRoot-folder.
2. Modify following files by changing usernames and passwords:
- samples/pam/imap
- inc/database.sql
And either of these:
- samples/postfix/*
- samples/oma_mail.daimon.*
3. Create the required database and users in MySQL. Modify database.sql and have it executed inside the new database.
4. Copy samples/pam/imap settings to your /etc/pam.d folder
{{{
chmod 600 samples/pam/imap
cp samples/pam/imap /etc/pam.d/imap
ln -s /etc/pam.d/imap /etc/pam.d/pop
ln -s /etc/pam.d/imap /etc/pam.d/sieve
ln -s /etc/pam.d/imap /etc/pam.d/smtp
}}}
5. For security reasons, remove these files from your DocumentRoot-folder:
{{{
rm inc/database.sql
rm -r samples/pam
rm samples/oma_mail.daimon.* samples/postfix
}}}
Download (0.064MB)
Added: 2007-06-01 License: GPL (GNU General Public License) Price:
878 downloads
Cft 0.2.1
Cft project watches a system administrator as she makes changes to a system. more>>
Its basic principle is heavily influenced by Gnomes Sabayon. Instead of the desktop though, cft is focused on traditional system administrators and how they maintain machines, mostly with command line tools.
Cft uses puppet as its backbone for expressing the configuration of a system, and for understanding in greater detail what changes the admin has made to the system. Sites that already use puppet to manage their configuration can easily integrate cfts output into the overall site configuration; for sites that use some other means of configuration management, cfts output provides a complete record of changes made and serves as a good starting point of integrating the changes back into the sites configuration.
Example:
In lieu of colorful screenshots, a simple example will explain in more detail how cft works: cft organizes changes in sessions to let the user better indicate what aspect of the system they are fixing (the webserver, the mailserver etc.) A simple session to fix the configuration of postfix and to start and enable the service might entail root running the following commands:
tux:1# cft begin postfix
tux:2# yum -y install postfix
tux:3# vi /etc/postfix/main.cf
tux:4# chkconfig postfix on
tux:5# service postfix start
tux:6# cft finish postfix
Note that the user only had to issue two additonal commands to begin and finish the session, everything else in the session is exactly the same as if the changes had been made without cft. The command cft begin postfix tells cft to start a session called postfix, and the last command cft finish postfix tells it to do the final bookkeeping necessary for analysing the results.
Once the commands above have been issued, running cft manifest postfix will print the changes in the form of a puppet manifest:
tux:6# cft manifest postfix
class postfix {
package { postfix.i386:
ensure => 2:2.3.3-2
}
service { postfix:
enable => true,
pattern => postfix,
ensure => running
}
file { /etc/aliases.db:
group => smmsp,
owner => root,
mode => 0640,
source => /tmp/cft/postfix/after/etc/aliases.db
}
file { /etc/postfix/main.cf:
group => root,
owner => root,
mode => 0644,
source => /tmp/cft/postfix/after/etc/postfix/main.cf
}
}
This manifest tells puppet that puppet should enable and start the postfix service, and that the two files should be copied from the location mentioned as the source and receive the given owner, group, and mode. cft takes care of copying all modified files into a safe location so that they can be copied off the machine into a central location. The mention of the file aliases.db is somewhat spurious: it gets automatically recreated by the init script for postfix, and cft treats it exactly as if the user had created the file.
To facilitate moving the changes onto a central serevr, cft can also convert a session into a tarball that contains both the puppet manifest and all the files that are mentioned in it, in this case aliases.db and main.cf. Fancier, more convenient methods of integrating changes back into a central puppet server are planned for the future.
<<lessCft uses puppet as its backbone for expressing the configuration of a system, and for understanding in greater detail what changes the admin has made to the system. Sites that already use puppet to manage their configuration can easily integrate cfts output into the overall site configuration; for sites that use some other means of configuration management, cfts output provides a complete record of changes made and serves as a good starting point of integrating the changes back into the sites configuration.
Example:
In lieu of colorful screenshots, a simple example will explain in more detail how cft works: cft organizes changes in sessions to let the user better indicate what aspect of the system they are fixing (the webserver, the mailserver etc.) A simple session to fix the configuration of postfix and to start and enable the service might entail root running the following commands:
tux:1# cft begin postfix
tux:2# yum -y install postfix
tux:3# vi /etc/postfix/main.cf
tux:4# chkconfig postfix on
tux:5# service postfix start
tux:6# cft finish postfix
Note that the user only had to issue two additonal commands to begin and finish the session, everything else in the session is exactly the same as if the changes had been made without cft. The command cft begin postfix tells cft to start a session called postfix, and the last command cft finish postfix tells it to do the final bookkeeping necessary for analysing the results.
Once the commands above have been issued, running cft manifest postfix will print the changes in the form of a puppet manifest:
tux:6# cft manifest postfix
class postfix {
package { postfix.i386:
ensure => 2:2.3.3-2
}
service { postfix:
enable => true,
pattern => postfix,
ensure => running
}
file { /etc/aliases.db:
group => smmsp,
owner => root,
mode => 0640,
source => /tmp/cft/postfix/after/etc/aliases.db
}
file { /etc/postfix/main.cf:
group => root,
owner => root,
mode => 0644,
source => /tmp/cft/postfix/after/etc/postfix/main.cf
}
}
This manifest tells puppet that puppet should enable and start the postfix service, and that the two files should be copied from the location mentioned as the source and receive the given owner, group, and mode. cft takes care of copying all modified files into a safe location so that they can be copied off the machine into a central location. The mention of the file aliases.db is somewhat spurious: it gets automatically recreated by the init script for postfix, and cft treats it exactly as if the user had created the file.
To facilitate moving the changes onto a central serevr, cft can also convert a session into a tarball that contains both the puppet manifest and all the files that are mentioned in it, in this case aliases.db and main.cf. Fancier, more convenient methods of integrating changes back into a central puppet server are planned for the future.
Download (3.1MB)
Added: 2007-05-09 License: GPL (GNU General Public License) Price:
901 downloads
DNS::ZoneParse 0.95
DNS::ZoneParse is a Perl module to parse and manipulate DNS Zone Files. more>>
DNS::ZoneParse is a Perl module to parse and manipulate DNS Zone Files.
SYNOPSIS
use DNS::ZoneParse;
my $zonefile = DNS::ZoneParse->new("/path/to/dns/zonefile.db", $origin);
# Get a reference to the MX records
my $mx = $zonefile->mx;
# Change the first mailserver on the list
$mx->[0] = { host => mail.localhost.com,
priority => 10,
name => @ };
# update the serial number
$zonefile->new_serial();
# write the new zone file to disk
open NEWZONE, ">/path/to/dns/zonefile.db" or die "error";
print NEWZONE $zonefile->output();
close NEWZONE;
INSTALLATION
perl Makefile.PL
make
make test
make install
<<lessSYNOPSIS
use DNS::ZoneParse;
my $zonefile = DNS::ZoneParse->new("/path/to/dns/zonefile.db", $origin);
# Get a reference to the MX records
my $mx = $zonefile->mx;
# Change the first mailserver on the list
$mx->[0] = { host => mail.localhost.com,
priority => 10,
name => @ };
# update the serial number
$zonefile->new_serial();
# write the new zone file to disk
open NEWZONE, ">/path/to/dns/zonefile.db" or die "error";
print NEWZONE $zonefile->output();
close NEWZONE;
INSTALLATION
perl Makefile.PL
make
make test
make install
Download (0.009MB)
Added: 2007-04-16 License: Perl Artistic License Price:
925 downloads
Fetchmail 6.3.8
fetchmail is a free, full-featured, robust, well-documented remote-mail retrieval utility. more>>
Fetchmail is a full-featured, robust, well-documented remote-mail retrieval and forwarding utility intended to be used over on-demand TCP/IP links (such as SLIP or PPP connections). Fetchmail supports every remote-mail protocol now in use on the Internet: POP2, POP3, RPOP, APOP, KPOP, all flavors of IMAP, ETRN, and ODMR. It can even support IPv6 and IPSEC.
Fetchmail retrieves mail from remote mail servers and forwards it via SMTP, so it can then be read by normal mail user agents such as mutt, elm(1) or BSD Mail. It allows all your system MTAs filtering, forwarding, and aliasing facilities to work just as they would on normal mail.
Fetchmail offers better security than any other Unix remote-mail client. It supports APOP, KPOP, OTP, Compuserve RPA, Microsoft NTLM, and IMAP RFC1731 encrypted authentication methods including CRAM-MD5 to avoid sending passwords en clair. It can be configured to support end-to-end encryption via tunneling with ssh, the Secure Shell.
Fetchmail can be used as a POP/IMAP-to-SMTP gateway for an entire DNS domain, collecting mail from a single drop box on an ISP and SMTP-forwarding it based on header addresses. (We dont really recommend this, though, as it may lose important envelope-header information. ETRN or a UUCP connection is better.)
Fetchmail can be started automatically and silently as a system daemon at boot time. When running in this mode with a short poll interval, it is pretty hard for anyone to tell that the incoming mail link is not a full-time "push" connection.
Fetchmail is easy to configure. You can edit its dotfile directly, or use the interactive GUI configurator (fetchmailconf) supplied with the fetchmail distribution. It is also directly supported in linuxconf versions 1.16r8 and later.
Fetchmail is fast and lightweight. It packs all its standard features (POP3, IMAP, and ETRN support) in 196K of core on a Pentium under Linux.
Fetchmail is open-source software. The openness of the sources is your strongest possible assurance of quality and reliability.
Main features:
- STARTTLS is supported in both POP and IMAP.
- ESMTP AUTH (RFC 2554) is supported.
- Has the capability of adding trace information to the Received header to faciliate mail filtering by mailserver and remote account.
- Fetchmail now has options to handle SSL certificate validation.
- Fetchmail can be told to fall back to delivering via local sendmail if it cant open port 25.
- Support for AUTH=CRAM-MD5 under POP3, a la RFC2195.
- Support for ODMR (On-Demand Mail Relay), RFC 2645.
- Its now easy to deliver mail to a local LMTP socket.
- The interface option now checks both local and remote interface IPs.
- The plugin facility has been enhanced; %h and %p options are now available to pass in the hostname and service port number.
- Added a dropdelivered option to discard Delivered-To headers. This addresses a problem with using fetchmail and postfix as a relay inside a domain; when postfix sees incoming messages with delivered-to headers looking exactly the same as the ones it adds himself, it bounces the message.
- Added --smtpname to set username and domain portion of SMTP "RCPT TO" command. - Added "from" servers IP address to inserted Received line.
- Fetchmail now runs on BeOS, thanks to David Reid .
- In IMAP, unseen-message counting and indexing is now done by SEARCH UNSEEN at the beginning of each poll or re-poll (rather than with the UNSEEN and RECENT responses and FLAGS queries on individual messages). This significantly cuts down on traffic to and from the server, and gives more reliable results.
- The aka option now matches hostname suffixes, so (for example) saying `aka netaxs.com will match not just netaxs.com but also (say) pop3.netaxs.com and mail.netaxs.com.
- Fetchmail can optionally use the RFC 2177 IDLE extension on an IMAP server that supports it. On IMAP servers that dont, it can simulate it using periodic NOOP commands.
- Fetchmail now recognizes the RFC 2449 extended responses [IN-USE] and [LOGIN-DELAY].
- Fetchmail running in daemon mode now restarts itself quietly when the rc file is touched.
- Following recent court decisions and changes in U.S. federal regulatory policy, hooks for Secure Sockets Layer (SSL) are now part of the main fetchmail distribution. The distribution still contains no actual cryptographic code.
- NTLM support under IMAP, so fetchmail can query Microsoft Exchange servers.
- Expunge option can now be used to break POP3 retrieval into subsessions.
- Support for AUTH=CRAM-MD5 under IMAP, a la RFC2195.
<<lessFetchmail retrieves mail from remote mail servers and forwards it via SMTP, so it can then be read by normal mail user agents such as mutt, elm(1) or BSD Mail. It allows all your system MTAs filtering, forwarding, and aliasing facilities to work just as they would on normal mail.
Fetchmail offers better security than any other Unix remote-mail client. It supports APOP, KPOP, OTP, Compuserve RPA, Microsoft NTLM, and IMAP RFC1731 encrypted authentication methods including CRAM-MD5 to avoid sending passwords en clair. It can be configured to support end-to-end encryption via tunneling with ssh, the Secure Shell.
Fetchmail can be used as a POP/IMAP-to-SMTP gateway for an entire DNS domain, collecting mail from a single drop box on an ISP and SMTP-forwarding it based on header addresses. (We dont really recommend this, though, as it may lose important envelope-header information. ETRN or a UUCP connection is better.)
Fetchmail can be started automatically and silently as a system daemon at boot time. When running in this mode with a short poll interval, it is pretty hard for anyone to tell that the incoming mail link is not a full-time "push" connection.
Fetchmail is easy to configure. You can edit its dotfile directly, or use the interactive GUI configurator (fetchmailconf) supplied with the fetchmail distribution. It is also directly supported in linuxconf versions 1.16r8 and later.
Fetchmail is fast and lightweight. It packs all its standard features (POP3, IMAP, and ETRN support) in 196K of core on a Pentium under Linux.
Fetchmail is open-source software. The openness of the sources is your strongest possible assurance of quality and reliability.
Main features:
- STARTTLS is supported in both POP and IMAP.
- ESMTP AUTH (RFC 2554) is supported.
- Has the capability of adding trace information to the Received header to faciliate mail filtering by mailserver and remote account.
- Fetchmail now has options to handle SSL certificate validation.
- Fetchmail can be told to fall back to delivering via local sendmail if it cant open port 25.
- Support for AUTH=CRAM-MD5 under POP3, a la RFC2195.
- Support for ODMR (On-Demand Mail Relay), RFC 2645.
- Its now easy to deliver mail to a local LMTP socket.
- The interface option now checks both local and remote interface IPs.
- The plugin facility has been enhanced; %h and %p options are now available to pass in the hostname and service port number.
- Added a dropdelivered option to discard Delivered-To headers. This addresses a problem with using fetchmail and postfix as a relay inside a domain; when postfix sees incoming messages with delivered-to headers looking exactly the same as the ones it adds himself, it bounces the message.
- Added --smtpname to set username and domain portion of SMTP "RCPT TO" command. - Added "from" servers IP address to inserted Received line.
- Fetchmail now runs on BeOS, thanks to David Reid .
- In IMAP, unseen-message counting and indexing is now done by SEARCH UNSEEN at the beginning of each poll or re-poll (rather than with the UNSEEN and RECENT responses and FLAGS queries on individual messages). This significantly cuts down on traffic to and from the server, and gives more reliable results.
- The aka option now matches hostname suffixes, so (for example) saying `aka netaxs.com will match not just netaxs.com but also (say) pop3.netaxs.com and mail.netaxs.com.
- Fetchmail can optionally use the RFC 2177 IDLE extension on an IMAP server that supports it. On IMAP servers that dont, it can simulate it using periodic NOOP commands.
- Fetchmail now recognizes the RFC 2449 extended responses [IN-USE] and [LOGIN-DELAY].
- Fetchmail running in daemon mode now restarts itself quietly when the rc file is touched.
- Following recent court decisions and changes in U.S. federal regulatory policy, hooks for Secure Sockets Layer (SSL) are now part of the main fetchmail distribution. The distribution still contains no actual cryptographic code.
- NTLM support under IMAP, so fetchmail can query Microsoft Exchange servers.
- Expunge option can now be used to break POP3 retrieval into subsessions.
- Support for AUTH=CRAM-MD5 under IMAP, a la RFC2195.
Download (1.1MB)
Added: 2007-04-07 License: GPL (GNU General Public License) Price:
932 downloads
Other version of Fetchmail
License:GPL (GNU General Public License)
fetchExc 2.0
fetchExc is a Java utility for fetching mail with WebDAV from MS Exchange 2000/2003 servers. more>>
fetchExc project is java utilily which retrieves mail from your MS Exchange (2000/2003) inbox and forwards it to SMTP server of your choice or mbox type file.
FetchExc uses webDAV (OWA) to retrieve mail either over http or https. This is also means that you administrator must have left Outlook Webaccess available in Exchange in order to get this utility to work.
Although version number is still below 1.0 I consider this program usable in production environment.
There are still many places that should be polished and improved but atleast there havent been major problems in over an half a year. Before you install read installation instructions from below carefully.
Installing:
So far this only covers *nix systems (windows instructions may follow if they are needed)
Extract fetchExc-*.tar.gz or make directory for fetchExc.jar. If you are downloading Jakarta components yourself put them in the same directory as fetchExc.jar.
Create fetchExc.properties file in your home directory. Remember to protect it with chmod 700 (it contains your password). If you took .tar.gz package there should be example included.
ExchangeServer=xxx.dddddd.com
ExchangePath=exchange
ExchangeUser=exuser
MailServer=yyy.dddddd.com
DestinationAddress=user@yyy.dddddd.com
Username=domainuser
Password=domainpassword
Domain=DOMAIN
Delete=false
All=false
Secure=true
FBApath=/exchweb/bin/auth/owaauth.dll
ExchangeServer - Name of your MS Exchange server.
ExchangePath - Exchange path for MS Exchange OutLook WebAccess.
ExchangeUser - Name of you MS Exchange User.
You can test first three properties by making URL out of them: http://xxx.dddddd.com/exchange/exuser. This should give you a Outlook Webaccess Page.
MboxFile - Path and name of mbox-type mail box. This disables MailServer- and DestinationAddress-properties. Be careful with this because Im not 100% sure that file locking works (YMMV). If there are problems let me know. Also success reports would be nice.
MailServer - Name of your SMTP Server which receives forwarded messages. If there is MboxFile defined this property wont be used.
DestinationAddess - Address of recipient of forwarded messages. If there is MboxFile defined this property wont be used.
Username - Username for your windows domain user. It may be same as ExchangeUser but necessarily.
Password - Password for domain user.
Domain - Domain for above user.
Delete - Whether program should delete mail from Inbox or just mark them as read. If Delete is true mail will be deleted after succesful forwarding. Any other value will just mark message as read. While you are configuring other properties I strongly recommend that you use value false for this property.
All - Whether program should real all mail from Inbox or just which are not read yet. If All is true every mail will be read. Any other value will read only unread mail. While you are configuring other properties I strongly recommend that you use value false for this property.
WARNING!!! Dont combine Delete=false and All=true if you are not testing. That will fetch every mail from your Inbox everytime you start the program.
Secure - If value is true program will use https. Any other value will use http. Https should be user whenever possible.
FBApath - Path to form based authentication. If not set defaults to /exchweb/bin/auth/owaauth.dll. This can be found on FBA login page source (hint: search for "destination")
ForceFrom - If this is set to true forwarded mail will be forwarded with address from ForceFromAddr parameter. This only happens when sender address is not valid. For example if there is two From: fields in mail header Exchange can join addresses. NOTE: This may help spam to get through so use carefully.
ForceFromAddr - E-mail address that forwarding server will accept. Only used if ForceFrom is true
NoEightBitMime - If this is true SMTP forwarding doesnt use BODY=8BITMIME. Default is false.
Now you just need to include JRE in you path. If it is in you path you can run program:
java -jar /install/fetchExc/fetchExc.jar
You can now (>0.80) use -p switch to change properties file. For example:
java -jar /install/fetchExc/fetchExc.jar -p test.properties
would run program using properties from test.properties
I use fetchExc with following little shell script and crontab entry so that it keeps fetching mail every two minutes.
fetchExc
#!/bin/bash
export PATH=$PATH:/usr/local/jre/bin
java -jar /install/fetchExc/fetchExc.jar $* >> fetchExc.log 2>> fetchExc.err
If you use this script replace /usr/local/jre/bin with path to your java runtime environment. Same applies to location of your installation on next line.
crontab entry:
*/2 * * * * ~jrauti/bin/fetchExc
Enhancements:
- Java has been changed from 1.4 to 1.5.
- The Jakarta HHTTP client has been upgraded from 2.0 to 3.0.
- Proxying also works with HTTPS.
- Code cleanups.
- A small fix in mbox saving (in Mac OS X, messages were coalesced).
<<lessFetchExc uses webDAV (OWA) to retrieve mail either over http or https. This is also means that you administrator must have left Outlook Webaccess available in Exchange in order to get this utility to work.
Although version number is still below 1.0 I consider this program usable in production environment.
There are still many places that should be polished and improved but atleast there havent been major problems in over an half a year. Before you install read installation instructions from below carefully.
Installing:
So far this only covers *nix systems (windows instructions may follow if they are needed)
Extract fetchExc-*.tar.gz or make directory for fetchExc.jar. If you are downloading Jakarta components yourself put them in the same directory as fetchExc.jar.
Create fetchExc.properties file in your home directory. Remember to protect it with chmod 700 (it contains your password). If you took .tar.gz package there should be example included.
ExchangeServer=xxx.dddddd.com
ExchangePath=exchange
ExchangeUser=exuser
MailServer=yyy.dddddd.com
DestinationAddress=user@yyy.dddddd.com
Username=domainuser
Password=domainpassword
Domain=DOMAIN
Delete=false
All=false
Secure=true
FBApath=/exchweb/bin/auth/owaauth.dll
ExchangeServer - Name of your MS Exchange server.
ExchangePath - Exchange path for MS Exchange OutLook WebAccess.
ExchangeUser - Name of you MS Exchange User.
You can test first three properties by making URL out of them: http://xxx.dddddd.com/exchange/exuser. This should give you a Outlook Webaccess Page.
MboxFile - Path and name of mbox-type mail box. This disables MailServer- and DestinationAddress-properties. Be careful with this because Im not 100% sure that file locking works (YMMV). If there are problems let me know. Also success reports would be nice.
MailServer - Name of your SMTP Server which receives forwarded messages. If there is MboxFile defined this property wont be used.
DestinationAddess - Address of recipient of forwarded messages. If there is MboxFile defined this property wont be used.
Username - Username for your windows domain user. It may be same as ExchangeUser but necessarily.
Password - Password for domain user.
Domain - Domain for above user.
Delete - Whether program should delete mail from Inbox or just mark them as read. If Delete is true mail will be deleted after succesful forwarding. Any other value will just mark message as read. While you are configuring other properties I strongly recommend that you use value false for this property.
All - Whether program should real all mail from Inbox or just which are not read yet. If All is true every mail will be read. Any other value will read only unread mail. While you are configuring other properties I strongly recommend that you use value false for this property.
WARNING!!! Dont combine Delete=false and All=true if you are not testing. That will fetch every mail from your Inbox everytime you start the program.
Secure - If value is true program will use https. Any other value will use http. Https should be user whenever possible.
FBApath - Path to form based authentication. If not set defaults to /exchweb/bin/auth/owaauth.dll. This can be found on FBA login page source (hint: search for "destination")
ForceFrom - If this is set to true forwarded mail will be forwarded with address from ForceFromAddr parameter. This only happens when sender address is not valid. For example if there is two From: fields in mail header Exchange can join addresses. NOTE: This may help spam to get through so use carefully.
ForceFromAddr - E-mail address that forwarding server will accept. Only used if ForceFrom is true
NoEightBitMime - If this is true SMTP forwarding doesnt use BODY=8BITMIME. Default is false.
Now you just need to include JRE in you path. If it is in you path you can run program:
java -jar /install/fetchExc/fetchExc.jar
You can now (>0.80) use -p switch to change properties file. For example:
java -jar /install/fetchExc/fetchExc.jar -p test.properties
would run program using properties from test.properties
I use fetchExc with following little shell script and crontab entry so that it keeps fetching mail every two minutes.
fetchExc
#!/bin/bash
export PATH=$PATH:/usr/local/jre/bin
java -jar /install/fetchExc/fetchExc.jar $* >> fetchExc.log 2>> fetchExc.err
If you use this script replace /usr/local/jre/bin with path to your java runtime environment. Same applies to location of your installation on next line.
crontab entry:
*/2 * * * * ~jrauti/bin/fetchExc
Enhancements:
- Java has been changed from 1.4 to 1.5.
- The Jakarta HHTTP client has been upgraded from 2.0 to 3.0.
- Proxying also works with HTTPS.
- Code cleanups.
- A small fix in mbox saving (in Mac OS X, messages were coalesced).
Download (0.012MB)
Added: 2007-03-28 License: GPL (GNU General Public License) Price:
943 downloads
SiMP 3.5
SiMP (Simple Mail Parser) is a procmail-like mailparser, except that its much more easier to configure. more>>
SiMP (Simple Mail Parser) is a procmail-like mailparser, except that its much more easier to configure. With SiMP you can automatically store incoming mail in seperate folders, remove junkmail, send a reply, forward the mail, etc.
It has been tested with Sendmail and Postfix as a mailserver and Pine as the mailreader, but it is likely that SiMP will work with other mailservers and -clients.
<<lessIt has been tested with Sendmail and Postfix as a mailserver and Pine as the mailreader, but it is likely that SiMP will work with other mailservers and -clients.
Download (0.020MB)
Added: 2007-03-21 License: GPL (GNU General Public License) Price:
951 downloads
SafeRelay 0.0.1
SafeRelay is a certificate authority center, based on OpenSSL. more>>
SafeRelay is a certificate authority center, based on OpenSSL, for network administrators who want to deploy certificates on a LAN (local area network). SafeRelay is written in CURSEL.
You may be thinking of using TLS/SSL and certificates on your LAN for activities like:
configuring intranet web servers to use HTTPS instead of plain HTTP
making LAN users connect over IMAP/SSL or POP3/SSL to your mailserver
letting your LAN users connect to your Sendmail SMTP server using certificate client authentication
having LAN users sign or encrypt their email with S/MIME
client authentication based on certificates for intranet HTTPS webservers
The basic idea is that users tend to forget to make a backup of their certificates.
If the PC of the user crashes, the private key and certificate, can be recovered, from the diskette, by the user without help or intervention from the system or network administrator.
If the user has multiple PCs (e.g. a laptop and desktop), it suffices to simply import the certificate from the diskette on both PCs.
If the diskette is lost by the user, or stolen by another user, or if the diskette suffers from a media error, a new diskette with a new keypair must be prepared for the user.
In any case, by giving the user a diskette with a certificate, the user immediately receives a backup. Any tangible medium would also work. In fact, SafeRelay could allow you to use "cdrecord" and a CD-RW drive instead. For important keys and certificates, you could copy the contents of the diskette onto a read-only medium such as a CD.
<<lessYou may be thinking of using TLS/SSL and certificates on your LAN for activities like:
configuring intranet web servers to use HTTPS instead of plain HTTP
making LAN users connect over IMAP/SSL or POP3/SSL to your mailserver
letting your LAN users connect to your Sendmail SMTP server using certificate client authentication
having LAN users sign or encrypt their email with S/MIME
client authentication based on certificates for intranet HTTPS webservers
The basic idea is that users tend to forget to make a backup of their certificates.
If the PC of the user crashes, the private key and certificate, can be recovered, from the diskette, by the user without help or intervention from the system or network administrator.
If the user has multiple PCs (e.g. a laptop and desktop), it suffices to simply import the certificate from the diskette on both PCs.
If the diskette is lost by the user, or stolen by another user, or if the diskette suffers from a media error, a new diskette with a new keypair must be prepared for the user.
In any case, by giving the user a diskette with a certificate, the user immediately receives a backup. Any tangible medium would also work. In fact, SafeRelay could allow you to use "cdrecord" and a CD-RW drive instead. For important keys and certificates, you could copy the contents of the diskette onto a read-only medium such as a CD.
Download (0.037MB)
Added: 2006-07-14 License: GPL (GNU General Public License) Price:
1198 downloads
Worm Warner 2.3
WormWarner is a tool designed to warn hosts that are probably infected by worms. more>>
WormWarner is a tool designed to warn hosts that are probably infected by worms. This is done by scanning the Apache log files and sending email to the host or the ISP when an worm or attack is detected. Wormwarner started in September 2002 as a small project written in Perl.
Wormwarner has a simple pattern database which makes it easy to add new worm patterns as they appear. Another important feature is the build in rate and mail size control which avoids that wormwarner sends out to much email to an ISP. Wormwarner has also the option to excute external commands, which makes it easy to adapt i.e. firewalls based on the attacks and worms detected by wormwarner.
However there were features requests and the application grown in complexity. The goal of the wormwarner project is to provided users with a powerful and flexible, but benign tool to take action against worms and attacks on their webserver(s).
Enhancements:
- The attack complaint message was changed to a less offensive one.
- "GET /scripts/nsiislog.dll" was added to the attack patterns.
- Various formmail exploits were added to the attack patterns.
- Added the smtp option to specify a mailserver to use to send the warnings to the ISP.
- Patterns are now stored in pattern.db which makes it easier to add patterns.
- The IIS WebDAV exploit was added to the patterns
<<lessWormwarner has a simple pattern database which makes it easy to add new worm patterns as they appear. Another important feature is the build in rate and mail size control which avoids that wormwarner sends out to much email to an ISP. Wormwarner has also the option to excute external commands, which makes it easy to adapt i.e. firewalls based on the attacks and worms detected by wormwarner.
However there were features requests and the application grown in complexity. The goal of the wormwarner project is to provided users with a powerful and flexible, but benign tool to take action against worms and attacks on their webserver(s).
Enhancements:
- The attack complaint message was changed to a less offensive one.
- "GET /scripts/nsiislog.dll" was added to the attack patterns.
- Various formmail exploits were added to the attack patterns.
- Added the smtp option to specify a mailserver to use to send the warnings to the ISP.
- Patterns are now stored in pattern.db which makes it easier to add patterns.
- The IIS WebDAV exploit was added to the patterns
Download (0.028MB)
Added: 2006-07-13 License: GPL (GNU General Public License) Price:
1201 downloads
Virge 3.04rc3
Virge is mail scanner written in C. more>>
Virge is mail scanner written in C, which replaces/substitutes procmail for a while, checks the incoming mail, and then sends the mail to the procmail. It will check mail for viruses and/or attachment names. Check the FEATURES/README/NEWS files for more details. Virge requires Sendmail and (optionally) AVPDaemon, Sophie or Trophie (to check attachments for viruses).
Virge replaces temporarily procmail. When new mail comes in, Sendmail will pass the contents of the mail to Virge. At that point, Virge performs set of checks:
Checks if the mail has attachments. If it does not, it sends it to procmail for delivery.
If mail has attachments, Virge creates temporary directory, unpacks attachments there, and asks AVP/Sophie/Trophie to scan the temporary directory for viruses. Virge was created with 2 things in mind: performance and security. Because of performance issues, it was not feasible to use any command line scanners like TrendMicro of McAfee ones.
AVP/Sophie/Trophie are instructed to scan attachments for viruses next. If it finds any viruses, mail is immediately isolated in a directory not (hopefully) accessible to anyone except administrators.
If no viruses were found, Virge will then perform attachment check, and see if any of the attachments are not allowed to be sent to the end user. A configuration file is consulted for list of extensions (or full filenames) that should not be allowed in. If any such attachments were found, tricky part comes - Virge will *hopefully* properly "rewrite" the whole email, and strip the attachments that are not allowed. Small notice is attached at the end of the mail, with names of stripped attachments. Mail is also isolated, in case poor overworked sysadmin ever gets some free time to take a closer look.
IMPORTANT: Please, keep in mind that Virge will *NOT* rewrite & send mails when virus has been found. I will *NOT* implement any such features, since it doesnt make any sense (I havent seen a mail with virus that actually had some valuable content in it for many months - maybe even years).
If AVP/Sophie/Trophie are not available (daemon is down), Virge will still deliver mails and annoy admins through syslog messages. Attachment check is still performed.
Users for which no checks should be performed can also be configured. Location of the file can be specified in the configuration file.
Virge is definitelly trying to not let any lame script kiddies abuse it in any way. It is trying to resist to race conditions, buffer overflows, and similar neat tricks. No guarantees, of course, that there are no security problems in Virge.
Virge tries to be as fast as possible, and not waste CPU time or any other resources. It is still possible to make it perform even better, although I presume it would be in 1-5% range. Will take some more time later, and try to fix all the small performance problems.
And yes - Virge *is* fast. I have made a complete Virge V1 in Perl some time ago, but it was absolute failure. Although I tried to use as little modules as possible and make it as fast as possible... it was crap. 2 minutes after I started a script that sends 3-5 mails per second, I started wondering "Why the hell cant I login to the mailserver anymore?". Perl is nice, but its not good for tools like this. Not at all (except if you have low traffic on your mailserver).
And Virge still needs a *lot* of testing. I have tried to test Virge with many different mail (MIME) formats and tried different tricks in order to bypass its decoding techniques (in order to send a virus or .exe to users), but it handles things pretty well. There are cases, though, when it is possible to trick librfc2045 and send attachments that dont get caught, but those attachments are violating RFCs anyway. If your mail client is so stupid to decode invalid/malformed attachments/mails - you deserved it. Dont use stupid mail clients then. Im not going to start adding all those crappy features into Virge that would let someone detect all possible tricks which can be used. Use good mail clients, dont rely on Virge to save you.
Main features:
- Virge can check every incoming mail for attachments, and can remove attachments that are considered dangerous.
- "Dangerous" can be defined:
- email with specific kinds of attachments (e.g., .EXE, .COM, etc.)
- email that contains a virus as identified by Sophie ( http://www.vanja.com )
- email that contains a virus as identified by trophie ( http://www.vanja.com )
- email that contains a virus as identified by AVPDaemon (http://www.avp.ch)
- Any combination of the above.
- Dangerous email can trigger:
- rewriting that removes virus.
- alert back to sender.
- alert to recepient.
- alert to system manager.
- rewrite to remove virus.
- All offending mail messages can be isolated for later reviewing.
- Written in C, so it is very fast, doesnt waste resources, and doesnt depend on a complicated perl installation (which is subject to breaking).
- Notification can be sent (configurable) to sender/recipient of suspicious/infected mail. Templates can be used to define the layout of the mail.
- Regular expressions can be used for filename matching
- Virge was made with security in mind, and should be hard to abuse
- Can be configured to fail open or fail closed if load on the machine goes too high.
- Virge 3.0 designed for easy integration with Postfix
<<lessVirge replaces temporarily procmail. When new mail comes in, Sendmail will pass the contents of the mail to Virge. At that point, Virge performs set of checks:
Checks if the mail has attachments. If it does not, it sends it to procmail for delivery.
If mail has attachments, Virge creates temporary directory, unpacks attachments there, and asks AVP/Sophie/Trophie to scan the temporary directory for viruses. Virge was created with 2 things in mind: performance and security. Because of performance issues, it was not feasible to use any command line scanners like TrendMicro of McAfee ones.
AVP/Sophie/Trophie are instructed to scan attachments for viruses next. If it finds any viruses, mail is immediately isolated in a directory not (hopefully) accessible to anyone except administrators.
If no viruses were found, Virge will then perform attachment check, and see if any of the attachments are not allowed to be sent to the end user. A configuration file is consulted for list of extensions (or full filenames) that should not be allowed in. If any such attachments were found, tricky part comes - Virge will *hopefully* properly "rewrite" the whole email, and strip the attachments that are not allowed. Small notice is attached at the end of the mail, with names of stripped attachments. Mail is also isolated, in case poor overworked sysadmin ever gets some free time to take a closer look.
IMPORTANT: Please, keep in mind that Virge will *NOT* rewrite & send mails when virus has been found. I will *NOT* implement any such features, since it doesnt make any sense (I havent seen a mail with virus that actually had some valuable content in it for many months - maybe even years).
If AVP/Sophie/Trophie are not available (daemon is down), Virge will still deliver mails and annoy admins through syslog messages. Attachment check is still performed.
Users for which no checks should be performed can also be configured. Location of the file can be specified in the configuration file.
Virge is definitelly trying to not let any lame script kiddies abuse it in any way. It is trying to resist to race conditions, buffer overflows, and similar neat tricks. No guarantees, of course, that there are no security problems in Virge.
Virge tries to be as fast as possible, and not waste CPU time or any other resources. It is still possible to make it perform even better, although I presume it would be in 1-5% range. Will take some more time later, and try to fix all the small performance problems.
And yes - Virge *is* fast. I have made a complete Virge V1 in Perl some time ago, but it was absolute failure. Although I tried to use as little modules as possible and make it as fast as possible... it was crap. 2 minutes after I started a script that sends 3-5 mails per second, I started wondering "Why the hell cant I login to the mailserver anymore?". Perl is nice, but its not good for tools like this. Not at all (except if you have low traffic on your mailserver).
And Virge still needs a *lot* of testing. I have tried to test Virge with many different mail (MIME) formats and tried different tricks in order to bypass its decoding techniques (in order to send a virus or .exe to users), but it handles things pretty well. There are cases, though, when it is possible to trick librfc2045 and send attachments that dont get caught, but those attachments are violating RFCs anyway. If your mail client is so stupid to decode invalid/malformed attachments/mails - you deserved it. Dont use stupid mail clients then. Im not going to start adding all those crappy features into Virge that would let someone detect all possible tricks which can be used. Use good mail clients, dont rely on Virge to save you.
Main features:
- Virge can check every incoming mail for attachments, and can remove attachments that are considered dangerous.
- "Dangerous" can be defined:
- email with specific kinds of attachments (e.g., .EXE, .COM, etc.)
- email that contains a virus as identified by Sophie ( http://www.vanja.com )
- email that contains a virus as identified by trophie ( http://www.vanja.com )
- email that contains a virus as identified by AVPDaemon (http://www.avp.ch)
- Any combination of the above.
- Dangerous email can trigger:
- rewriting that removes virus.
- alert back to sender.
- alert to recepient.
- alert to system manager.
- rewrite to remove virus.
- All offending mail messages can be isolated for later reviewing.
- Written in C, so it is very fast, doesnt waste resources, and doesnt depend on a complicated perl installation (which is subject to breaking).
- Notification can be sent (configurable) to sender/recipient of suspicious/infected mail. Templates can be used to define the layout of the mail.
- Regular expressions can be used for filename matching
- Virge was made with security in mind, and should be hard to abuse
- Can be configured to fail open or fail closed if load on the machine goes too high.
- Virge 3.0 designed for easy integration with Postfix
Download (0.17MB)
Added: 2006-07-10 License: BSD License Price:
1201 downloads
lfwmail 2.4
lfwmail is a light weight web mail program written in perl. more>>
lfwmail is a light weight web mail program written in perl.
It will run with acceptable speed even on a Pentium 100Mhz Linux mailserver.
It has just basic features and no calendar or folders but it is fully
mime compatible and can handle attachments.
If you dont like browser cookies, this program is very suitable for you, because you dont have to enable cookies.
It is also very secure when you use https (encryption). HTML
mails are converted to ASCII text for security reasons but
you can still see the HTML mail if you want.
The code is clean and structured. Installation is straight forward
and you dont need a lot of non standard modules.
You can run it in mod_perl if you want. Remember to restart the
server when you do changes in the lfwmC.pm or any other file.
Response time will be very fast with mod_perl however for most people
normal cgi-bin will be good enough. lfwmail is already quite fast.
lfwmail is a light weight mail program. It does not keep track on what
you have read and what is new. You have to remember the dates of the
mails. There is however a small help to keep track on what you have seen
and what is new. It works for Mozilla (not netscape 4), Opera and MS IE
only as it depends on javascript style objects: the background color of e-mails
you have clicked on is changed. This is to keep track on what you have
read and what is new. This information does also survive between sessions since
version 1.5.
Enhancements:
- make it possible to call lfwmail with uid=xxx in the url. e.g https://my.host/cgi-perl/lfwmail?uid=joe_wm
<<lessIt will run with acceptable speed even on a Pentium 100Mhz Linux mailserver.
It has just basic features and no calendar or folders but it is fully
mime compatible and can handle attachments.
If you dont like browser cookies, this program is very suitable for you, because you dont have to enable cookies.
It is also very secure when you use https (encryption). HTML
mails are converted to ASCII text for security reasons but
you can still see the HTML mail if you want.
The code is clean and structured. Installation is straight forward
and you dont need a lot of non standard modules.
You can run it in mod_perl if you want. Remember to restart the
server when you do changes in the lfwmC.pm or any other file.
Response time will be very fast with mod_perl however for most people
normal cgi-bin will be good enough. lfwmail is already quite fast.
lfwmail is a light weight mail program. It does not keep track on what
you have read and what is new. You have to remember the dates of the
mails. There is however a small help to keep track on what you have seen
and what is new. It works for Mozilla (not netscape 4), Opera and MS IE
only as it depends on javascript style objects: the background color of e-mails
you have clicked on is changed. This is to keep track on what you have
read and what is new. This information does also survive between sessions since
version 1.5.
Enhancements:
- make it possible to call lfwmail with uid=xxx in the url. e.g https://my.host/cgi-perl/lfwmail?uid=joe_wm
Download (0.019MB)
Added: 2006-06-10 License: GPL (GNU General Public License) Price:
1231 downloads
mod_tee
mod_tee serves to clone an document as it is served. more>>
mod_tee serves to "clone" an document as it is served. mod_tee was hacked up as a quick-and-dirty fix when a Site Valet user complained of problems saving a Valet report: mod_tee now serves to enable registered users to request email copies of any report generated.
The current status is "works for us", but it is not of release quality. It is less-than-complete in several respects. Its probably not a good idea to use it operationally unless youre prepared to get your hands dirty fixing any problems, or pay for support.
Configuration
TeeType FILE|PIPE|SMTP [Destination]
Where to send the cloned output:
FILE - save to a destination file. For testing only!
PIPE - pipes output to a destination program with popen.
SMTP - sends cloned output directly to email at a destination mailserver. Implements SMTP handshake with no error checking - so its a dangerous option!
TeeCondition query|cookie|path|header|env|true|false [key] [val]
Defines a condition for mod_tee to be activated for a request. Values true and false are unconditional, while the others define a QUERY_STRING key, a Cookie, a PATH_INFO component, a request header or an environment variable to trigger the tee. Conditional values require a key. If val is defined then key must match it; otherwise any value of key will activate the tee.
TeeHeader key value
Defines an RFC822-style header to be inserted in front of the body of the page.
<<lessThe current status is "works for us", but it is not of release quality. It is less-than-complete in several respects. Its probably not a good idea to use it operationally unless youre prepared to get your hands dirty fixing any problems, or pay for support.
Configuration
TeeType FILE|PIPE|SMTP [Destination]
Where to send the cloned output:
FILE - save to a destination file. For testing only!
PIPE - pipes output to a destination program with popen.
SMTP - sends cloned output directly to email at a destination mailserver. Implements SMTP handshake with no error checking - so its a dangerous option!
TeeCondition query|cookie|path|header|env|true|false [key] [val]
Defines a condition for mod_tee to be activated for a request. Values true and false are unconditional, while the others define a QUERY_STRING key, a Cookie, a PATH_INFO component, a request header or an environment variable to trigger the tee. Conditional values require a key. If val is defined then key must match it; otherwise any value of key will activate the tee.
TeeHeader key value
Defines an RFC822-style header to be inserted in front of the body of the page.
Download (0.012MB)
Added: 2006-04-20 License: GPL (GNU General Public License) Price:
1285 downloads
SMTP Relay Checker 2.0.3
SMTP Relay Checker is a fully configurable, multithreaded open mail relay scanner. more>>
SMTP Relay Checker is a fully configurable, multithreaded open mail relay scanner. It supports scanning of IP blocks, and can print the results to a Web page.
SMTP Relay Checker is intended for Systems Administrators to check IP blocks under their control.
Compilation / Installation
To build SmtpRC please run "make" in the package directory. This will build the package and create the binary "smtprc". To install the package, please run "make install".
By Default, the binary will be installed into /usr/local/bin/, configuration files will be installed under /usr/local/etc/smtprc/ and all documentation files will be installed under /usr/local/share/doc/smtprc/. Please see below for a full list of installed files.
/usr/local/bin/smtprc
/usr/local/bin/gsmtprc
/usr/local/etc/smtprc/auto.conf
/usr/local/etc/smtprc/email.tmpl
/usr/local/etc/smtprc/rcheck.conf
/usr/local/share/doc/smtprc/README
/usr/local/share/doc/smtprc/FAQ
/usr/local/man/man1/smtprc.1
/usr/local/man/man1/gsmtprc.1
Using Smtprc
SmtpRC can be run by specifying options on the command line, or by configuring an "auto configuration" file and letting SmtpRC parse the options from there. The latter is recommended.
When SmtpRC is installed, a example "auto configuration" file is installed in "/usr/local/etc/smtprc/auto.conf". Edit this file, changing the values to suit your specific network requirements and run smtprc with the following option (a full list of options
is detailed below):
"/usr/local/bin/smtprc -j /usr/local/etc/smtprc/auto.conf"
To be sure that a mailserver relays third-party email, SmtpRC will attempt to relay mail to an address specified. It is recommended that this address is a mailbox on the local machine that is being used to run SmtpRC - pop support is a planned feature, but for now, SmtpRC only supports checking local mailboxes (mbox and Maildir). Create a new user account (smtprc), specify the email address for this account, and the local mailbox (on the command line or in the "auto configuration" file), and SmtpRC will attempt to relay emails to this address and check for recieved emails after scanning.
There is also a GUI interface to smtprc (gsmtprc) that is installed in /usr/local/bin. This requires Perl Tk to run.
Enhancements:
- Fixes a race condition between the master and reaper threads.
<<lessSMTP Relay Checker is intended for Systems Administrators to check IP blocks under their control.
Compilation / Installation
To build SmtpRC please run "make" in the package directory. This will build the package and create the binary "smtprc". To install the package, please run "make install".
By Default, the binary will be installed into /usr/local/bin/, configuration files will be installed under /usr/local/etc/smtprc/ and all documentation files will be installed under /usr/local/share/doc/smtprc/. Please see below for a full list of installed files.
/usr/local/bin/smtprc
/usr/local/bin/gsmtprc
/usr/local/etc/smtprc/auto.conf
/usr/local/etc/smtprc/email.tmpl
/usr/local/etc/smtprc/rcheck.conf
/usr/local/share/doc/smtprc/README
/usr/local/share/doc/smtprc/FAQ
/usr/local/man/man1/smtprc.1
/usr/local/man/man1/gsmtprc.1
Using Smtprc
SmtpRC can be run by specifying options on the command line, or by configuring an "auto configuration" file and letting SmtpRC parse the options from there. The latter is recommended.
When SmtpRC is installed, a example "auto configuration" file is installed in "/usr/local/etc/smtprc/auto.conf". Edit this file, changing the values to suit your specific network requirements and run smtprc with the following option (a full list of options
is detailed below):
"/usr/local/bin/smtprc -j /usr/local/etc/smtprc/auto.conf"
To be sure that a mailserver relays third-party email, SmtpRC will attempt to relay mail to an address specified. It is recommended that this address is a mailbox on the local machine that is being used to run SmtpRC - pop support is a planned feature, but for now, SmtpRC only supports checking local mailboxes (mbox and Maildir). Create a new user account (smtprc), specify the email address for this account, and the local mailbox (on the command line or in the "auto configuration" file), and SmtpRC will attempt to relay emails to this address and check for recieved emails after scanning.
There is also a GUI interface to smtprc (gsmtprc) that is installed in /usr/local/bin. This requires Perl Tk to run.
Enhancements:
- Fixes a race condition between the master and reaper threads.
Download (0.053MB)
Added: 2006-04-13 License: GPL (GNU General Public License) Price:
1313 downloads
AeroMail 2.52
AeroMail 2 is the next generation of Mark Cushmans AeroMail. more>>
AeroMail 2 is the next generation of Mark Cushmans AeroMail.
AeroMail is a web-based e-mail client written in PHP. AeroMail uses an IMAP server to read and store messages in one or more user-defined folders. Features include HTTP authentication for login (no cookies) and folder manipulation.
AeroMail 2 adds something to the original. You can now embed AeroMail in a webpage of your own design, and customize its appearance more easily.
Furthermore, displaying of messages was improved to include foreign languages like Russian and Chinese, and to display HTML messages including pictures. Last but not least, spam flagging using DNS blacklists is now possible.
Who can use Aeromail?
Are you an ISP who want a webmail service that is easily configurable? AeroMail allows you full control over operation and appearance.
Are you a webhosting company who need webmail for their clients? AeroMail comes with genericstable support, spam marking and many configurable options.
Are you a mail user who is sick of spam? You can use AeroMail to mark and delete your spam without downloading it to your own computer first.
Do you just want a fast and easy way to check mail when youre on the move? AeroMail is small, easy to set up and does not depend on MySQL, LDAP or other things you do not have: you only need an Apache webserver, PHP and an IMAP mailserver.
Why use AeroMail?
AeroMail is small, fast and simple to use. It is known for its clear and elegant interface.
AeroMail has support for other characters sets. It displays e-mail in Russian, Chinese, Japanese and many other languages.
AeroMail is available in many languages: currently you can choose from Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Italian, Japanese, Latvian, Lithuanian, Norse, Polish, Portuguese (Brasil), Portuguese (Portugal), Romanian, Russian, Serbian (Roman or Cyrillic), Slovenian, Spanish, Swedish, Turkish, Thai and Ukranian.
Optionally you can use AeroMail to flag spam, so you can easily delete it before downloading it to your own computer.
AeroMail is very easy to set up: just copy the files, answer some questions and youre ready to go!
Where use AeroMail?
AeroMail can be used on many types of IMAP servers: Cyrus, UWash and Courier IMAP servers are supported.
You dont need an LDAP server or a MySQL server to use AeroMail. It will work on any Apache server with PHP 4 installed.
You can use AeroMail from virtually any browser: No JavaScript required, simple HTML that will also work on mobile devices.
You can use AeroMail from any computer you want. It uses basic authentication (no cookies) or use cookies (session variables) for login, and can run on an SSL IMAP server.
Main features:
Basic features:
- Aeromail is a webmail client that lets you read e-mail from an IMAP server
- Each mail folder can be sorted in many ways
- View HTML messages and rich-text messages
- Clickable links and e-mail addresses in plain-text messages
- View inline images and text attachments
- Recieve attachments
- Optionally reply to and forward e-mail, write new messages and delete messages
- Use Cc and Bcc
- Send attachments yourself
- Optionally create and delete folders, and move messages between folders
Advanced features:
- Optional multi-message view lets you view selected messages in one window (nice for catching up or when on a slow link)
- Optional spam blacklisting using reverse DNS lookup (e.g. SpamCop)
- Optionally move junk mail automatically to another folder
- Show full e-mail addresses, or just the name (Outlook style)
- Show full address lists in mail overview, or just the first few
- Automatically wrap wide message, or leave them unchanged
- Optional colorization of messages (quoted text and signatures)
Languages and character sets:
- AeroMail comes in 29 languages
- Full support for foreign character sets (using UTF-8)
Configuration features:
- AeroMail is easily embedded in a web page of your own design
- AeroMail comes with many color schemes or themes
- The HTML code is separated from the program, so it can be changed more easily
- Folder use and management can be switched on or off
- Sent mail folder and Trash folder can be switched on or off
- Writing of messages can be switched on or off
- Deleting of messages can be switched on or off
Technical features:
- Use UWash, Cyrus and Courier type IMAP servers
- Either use Basic Authentication for login (no cookies), or cookies (session variables)
- Support for sendmails genericstable
- Alternatively force the senders from-address
- Support for SSL IMAP servers
- No SQL server or LDAP server required
- No JavaScript browser required
<<lessAeroMail is a web-based e-mail client written in PHP. AeroMail uses an IMAP server to read and store messages in one or more user-defined folders. Features include HTTP authentication for login (no cookies) and folder manipulation.
AeroMail 2 adds something to the original. You can now embed AeroMail in a webpage of your own design, and customize its appearance more easily.
Furthermore, displaying of messages was improved to include foreign languages like Russian and Chinese, and to display HTML messages including pictures. Last but not least, spam flagging using DNS blacklists is now possible.
Who can use Aeromail?
Are you an ISP who want a webmail service that is easily configurable? AeroMail allows you full control over operation and appearance.
Are you a webhosting company who need webmail for their clients? AeroMail comes with genericstable support, spam marking and many configurable options.
Are you a mail user who is sick of spam? You can use AeroMail to mark and delete your spam without downloading it to your own computer first.
Do you just want a fast and easy way to check mail when youre on the move? AeroMail is small, easy to set up and does not depend on MySQL, LDAP or other things you do not have: you only need an Apache webserver, PHP and an IMAP mailserver.
Why use AeroMail?
AeroMail is small, fast and simple to use. It is known for its clear and elegant interface.
AeroMail has support for other characters sets. It displays e-mail in Russian, Chinese, Japanese and many other languages.
AeroMail is available in many languages: currently you can choose from Bulgarian, Catalan, Chinese, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Italian, Japanese, Latvian, Lithuanian, Norse, Polish, Portuguese (Brasil), Portuguese (Portugal), Romanian, Russian, Serbian (Roman or Cyrillic), Slovenian, Spanish, Swedish, Turkish, Thai and Ukranian.
Optionally you can use AeroMail to flag spam, so you can easily delete it before downloading it to your own computer.
AeroMail is very easy to set up: just copy the files, answer some questions and youre ready to go!
Where use AeroMail?
AeroMail can be used on many types of IMAP servers: Cyrus, UWash and Courier IMAP servers are supported.
You dont need an LDAP server or a MySQL server to use AeroMail. It will work on any Apache server with PHP 4 installed.
You can use AeroMail from virtually any browser: No JavaScript required, simple HTML that will also work on mobile devices.
You can use AeroMail from any computer you want. It uses basic authentication (no cookies) or use cookies (session variables) for login, and can run on an SSL IMAP server.
Main features:
Basic features:
- Aeromail is a webmail client that lets you read e-mail from an IMAP server
- Each mail folder can be sorted in many ways
- View HTML messages and rich-text messages
- Clickable links and e-mail addresses in plain-text messages
- View inline images and text attachments
- Recieve attachments
- Optionally reply to and forward e-mail, write new messages and delete messages
- Use Cc and Bcc
- Send attachments yourself
- Optionally create and delete folders, and move messages between folders
Advanced features:
- Optional multi-message view lets you view selected messages in one window (nice for catching up or when on a slow link)
- Optional spam blacklisting using reverse DNS lookup (e.g. SpamCop)
- Optionally move junk mail automatically to another folder
- Show full e-mail addresses, or just the name (Outlook style)
- Show full address lists in mail overview, or just the first few
- Automatically wrap wide message, or leave them unchanged
- Optional colorization of messages (quoted text and signatures)
Languages and character sets:
- AeroMail comes in 29 languages
- Full support for foreign character sets (using UTF-8)
Configuration features:
- AeroMail is easily embedded in a web page of your own design
- AeroMail comes with many color schemes or themes
- The HTML code is separated from the program, so it can be changed more easily
- Folder use and management can be switched on or off
- Sent mail folder and Trash folder can be switched on or off
- Writing of messages can be switched on or off
- Deleting of messages can be switched on or off
Technical features:
- Use UWash, Cyrus and Courier type IMAP servers
- Either use Basic Authentication for login (no cookies), or cookies (session variables)
- Support for sendmails genericstable
- Alternatively force the senders from-address
- Support for SSL IMAP servers
- No SQL server or LDAP server required
- No JavaScript browser required
Download (0.052MB)
Added: 2006-01-23 License: GPL (GNU General Public License) Price:
1369 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above mailserver search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed