Result for 07D4F5DEBE315D61FCFF3B5CE061CE6F875F7817

Query result

Key Value
FileName./usr/lib/.build-id/b1/0525f656b554408a89b8ff2b86e93419c486b0
FileSize43
MD53A92240833CA1B3E0B2AD378084488C7
SHA-107D4F5DEBE315D61FCFF3B5CE061CE6F875F7817
SHA-2567DE49A3149FF9A040C4A5D31396B5C8DA09A9FD348E7B21AB70307F3E43A6F85
SSDEEP3:gCD/kIKrKGd6jQQ:X/BFGdK
TLSH
hashlookup:parent-total24
hashlookup:trust100

Network graph view

Parents (Total: 24)

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

Key Value
MD5830A756B9BD100AC4DDBA90B5D8AE232
PackageArcharmv7hl
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerumeabot <umeabot>
PackageNamecyrus-imapd
PackageRelease3.mga8
PackageVersion2.5.15
SHA-106A37F3708C166B0415688B2EBB85411B54B8684
SHA-2561028277F01028D5D007E7688289C850DDB6E7005E89211DAFFAE66A3E1C191EA
Key Value
MD53F55D36CA0633FD9FC8B0725F2987669
PackageArchx86_64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainermrambo3501 <mrambo3501>
PackageNamecyrus-imapd
PackageRelease7.1.mga7
PackageVersion2.5.11
SHA-10BAE9A68DEAED26FA10EAD3751CE8EDDB702B2F7
SHA-2565D3CCA8FBB71545E76FF17EF170F44FA464A867DD2E64D6CA7D66CA0D2193121
Key Value
MD543E06664AB90A4BDD0365984F8551133
PackageArchaarch64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerdaviddavid <daviddavid>
PackageNamecyrus-imapd
PackageRelease1.mga7
PackageVersion2.5.15
SHA-10F21C5128DBA948C1550E60C7AF3B83E737CF6C7
SHA-256F32404CFCF609588F24FD9B10C525C1F8C6BB194F5767911D48EA03D493029EF
Key Value
MD5A10CEAD05C3E5E5874EAC98100F427DF
PackageArchx86_64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerluigiwalser <luigiwalser>
PackageNamecyrus-imapd
PackageRelease7.mga7
PackageVersion2.5.11
SHA-1184BDD37100A2AF924C5352CB28A1D87E57C3F51
SHA-256590E0CD376C3259CA7358C389FD0586FC8EE7BE0B7AC671EF25AF36B7B211308
Key Value
MD56486839447458E87389B98BE739D4745
PackageArcharmv7hl
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerns80 <ns80>
PackageNamecyrus-imapd
PackageRelease3.1.mga8
PackageVersion2.5.15
SHA-1318DA60A39DA97D917846ECB8F3443A9BC55921D
SHA-256F26EF8155FEB0E9BF8740C7C56C5D21BC2A16B4F24CA4644CBB1E21ABFACA2D7
Key Value
MD50C27D0C8C9DF4268C858936E1EED6488
PackageArchx86_64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerdaviddavid <daviddavid>
PackageNamecyrus-imapd
PackageRelease1.mga7
PackageVersion2.5.15
SHA-1326610E292D81439DD54F76257B5811274990191
SHA-256F8934F97975B002326F3AA7508830D04E3D3FD2D0B332521D1A0AE68A9B28401
Key Value
MD5960D8EA5BFD25B5C8AF004C7C7DD6EB5
PackageArchx86_64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerumeabot <umeabot>
PackageNamecyrus-imapd
PackageRelease3.mga8
PackageVersion2.5.15
SHA-14E19AD902D483B2740F5D6BD62407B5B1696AA1F
SHA-2569E9A1F2B609704C0D4EA6D47484A5E583524836A1363655D7DFF6B63EF211780
Key Value
MD5927038396E9C0C0B5D47670F4217BBBB
PackageArchi586
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerluigiwalser <luigiwalser>
PackageNamecyrus-imapd
PackageRelease7.mga7
PackageVersion2.5.11
SHA-159A93C68F42E8DA668D849A493F9E662D072D375
SHA-2564E9DB2E1A68E15FDAC600CAFF5EC568E7AB8AAFCAA3D05C712282DAB098E0F3D
Key Value
MD5B1584D140EB4D16436E0F40C6F6CBFF2
PackageArchaarch64
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerns80 <ns80>
PackageNamecyrus-imapd
PackageRelease9.mga9
PackageVersion2.5.15
SHA-163B14BF903F6E809B0BD92DD13C7724BD89CC8CF
SHA-25689CDF9DC74202D4EF1856D5A74E974B96A48AF96E9F1437E61F53A2FE814354B
Key Value
MD5AEF1D2606BCF8B7B0BAB9634F94F4597
PackageArchi586
PackageDescriptionThe cyrus-imapd package contains the core of the Cyrus IMAP server. It is a scaleable enterprise mail system designed for use from small to large enterprise environments using standards-based internet mail technologies. A full Cyrus IMAP implementation allows a seamless mail and bulletin board environment to be set up across multiple servers. It differs from other IMAP server implementations in that it is run on "sealed" servers, where users are not normally permitted to log in and have no system account on the server. The mailbox database is stored in parts of the filesystem that are private to the Cyrus IMAP server. All user access to mail is through software using the IMAP, POP3 or KPOP protocols. It also includes support for virtual domains, NNTP, mailbox annotations, and much more. The private mailbox database design gives the server large advantages in efficiency, scalability and administratability. Multiple concurrent read/write connections to the same mailbox are permitted. The server supports access control lists on mailboxes and storage quotas on mailbox hierarchies. The Cyrus IMAP server supports the IMAP4rev1 protocol described in RFC 3501. IMAP4rev1 has been approved as a proposed standard. It supports any authentication mechanism available from the SASL library, imaps/pop3s/nntps (IMAP/POP3/NNTP encrypted using SSL and TLSv1) can be used for security. The server supports single instance store where possible when an email message is addressed to multiple recipients, SIEVE provides server side email filtering.
PackageMaintainerdaviddavid <daviddavid>
PackageNamecyrus-imapd
PackageRelease1.mga7
PackageVersion2.5.15
SHA-16A37B835BEC6B6535E38E92F1DB60D504C878A13
SHA-2562CC84505E611E78F06E145002CFD0F09595F7EB3D690AD8F42A6BAF14BFCDB0F