Distributed Checksum Clearinghouse 1.3.101 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Distributed Checksum Clearinghouse 1.3.101 (Default branch)
# 1  
Old 01-11-2009
Distributed Checksum Clearinghouse 1.3.101 (Default branch)

Distributed Checksum Clearinghouse (DCC) is a system of clients and servers that collect and count checksums related to mail messages. The counts can be used by SMTP servers and mail user agents to detect and reject bulk mail. DCC servers can exchange common checksums. The checksums include values that are "fuzzy", or constant across common variations in bulk messages. License: Free for non-commercial use Changes:
Groups of DNS blacklists that can be independently enabled in per-user whiteclnt files are supported. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Dapper Distributed Dataflow Engine 0.91 (Default branch)

Dapper, or "Distributed and Parallel Program Execution Runtime", is a tool for taming the complexities of developing for large-scale cloud and grid computing, enabling the user to create distributed computations from the essentials: the code that will execute, along with a dataflow graph... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
saslfinger(1)						      General Commands Manual						     saslfinger(1)

NAME
saslfinger - A utility to collect SMTP AUTH relevant configuration for Postfix SYNOPSIS
saslfinger [-chs] DESCRIPTION
saslfinger is a utility to collect SMTP AUTH relevant configuration for Postfix. Depending on how you run it, it will search for informa- tion on server-side or client-side SMTP AUTH configuration settings in Postfix and Cyrus SASL. OPTIONS
-c If you run saslfinger with the option -c it will collect data required for client-side SMTP AUTH. Client-side SMTP AUTH is when Postfix smtp daemon uses SMTP AUTH to authenticate itself with a remote mail server that offers SMTP AUTH. saslfinger will try to telnet to all hosts listed in smtp_sasl_password_maps, if it may read smtp_sasl_password_maps The telnet test verifies your host is able to reach the remote servers and shows what AUTH mechanisms they offer - in some cases this is required to debug client-side SMTP AUTH. Important: By default smtp_sasl_password_maps must be read-only to root, since these maps contain the usernames and passwords to authenticate. If you run saslfinger as root access will be no problem, but saslfinger will fail if you lack the permissions to access smtp_sasl_password_maps. If you want to run the telnet test, but don't want to run saslfinger as root change permissions of smtp_sasl_password_maps so that the user running saslfinger may access smtp_sasl_password_maps while you debug. *note: You don't need to worry about saslfinger doing anything with the username or password stored next to the remote hosts in your smtp_sasl_password_maps; saslfinger completely ignores these informations! -h If you run saslfinger with the option -h it will print a little help message that tells you about the options you can use. -s If you run saslfinger with the option -s it will collect data required for server-side SMTP AUTH. Server-side SMTP AUTH is when Postfix smtpd daemon offers SMTP AUTH to mail clients. FILES
saslfinger - the script you need to run. saslfinger.1 - the man page you are currently reading. AUTHOR
Patrick Koetter, <patrick.koetter@state-of-mind.de>, http://www.state-of-mind.de You will find the newest version of saslfinger at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/. BUGS
Please report bugs to <patrick.koetter@state-of-mind.de> Manuals User saslfinger(1)