Free axigen mail server office discount software for linux

pop3spam is a POP3 client which connects to a POP3 server and deletes unsolicited mail. If a message has been identified as unsolicited, it can be deleted directly from the POP3 server without the need to download it first.

Eventually your normal mail-retrieval utility (e.g. fetchmail) can gather all (cleaned) mail as usual. The program is intended for people with low bandwidth. Its very annoying if you first have to download lots of large messages just for the sole purpose of deleting them afterwards because your local spam filter debunked them as spam. Its also annoying to download very large messages (attachments) at all.

pop3spam doesnt use any hard wired regular expressions so it should basically work with any recent version. For information about the configuration and use of pop3spam, take a look at the man pages pop3spam(1) and pop3spamrc(5). A sample configuration file exists in the directory doc/ in the source tree.

getmail is a mail retriever designed to allow you to get your mail from one or more mail accounts on various mail servers to your local machine for reading with a minimum of fuss.
getmail it is secure, flexible, reliable, and easy-to-use. getmail is designed to replace other mail retrievers such as fetchmail.
Main features:
- simple to install, configure, and use
- retrieve virtually any mail
- support for accessing mailboxes with the following protocols:
- POP3
- POP3-over-SSL
- IMAP4
- IMAP4-over-SSL
- SDPS (Demon UKs extensions to POP3)
- support for single-user and domain mailboxes
- retrieve mail from an unlimited number of mailboxes and servers
- can remember which mail it has already retrieved, and can be set to only download new messages
- support for message filtering, classification, and annotation by external programs like spam filters and anti-virus programs
- support for delivering messages to different destinations based on the message recipient
- reliability
- native safe and reliable delivery support for maildirs and mboxrd files, in addition to delivery through arbitrary external message delivery agents (MDAs)
- does not destroy information by rewriting mail headers
- does not cause mail loops by doing SMTP injection, and therefore does not require that you run an MTA (like qmail or sendmail) on your host
- written in Python, and therefore easy to extend or customize
- a flexible, extensible architecture so that support for new mail access protocols, message filtering operations, or destination types can be easily added
- cross-platform operation; getmail 4 should work on Unix/Linux, Macintosh, and other platforms. Windows support available under the free Cygwin package.
- winner of various software awards, including DaveCentrals "Best of Linux.
Enhancements:
- A fix for an exception when getmail is trying to report a POP3 server that completely missed generating a UIDL token for a message. .

Scam-backscatter prevents backscatter (accept and bounce) on mail servers which dont host mailboxes locally. The project validates mailboxes by verifying the recipient addresses hosted on a different mail server.

Backscatter is when a mail server accepts an email with a forged sender address, then generates a bounce (non-delivery receipt) to the sending address. The figure below shows an example where the sender address is forged:

1. An email is sent by smtp.example.com with a forged sender address of user1@example.org to user2@example.net.

2. The email is accepted for delivery by smtp.example.net.

3. The email is then forwarded to mailbox.example.net.

As there is no user2 mailbox on mailbox.example.net, a bounce message (non-delivery receipt) is generated by mailbox.example.net to notify the sender address (user1@example.org) of the delivery failure.

4. The bounce message is sent to the mail server at smtp.example.org.

5. user1@example.org receives the bounce message.

Your mail server can prevent backscatter by validating the recipient email address in step 2.

Kshowmail project is a KDE tool to watch mails on a POP3 server. Headers and complete mails can be viewed without loading them to the local mail client. Unpleasant mail can be deleted from the server.
The list of displayed mails can be refreshed via configurable timers. Filters can be assigned to mark known spam for deletion. Multiple accounts are supported.
A sound can be played if new mail arrives. A command menu allows user configurable commands like fetchmail or sendmail. A special command can be defined to send complain mail against spam.
The modifications I provided are mainly Qt/KDE stuff to generate a nice GUI interface. I am using the great development tool kDevelop V2.1.
Enhancements:
- Fixed bug where if you configure 2 accounts, retrieve mail, and then deactivate one of the accounts, its number of messages still reflects in the tray icon.
- Fixed sort of message number and size columns in message list to be numerical rather than alpha.
- Corrected version displayed in the About dialog.

Mail::Bulkmail is a platform independent mailing list module.

SYNOPSIS

use Mail::Bulkmail /path/to/conf.file

my $bulk = Mail::Bulkmail->new(
"LIST" => "~/my.list.txt",
"From" => "Jim Thomason" ,
"Subject" => "This is a test message",
"Message" => "Here is my test message"
) || die Mail::Bulkmail->error();

$bulk->bulkmail() || die $bulk->error;

Dont forget to set up your conf file!

Mail::Bulkmail gives a fairly complete set of tools for managing mass-mailing lists. I initially wrote it because the tools I was using at the time were just too damn slow for mailing out to thousands of recipients. I keep working on it because its reasonably popular and I enjoy it.

In a nutshell, it allows you to rapidly transmit a message to a mailing list by zipping out the information to them via an SMTP relay (your own, of course). Subclasses provide the ability to use mail merges, dynamic messages, and anything else you can think of.

Mail::Bulkmail 3.00 is a major major major upgrade to the previous version (2.05), which was a major upgrade to the previous version (1.11). My software philosophy is that most code should be scrapped and re-written every 6-8 months or so. 2.05 was released in October of 2000, and Im writing these docs for 3.00 in January of 2003. So Im at least 3 major re-writes behind. (philosophy is referenced in the FAQ, below)

But thats okay, because were getting it done now.

3.00 is about as backwards compatible to 2.00 as 2.00 is to 1.00. That is to say, sorta. Ive tried to make a note of things where they changed, but Im sure I missed things. Some things can no longer be done, lots are done differently, some are the same. You will need to change your code to update from 1.x or 2.x to 3.00, though. Thats a given.

So whats new for 3.00? Lots of stuff.

Immediate changes are:

* code compartmentalization
* multi-server support
* conf file

The immediate change is that the code is now compartmentalized. Mail::Bulkmail now just handles ordinary, non-dynamic mailings. See Mail::Bulkmail::Dynamic for the merging and dynamic text abilities from the prior versions.

Server connections are no longer handled directly in Mail::Bulkmail (Smtp attribute, Port attribute, etc.), there is now a separate Mail::Bulkmail::Server object to handle all of that.

And everything subclasses off of Mail::Bulkmail::Object, where I have my super-methods to define my objects, some helper stuff, and so on.
Its just a lot easier for me to maintain, think about it, etc. if its all separated. Its also easier for you, the user, if you want to make changes to things. Just subclass it, tweak it, and use it. Very straightforward to modify and extend now. 2.x and below *could* do it, but it wasnt really that easy (unless you were making very trivial changes). This should rectify that.

Another major change is the addition of multi-server support. See the docs in Mail::Bulkmail::Server for more information. You can still specify one SMTP relay if thats all youve got, but if you have multiple servers, Mail::Bulkmail can now load balance between them to help take the stress off. No matter what, the biggest bottleneck to all of this is network performance (both to the SMTP relay and then from the relay to the rest of the world), so i wanted to try and help alleviate that by using multiple servers. I know that some people were doing that on there own with small changes, but this allows you to do it all invisibly.
And finally, finally, finally there is a conf file. Documentation on the format is in Mail::Bulkmail::Object. Its pretty easy to use. This is the conf file format that I designed for my own use (along with most of the rest of Mail::Bulkmail::Object). The software also has the ability to read multiple conf files, if so desired. So no more worrying about asking your sysadmin to tweak the values in your module somewhere up in /usr/lib/whatever

Just have him create the conf file you want, or pass in your own as desired.
conf_files are specified and further documented in Mail::Bulkmail::Object, in an internal array called @conf_files, right at the top of the module. To specify a universal conf file, put it in that array (or have your sysadmin do so). Alternatively, you can also add a conf_file via the conf_files accessor.

Mail::Bulkmail->conf_files(/path/to/conf_file, /path/to/other/conf_file); #, etc.

But the recommended way is to specify your conf file upon module import.

use Mail::Bulkmail 3.00 "/path/to/conf/file";

In addition, there is the usual plethora of bug fixes, tweaks, clean-ups, and so on.

And yes, the horrid long-standing bug in the Tz method is fixed! No, honest.
Im also trying a new documentation technique. The pod for a given method is now in the module by that method, as opposed to everything being bunched up at the bottom. Personally, I prefer everything being bunched up there for clarities sake. But from a maintenance point of view, spreading it all out makes my life much easier.

These are the primary mail utilities of the GNU system.

Specifically, this package contains a POP3 server, an IMAP4 server, and a Sieve mail filter. It also provides a POSIX mailx client and a collection of other tools.