libraries/libvmime-zarafa: Removed (build failure)

1 files changed, 0 insertions, 140 deletions

diff --git a/libraries/libvmime-zarafa/zarafa-patches/PATCHES b/libraries/libvmime-zarafa/zarafa-patches/PATCHES
deleted file mode 100644
index a316eda3628e5..0000000000000
--- a/libraries/libvmime-zarafa/zarafa-patches/PATCHES
+++ /dev/null
@@ -1,140 +0,0 @@
-Patches
-
-The following patches are applied by Zarafa to the vmime library, in order of creation date.
-
-
-vmime-charset-catch.diff
-
-	Early catches an exception of vmime when iconv was unable to convert a word from or to the requested charsets. This makes broken mails with invalid characters for a valid charset still be able to deliver. We'd rather have an email with a ? sign than a FallbackDelivery for the user.
-
-
-vmime-missing-boundary.diff
-
-	Broken emails without a final boundary will still be able to deliver with all attachments. The final part without the boundary will be treated as an attachment.
-
-
-vmime-allow-no-recips-and-senders.diff
-
-	Makes the messageBuilder helper generate an mail without To or Cc headers. This way, an email with only Bcc entries will still be sent. This feature is mostly used by people to mask a mailing list or invitation that should be send to alot of people.
-
-
-vmime-bmoted-printable.diff
-
-		We've seen broken mails with an invalid encoding. Unsure what 'bmoted-printable' actually is, we make vmime treat it as normal quoted-printable.
-
-
-vmime-strip-header-endspaces.diff
-
-	This patch makes sure that vmime does not parse trailing spaces on an header. Otherwise vmime will throw an exception and a fallback delivery wil be started.
-
-
-vmime-attachfnamelen.diff
-
-	Fixes parsing of an attachment filename that is between 66 and 76 characters long.
-
-
-vmime-remove-bcc.diff
-
-	Bcc headers should not be send to the SMTP server. Some SMTP server automatically strip this header (Postfix, qmail), and others have an option for this (Exim).
-
-
-vmime-mdn-disposition.diff
-
-	Fixes a small but crusial typo in a header of an MDN (read receipt) mail.
-
-
-vmime-mdn-final-recipient.diff
-
-	A header with the final recipient information was created, but not added to the MDN email. This patch adds this information to the mail.
-
-
-vmime-broken-locale-error.diff
-
-	On [WWW] Debian machines, you need to configure the locales (languages) that will be used on the system. When you use a locale (eg. LC_MESSAGES=nl_NL, but did not configure your distribution to have this locale present on your system, a NULL pointer would have thrown an exception in the std::string class. This makes sure that exception never happends.
-
-
-vmime-qp-starts-on-second-line.diff
-
-	Headers can be broken over multiple lines in an email. When the wrapped line directly started with quoted-printable, vmime copied this text as normal text, in stead of parsing it as quoted-printable.
-
-
-vmime-quoted-printable-specials.diff
-
-	This patch adds some characters that should be "escaped" in quoted-printable. With this fix you can have these characters in a fullname of an email address.
-
-
-vmime-header-value-on-next-line.diff
-
-	When an email header has the data part on the second line, vmime was unable to parse this data and skip adds the header as empty to it's internal structures. This makes sure these headers are still correctly parsed.
-
-
-vmime-oe-compatibility.diff
-
-	Fixes attachment names in Outlook Express which are long and have high characters.
-
-
-vmime-unicode-1-1-utf-7-charset.diff
-
-	Some mails have a special definition of the utf-7 character set, named unicode-1-1-utf-7. Since this name is not defined by iconv, we rename it to utf-7.
-
-
-vmime-out-of-bounds-copy.diff
-
-	When a line in a plain text mail starts with a '.', the character needs to be escaped. VMime has a special filter for this, but due to a bug in this filter, a second line starting with a '.' would trigger a wrong buffer copy, and your email would contain double parts.
-
-
-vmime-default-transfer-encoding.diff
-
-	Some broken generators may set the Content-Tranfer-Encoding header, but did not set any value. We'll assume the default value '7bit'.
-
-
-vmime-contentid-without-at.diff
-
-	Enables re-generation of broken content-id's that had no @ sign in them.
-
-
-vmime-socket-backport-and-timeout-fix.diff
-
-	Small partial backport of some socket handling code from 0.8.1
-	Only receiving data is handled better. It also has a timeout, when receiving data from a socket hasn't worked for 5 minutes. This isn't present in 0.8.1.
-
-
-vmime-double-empty-boundary.diff
-
-	When an email contains the same boundary to announce a new body part directly one after another, vmime would have crashed because the body part added to the object with size of (size_type)(-1). Thus having a body part of 4294967294 bytes on 32bit and 18446744073709551615 bytes on 64bit systems.
-
-
-vmime-quoted-printable-encode-questionmark.diff
-
-	Special characters break the quotedprintable encoding when they are typed after a ?. This fix also encodes ?-characters, so we can't break the encoding with this trick.
-
-
-vmime-gcc-4.3-support.diff
-
-	Adds required include headers to compile with g++-4.3.
-
-vmime-charset-output-buffer.diff
-
-	Fixes iconv conversion with source buffers >64Kb not to add a '?' and skip one byte of the input buffer.
-
-vmime-timezone-name.diff
-
-	Fixes dates in headers which use a timezone definition, instead of a numeric timezone offset.
-
-vmime-socket-tcp-nodelay.diff
-
-	Adds the TCP_NODELAY flag to vmime sockets. This makes the SMTP connection much faster.
-
-vmime-threading-remove-static_non-abi-change.diff
-
-	Workaround a static variable in the smart_ptr class using a pthread mutex, which fixes multi-threading issues in libvmime.
-
-vmime-gcc-4.4-support.diff
-
-	Adds required include headers to compile with g++-4.4.
-
-vmime-plain-bodycopy.diff
-
-	When constructing a plaintext only body without attachments, a copy of the body was made to set as the real body, and thus
-	removing all the multiparts. However, the same reference is removed before setting the new body, thus invalidating that body
-	we wish to copy, possibly resulting in a crash.