Free smtp definition software for linux

Speegle Define is a Firefox extension that gives a spoken definition of a word using Speegle Speech Technology. You highlight the word you would like explained with highlight left click on any internet page you are reading.

Right click and choose "Audio Definition" from the pop up menu and its definition will be read back to you in English through your speakers or headphones.

Postfix SMTP Monitoring Solution is a set of three Perl CGI scripts used to monitor the SMTP queue, allowing the deletion of messages that for one reason or another become "stuck" in the queue.

I needed a web-based solution to monitor my Postfix SMTP relay, which enabled me to remove messages that become "stuck" in the queue. I wrote three simple Perl scripts, and used Sudo to give me the desired functionality.

I am uploading these scripts in case they are useful to others. Assuming you have Apache configured correctly on your Postfix server, it should be as easy as placing the three .cgi files into your webservers cgi-bin directory, and making the appropriate modifications to your /etc/sudoers file (see the README contained in the tarball).

No-relay SMTP daemon is a lightweight mail server whose sole purpose is to receive incoming messages and deliver them to local users. Its main "feature" (or non-feature, really) is to be completely unable to relay messages to adjacent servers: if an incoming message is not addressed to a local mailbox, smtpd will reject it.

Another convenient feature is its automatic grey-listing of clients that allows you to efficiently reject spammers based on their behaviour. No-relay SMTP daemon can handle incoming email traffic for an unlimited number of domains (i.e. act as a MX for these domains) without the need for any configuration (other than creation of users mailboxes).

smtp-vilter is a high-performance content filter for sendmail, which detects email viruses and spam.

smtp-vilter can pass, discard, or simply mark an email based on the results of a content scan. It relies on third-party products for the actual content scan. It uses the milter API to communicate with sendmail, and backends to communicate with the actual scanning engines.

The backends can be chained to perform a series of checks on each message in one run.

Curses::Application provides the Curses Application Framework.

Curses::Application attempts to relieve the programmer of having to deal directly with Curses at all. Based upon Curses::Widgets and Curses::Forms, all one should have to do is define the application forms and contents in the DATA block of a script. Curses::Application will take care of the rest.

This module follows many of the conventions established by the Curses::Widgets and Curses::Forms modules, being built upon that framework. One area of special note, however, is the declaration of forms used within the application.

Curses::Application differentiates between forms and form definitions. A form is an instance of any particular form definition. Keeping that line of separation simplifies the development of MDI (Multiple Document Interface) applications.
Form definitions can be provided in two ways: as a list of definitions in the main::DATA block, or individually by using the addFormDef method. The former would normally be the simplest way to do so.

At the end of your script, declare a DATA block using Perls __DATA__ token. In that DATA block place a hash declaration (%forms) which contains a key/value pair for each form definition. The key being the name of the definition, and the value being a hash reference to the form declarations (see the Curses::Forms pod for directives available to that module). The only extra key that should be in each forms hash reference should be a TYPE directive, which would point to a module name relative to the base Curses::Forms class. If you omit this key, then it will be assumed that the form is a Curses::Forms object, or some custom derivative as specified in ALTPATH.

DGS SMTP is a PHP class which acts as an email client, able to send an email without using PHPs built in mail() function.

This is most often useful for sites that are unable to get PHPs build in mail() function to work. (Usually because they dont have access to sites php.ini file).

SMTPHandler is a handler for the java.util.logging library. SMTPHandler sends LogRecords via email using the Simple Mail Transfer Protocol.
The SMTPHandler code is derived from log4js SMTPAppender.
After downloading the SMTPHandler software, you will need to download two additional JAR files:
1) Sun JavaMail
http://java.sun.com/products/javamail
2) Sun JavaBeans Activiation Framework
http://java.sun.com/products/javabeans/glasgow/jaf.html
Enhancements:
- This release adds SMTP server authentication.
- You can specify an SMTP username and SMTP password.

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.