Package: greylistd Architecture: all Version: 0.8.3.2+mrtg Priority: optional Section: mail Maintainer: Tor Slettnes Installed-Size: 224 Depends: python (>= 2.3), debconf (>= 0.5) | debconf-2.0, adduser Recommends: exim4 Filename: deb/greylistd_0.8.3.2+mrtg_all.deb Size: 46632 MD5sum: 81d6f0081acf5d780e0ca6d0f193f4f4 SHA1: 49c81a2d601db7d5640dcb10d011951119a71aa2 SHA256: 3dbca7ed0062af357b274951dcc41a8bd9fc120977e2b67d1e944e6e73265b5d SHA512: 498c440e4f46692e8d61c9cd40e41f4d6687ac5f9647b33568f197fdc8948108160dde5a593cc0e041f891553b119220bf57b822d9baf6bc086e0e035fcd5d41 Description: Greylisting daemon for use with Exim 4 This daemon provides a simple greylisting implementation for use with the Exim Mail Transport Agent (MTA), version 4. . Greylisting is a simple but highly effective means to weed out messages that are being delivered via spamware/ratware tools. The idea is to establish whether a prior relationship exists between the sender and the receiver of a message. Most of the time it does, and the delivery proceeds normally. . On the other hand, if no prior relationship exists, the delivery is temporarily rejected. Legitimate MTAs will treat this response accordingly, and retry the delivery in a while. In contrast, ratware will usually fail to retry the delivery in a normal fashion. As a result, greylisting is currently more than 90% effective in blocking incoming junk mail, while nearly all legitimate mail goes through. For more information, see Evan Harris' whitepaper at: http://projects.puremagic.com/greylisting/ . This daemon listens for sender and recipient data on a UNIX domain socket. Your MTA would query the daemon during the incoming SMTP transaction, and accept or defer the incoming message depending on its response. . This package contains a script to configure support for greylisting in Exim 4. It may be possible to use greylistd with other MTAs as well, though some work will probably be involved. Postfix users may want to check out the "postgrey" package instead of this one. Package: greylistd Architecture: all Version: 0.8.3.1+mrtg Priority: optional Section: mail Maintainer: Tor Slettnes Installed-Size: 224 Depends: python (>= 2.3), debconf (>= 0.5) | debconf-2.0, adduser Recommends: exim4 Filename: deb/greylistd_0.8.3.1+mrtg_all.deb Size: 46450 MD5sum: 9221af7c571b6d42ffc60ce799bf36c0 SHA1: 74434d01c2506659926a49e76ac452e8e429b566 SHA256: eee5ce23c2232d47ce71e9ea1f5e964e392c9f8ccb6155716086a484772da88b SHA512: 8254ae45c22b3c12634d662eef313380f073c667ba11a22d6ea42a0b73f28e9ff78da0564ca60ada91f08c10c07ad2abf2e7f8a3701d96a7b608a4e5b1213390 Description: Greylisting daemon for use with Exim 4 This daemon provides a simple greylisting implementation for use with the Exim Mail Transport Agent (MTA), version 4. . Greylisting is a simple but highly effective means to weed out messages that are being delivered via spamware/ratware tools. The idea is to establish whether a prior relationship exists between the sender and the receiver of a message. Most of the time it does, and the delivery proceeds normally. . On the other hand, if no prior relationship exists, the delivery is temporarily rejected. Legitimate MTAs will treat this response accordingly, and retry the delivery in a while. In contrast, ratware will usually fail to retry the delivery in a normal fashion. As a result, greylisting is currently more than 90% effective in blocking incoming junk mail, while nearly all legitimate mail goes through. For more information, see Evan Harris' whitepaper at: http://projects.puremagic.com/greylisting/ . This daemon listens for sender and recipient data on a UNIX domain socket. Your MTA would query the daemon during the incoming SMTP transaction, and accept or defer the incoming message depending on its response. . This package contains a script to configure support for greylisting in Exim 4. It may be possible to use greylistd with other MTAs as well, though some work will probably be involved. Postfix users may want to check out the "postgrey" package instead of this one.