Result for 9D86EEEE4CE710AACE5E2C81CA30EBD6C66566B6

Query result

Key Value
FileName./etc/cron.daily/greylist-tidy.sh
FileSize192
MD5688D777972A8F5C7F22711A711CD4EB3
SHA-19D86EEEE4CE710AACE5E2C81CA30EBD6C66566B6
SHA-256D1DC3DC115085F7DB587935FF2113E9A51E797B0572A83F649BADC9E97C81B62
SSDEEP3:TKH/OsIafBxqUABWXJrAD8FKhBxqUABWXgYnvQs/V5HgFeY3WIEg6mgZ+4evrDu:exfBxq3mJrADUKhBxq3mgYvQs/V5AFeX
TLSHT19CC01256A1DF6D182CFD53173531E0B60564A01A7EEB07A460047AC4180DBE79110781
hashlookup:parent-total90
hashlookup:trust100

Network graph view

Parents (Total: 90)

The searched file hash is included in 90 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD5114080CFFFB8AB53EB881B90E12B479D
PackageArchppc64
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease1.el6
PackageVersion4.91
SHA-1037F351F8EB5A2E72A1C1D12BB7CCB3DFC11C6AA
SHA-256AF4CF371BB6B7BD550BA8EB8311C69933429C16B6908272DA95473F44E4075DE
Key Value
MD5DFCF7001182FBB60CE8670262D4E4E46
PackageArcharmv7hl
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease2.fc15
PackageVersion4.73
SHA-1041738ADE276AC0381C45902069FCE4BB45BE1F3
SHA-2567F78D1481B759631BE82EA33ABE2E03588B63CBDA4EE30309B33146D1ADA60E7
Key Value
MD5DC9CE4E3C532ED52A7DB533590218607
PackageArchsparcv9
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease17.fc12
PackageVersion4.69
SHA-104BA790EA7F91CFF997233E4D4DEBDF6C66B41AC
SHA-25655BEB4A9C064D187CDA2B3BFB4E454CA746ED9C0C99C3AE97839E03C8124684A
Key Value
MD5A49CB33C97EC033B05AF2991C24674C1
PackageArchs390
PackageDescriptionExim is a message transfer agent (MTA) developed at the University of Cambridge for use on Unix systems connected to the Internet. It is freely available under the terms of the GNU General Public Licence. In style it is similar to Smail 3, but its facilities are more general. There is a great deal of flexibility in the way mail can be routed, and there are extensive facilities for checking incoming mail. Exim can be installed in place of sendmail, although the configuration of exim is quite different to that of sendmail.
PackageMaintainerFedora Project
PackageNameexim
PackageRelease3.fc15
PackageVersion4.73
SHA-10A29761E5F7C0287A72E7073F87D07F959EE6697
SHA-2568073EB4517AF3751BEAB38CB33F27FFE48FFAC11962CC8B64A6664911F0DC1E1
Key Value
MD50D407FE6C56177287DDEFBF22963D5A4
PackageArchs390
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease4.fc16
PackageVersion4.76
SHA-10F6133D02D00C637B0C3BCC395E2D41E72921F3A
SHA-2561192153DB63EB158F090C02CB9833FFCD459F5D14AE6D178A5D62D298E002315
Key Value
MD5CDF4DF619E8F15C390FA66B2DA5C140C
PackageArchx86_64
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease2.el6
PackageVersion4.92.3
SHA-11975139AB5AF2D33727B541E02C2554203BC6621
SHA-25661DB895A602BBF0C730516E5E5CFF308B77D7857F1F7F7F92A5C97E38A8ADECE
Key Value
MD553968792F34B04291BC709BDC5505433
PackageArchs390x
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease3.fc19
PackageVersion4.80.1
SHA-11DA39A78AF00B7D42617DDC30FBDCA43AA3BC3F1
SHA-256C31C5F3034554CB3AC672CF95F56C41D1FFFE000FB80F5FEE1410DD835D2DF55
Key Value
MD5AF6FE48C4EC01FBF31F88B4600FC7BDC
PackageArchaarch64
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease4.fc21
PackageVersion4.84
SHA-11E4D518E253CAE717E4E0352B01E4A99F1E7B69E
SHA-2567CDD063BD409CD920A6483373FC3DD2901854FFB6C8EA7F07948283037F38F55
Key Value
MD5E4A9933A4DD10A927A5E1998A6E0C154
PackageArchsparcv9
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease4.fc16
PackageVersion4.76
SHA-11F119648309D09392BD731A9257441A55E721FAB
SHA-25643C219B0F3E01AF18A3879B0963D6ED0546022A61E3662D2DDC00ED490C1FA87
Key Value
MD5D9BC0C9EDDEE5C88C717BE6940A8213F
PackageArchx86_64
PackageDescriptionThis package contains a simple example of how to do greylisting in Exim's ACL configuration. It contains a cron job to remove old entries from the greylisting database, and an ACL subroutine which needs to be included from the main exim.conf file. To enable greylisting, install this package and then uncomment the lines in Exim's configuration /etc/exim.conf which enable it. You need to uncomment at least two lines -- the '.include' directive which includes the new ACL subroutine, and the line which invokes the new subroutine. By default, this implementation only greylists mails which appears 'suspicious' in some way. During normal processing of the ACLs we collect a list of 'offended' which it's committed, which may include having SpamAssassin points, lacking a Message-ID: header, coming from a blacklisted host, etc. There are examples of these in the default configuration file, mostly commented out. These should be sufficient for you to you trigger greylisting for whatever 'offences' you can dream of, or even to make greylisting unconditional.
PackageMaintainerFedora Project
PackageNameexim-greylist
PackageRelease1.el7
PackageVersion4.92.3
SHA-124068C14AB120D6CA2F1B58B1568AAFBBAFD5CFA
SHA-256F31B41F84F3466A2A389ED02518414B3B5B55703CB368E43A5274341FE0FBBD9