Parents (Total: 113)

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

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/5.9/packages//mips64//cyrus-imapd-2.5.7.tgz
MD5	D965344E6D1102698C638BD81742D5BD
SHA-1	01A58E8D567B54FB7FDA57056214226C51E7FF86
SHA-256	685DC3D99542E771448C86CA43990E544241434A8DDE9E12B19B868F1AF502BB
SSDEEP	49152:D2dP6ZTZDHfs1XEuFR75aOkbn3oMHGuzb/MBgecc5ZUFOPUX:D2dSZx01XEuFR75aOU3uc/MB7SX
TLSH	T143B5238EB9E8293D63A4A237425F1F5F532E4BB055457EFBC80B20A5B8472829D321C7

Key	Value
MD5	830A756B9BD100AC4DDBA90B5D8AE232
PackageArch	armv7hl
PackageDescription	The 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.
PackageMaintainer	umeabot <umeabot>
PackageName	cyrus-imapd
PackageRelease	3.mga8
PackageVersion	2.5.15
SHA-1	06A37F3708C166B0415688B2EBB85411B54B8684
SHA-256	1028277F01028D5D007E7688289C850DDB6E7005E89211DAFFAE66A3E1C191EA

Key	Value
FileName	https://ftp.lysator.liu.se/pub/OpenBSD/5.9/packages//sparc64//cyrus-imapd-2.5.7.tgz
MD5	FFE080446A60B0534D189F597CD49F7F
SHA-1	07E68D6BE44AC061DA8AC94C19C141D73E32E790
SHA-256	38C7FEE413EC14E26832BAA38715D754D32D5E0C5B21D2B4DDDA32EF47F0794E
SSDEEP	49152:b1gfdThSe09jHQ48tzhi5Gr5sQ+CPa9Z+W/tApePUZ:RgfJB0VEtz9+Q+AaTCZ
TLSH	T1D7C5238ABBE466BF2320F027915F4F1F731E4A30A7413F57D85A3280759A3A1CD6259B

Key	Value
MD5	3F55D36CA0633FD9FC8B0725F2987669
PackageArch	x86_64
PackageDescription	The 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.
PackageMaintainer	mrambo3501 <mrambo3501>
PackageName	cyrus-imapd
PackageRelease	7.1.mga7
PackageVersion	2.5.11
SHA-1	0BAE9A68DEAED26FA10EAD3751CE8EDDB702B2F7
SHA-256	5D3CCA8FBB71545E76FF17EF170F44FA464A867DD2E64D6CA7D66CA0D2193121

Key	Value
MD5	43E06664AB90A4BDD0365984F8551133
PackageArch	aarch64
PackageDescription	The 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.
PackageMaintainer	daviddavid <daviddavid>
PackageName	cyrus-imapd
PackageRelease	1.mga7
PackageVersion	2.5.15
SHA-1	0F21C5128DBA948C1550E60C7AF3B83E737CF6C7
SHA-256	F32404CFCF609588F24FD9B10C525C1F8C6BB194F5767911D48EA03D493029EF

Key	Value
FileSize	218758
MD5	DCBBA07CF681DAD256E4081CADC10815
PackageDescription	Interface to Cyrus imap client imclient library The Cyrus::IMAP module provides an interface to the Cyrus imclient library. These are primarily useful for implementing cyradm operations within a Perl script; there are easier ways to implement general client operations, although they may be more limited in terms of authentication options when talking to a Cyrus imapd. . The modules that compose Cyrus::SIEVE are also included, but they are undocumented upstream. . For more information, please see the cyrus-common package.
PackageMaintainer	Debian Cyrus Team <pkg-cyrus-imapd-debian-devel@lists.alioth.debian.org>
PackageName	libcyrus-imap-perl
PackageSection	perl
PackageVersion	2.5.10-3+deb9u2
SHA-1	0FD06EC161C11800E9B45122F903F15EC1F10B56
SHA-256	3002B6B62491E500C1BF8A4F9AFE1FE29B5F64AF8257D0DAD5E8BC06EBFC4543

Key	Value
FileSize	180808
MD5	9376F7FB281D1689219A63B5A3CA97FC
PackageDescription	Interface to Cyrus imap client imclient library The Cyrus::IMAP module provides an interface to the Cyrus imclient library. These are primarily useful for implementing cyradm operations within a Perl script; there are easier ways to implement general client operations, although they may be more limited in terms of authentication options when talking to a Cyrus imapd. . The modules that compose Cyrus::SIEVE are also included, but they are undocumented upstream. . For more information, please see the cyrus-common package.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	libcyrus-imap-perl
PackageSection	perl
PackageVersion	2.5.9-2
SHA-1	12BB4F644707C0C094D2A6F1AE6AB974B0BE6C04
SHA-256	1328507C82AEA10697F9317AAC985AC07CD11036696D71C2DA5F2BF64432F7F7

Key	Value
MD5	A10CEAD05C3E5E5874EAC98100F427DF
PackageArch	x86_64
PackageDescription	The 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.
PackageMaintainer	luigiwalser <luigiwalser>
PackageName	cyrus-imapd
PackageRelease	7.mga7
PackageVersion	2.5.11
SHA-1	184BDD37100A2AF924C5352CB28A1D87E57C3F51
SHA-256	590E0CD376C3259CA7358C389FD0586FC8EE7BE0B7AC671EF25AF36B7B211308

Key	Value
FileSize	251704
MD5	7CF885B4E7165DAA9D1CF861801125AD
PackageDescription	Interface to Cyrus imap client imclient library The Cyrus::IMAP module provides an interface to the Cyrus imclient library. These are primarily useful for implementing cyradm operations within a Perl script; there are easier ways to implement general client operations, although they may be more limited in terms of authentication options when talking to a Cyrus imapd. . The modules that compose Cyrus::SIEVE are also included, but they are undocumented upstream. . For more information, please see the cyrus-common package.
PackageMaintainer	Debian Cyrus Team <team+cyrus@tracker.debian.org>
PackageName	libcyrus-imap-perl
PackageSection	perl
PackageVersion	2.5.11-1+b2
SHA-1	1C898069EBCB4C95499C6247904BCE092A8AB235
SHA-256	67318642B8E0CCC860F214B041366FD49DE5394AE071AF1E278098D8696C6FC4

Key	Value
FileSize	212360
MD5	972DC093F20A357DEE8C7790BF76D086
PackageDescription	Interface to Cyrus imap client imclient library The Cyrus::IMAP module provides an interface to the Cyrus imclient library. These are primarily useful for implementing cyradm operations within a Perl script; there are easier ways to implement general client operations, although they may be more limited in terms of authentication options when talking to a Cyrus imapd. . The modules that compose Cyrus::SIEVE are also included, but they are undocumented upstream. . For more information, please see the cyrus-common package.
PackageMaintainer	Debian Cyrus Team <pkg-cyrus-imapd-debian-devel@lists.alioth.debian.org>
PackageName	libcyrus-imap-perl
PackageSection	perl
PackageVersion	2.5.10-3+deb9u2
SHA-1	24CBB4CB1DA3551ADC97D27AD5F805AF36769CA2
SHA-256	6070DB91814BE3869D24029EFFE4EE7CEC82D20526472F2C2567E4CC6E593E39