Result for 05279B188911954B552A7157DC7DC8862D8D69AA

Query result

Key Value
FileName./etc/cron.daily/greylist-tidy.sh
FileSize196
MD5228675244BF9FB5F906268A557C93F02
SHA-105279B188911954B552A7157DC7DC8862D8D69AA
SHA-256623041E927FDE2DF57D1DB8D1C7B1BAFF36E563BB6A18099E541142403C23D53
SSDEEP6:HWaHFJyBxq3mJrADUKhBxq3mgYvQs/V5AFeY3P6mD7u:HNJym3mJrem3mjx/VmFe5mnu
TLSHT1B8D02266F0DF6D282CFE43133530E0B604A4A01A2EEB1B9020007AC0180DBE39210280
hashlookup:parent-total9
hashlookup:trust95

Network graph view

Parents (Total: 9)

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

Key Value
MD5818A0CC96938911BB9BD03136E72752C
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
PackageRelease4.fc32
PackageVersion4.93
SHA-145C58FB15FA9DD1BF47A88042396C66EA06A2BC8
SHA-256BBAAE35CDB98F43516F60792F8784608554454123A3D1D5F48C7E4AA9B7B4795
Key Value
MD59C670F8195B852DA05A309928C340CCE
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
PackageRelease4.fc32
PackageVersion4.93
SHA-1A433D7E2EB09B17DC361C3F98726FE6ABD0CD6A8
SHA-256866864455FBA18E0B6A23A62AF65A23DAAFC5744067E53FC1617BD7EE46E20C8
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
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
MD5FE23A1C5F558475785396B6FD8311794
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
PackageRelease3.fc33
PackageVersion4.94
SHA-14E73121C4D4A1C8FAC650B93DF496B2A7E6DB784
SHA-256803F380C8CC8B421CDA942C20FFCECCDE8B53FF93D516A526DBCE114716BD4B3
Key Value
MD5301C96A232DCF06086D0B1CC80484D30
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
PackageRelease3.fc33
PackageVersion4.94
SHA-1EFC4EB86939558A9682C5AB25AB6D0146D87EF39
SHA-2562D5ABBD78131CF095548607122391DB3F8B22EC225BC36DE40F08161D387CBB6
Key Value
MD50C2B79C353122364A049DB999BB16C61
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
PackageRelease7.fc34
PackageVersion4.94
SHA-142C3D594E40CBB5D405054DF3FF4C010F80FAC14
SHA-25666025798A8BC6C54A0887E92CE2C99B4FD542E5D3E595E3D4482919FADD9A838
Key Value
MD50F367DA5E323DCD2AA32AF20F6B0535E
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
PackageRelease7.fc34
PackageVersion4.94
SHA-1C78D25D13408D4FE00E7A1A42F95941CE1CA8947
SHA-2561454CB24671475622BE032316C953820A09B3219E06CE948F80D09010DF1307F
Key Value
MD5323E3A9CAAF6ED61F21F9D92AF4499D2
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.fc32
PackageVersion4.93
SHA-1A22CC593F42ACAE256D776B0DFC9740626E5B4A4
SHA-256531BB6AF1E0730AFE7BAF2C1DF84E1E1D10F670A44CE63A1D5F5B8A2C2D80387