Result for 18C8CB60D136D117567169FFD0257C60D575A191

Query result

Key Value
FileName./etc/exim/mk-greylist-db.sql
FileSize193
MD5FBA79D8A8410A24F267EFAF0AFE69104
SHA-118C8CB60D136D117567169FFD0257C60D575A191
SHA-256FE992B118359FA7A23F50FDF903C5152ED46184D4B6D2C958360F266EA0EF5F6
SSDEEP6:eiusrGrsAmMv1GXRJbuMKuO4MOvzNqUmYdIKsAQev:eHs4sKMvrNbv
TLSHT177C0121FD699D62226E34B06AE1C0032C6B99C5744537EC372AE55102D8BB9D15328FD
hashlookup:parent-total114
hashlookup:trust100

Network graph view

Parents (Total: 114)

The searched file hash is included in 114 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
MD5582A883B38CAD9E16E7911AE6523C88B
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
PackageRelease7.fc34
PackageVersion4.94
SHA-10A0557C77DF0ACBF9307D01F49B5B345B59B1249
SHA-256AA39A483427EDA4B5558F99AAF3C8D2E8AF12D75D69E0628780E095301EF98C9
Key Value
MD53800B674C99F8F59CC531E29C13CA3CD
PackageArcharmv7hl
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
PackageRelease7.fc34
PackageVersion4.94
SHA-10A257AD02B991960EF34CF89AFE0D623681D4768
SHA-2565CCC182A1E6491347263E5E801E744730786DA3E5187B68982D27F5CA28F9EC0
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
MD58D46B1EA6771696D1035582A6753CC4A
PackageArchaarch64
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
PackageRelease1.el8
PackageVersion4.94
SHA-10A591445B95A8051EBE1FA3AB3A89391CD42C6E2
SHA-2564C18B6F0489513A0E1AEEA3CFD05280E374A503484965023EA95019305445876
Key Value
MD5B300DB183998DAAC59DF11FB5FBE1BA0
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
PackageRelease3.fc33
PackageVersion4.94
SHA-10BEB7010761322F2436A0422F564AA1EB6A6555E
SHA-256BC1EB6E03ACE148431F0E9B69EF56603532A1B033BD17F31B5F098EA77F72A32
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