aspose_email_cloud 20.12.0 → 21.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 98c75fe010400ae4891ce803ea59fee5e4530906bfcb3996065972e26ef36841
4
- data.tar.gz: 811860eebc195a763942b2900cb6ce55e7e1fd6a8fc1b839fcf988725b67c50d
3
+ metadata.gz: af4f01b0ed681cc4f8919e8b97eb964a3eb9effccae48919e4de64df2b8f4239
4
+ data.tar.gz: '07268e260e5ab75d5b895d37853d7b5eb9ca77457032925d183d0e6ede3dd8df'
5
5
  SHA512:
6
- metadata.gz: 29f99e42ac525bd806e8f7fd3c0d9c354cde93eb09c372dec7f5b9350900ab8c07cb5e50ec20164f7b7dbcfd4e567afe962ffa6492ec7ac6ba41b6b7fbc2f5eb
7
- data.tar.gz: 244e3b546cacbe815c9498a653dc363225060c7e896fb0c4d16e169699b0e4a2e5a70cf16d6cba26006b4e1d6dd3f9099139f858aa34cd5ab45c351f1d087d9e
6
+ metadata.gz: 257da5077ce1c84e2292712986232d780c2615a8be66674a07603ce3c4e324e877be133811bbeeab7edb4b1cce75bcfd0a6b56012f0015dfa670f3a9f3771d09
7
+ data.tar.gz: a942f89bfe647dd2315e564ad7413584293efdea5a51d635a456b755cb12b9f1f523dd5096a5f538b386e6aca7f064743362d1e096d974f41e84be0780b9d8b0
@@ -126,7 +126,7 @@ module AsposeEmailCloud
126
126
  end
127
127
 
128
128
  # Get messages from folder, filtered by query
129
- # The query string should have the following view. The example of a simple expression: '<Field name>' <Comparison operator> '<Field value>', where &lt;Field Name&gt; - the name of a message field through which filtering is made, &lt;Comparison operator&gt; - comparison operators, as their name implies, allow to compare message field and specified value, &lt;Field value&gt; - value to be compared with a message field. The number of simple expressions can make a compound one, ex.: (<Simple expression 1> & <Simple expression 2>) | <Simple expression 3 >, where \"&amp;\" - logical-AND operator, \"|\" - logical-OR operator At present the following values are allowed as a field name (<Field name>): \"To\" - represents a TO field of message, \"Text\" - represents string in the header or body of the message, \"Bcc\" - represents a BCC field of message, \"Body\" - represents a string in the body of message, \"Cc\" - represents a CC field of message, \"From\" - represents a From field of message, \"Subject\" - represents a string in the subject of message, \"InternalDate\" - represents an internal date of message, \"SentDate\" - represents a sent date of message Additionally, the following field names are allowed for IMAP-protocol: \"Answered\" - represents an /Answered flag of message \"Seen\" - represents a /Seen flag of message \"Flagged\" - represents a /Flagged flag of message \"Draft\" - represents a /Draft flag of message \"Deleted\" - represents a Deleted/ flag of message \"Recent\" - represents a Deleted/ flag of message \"MessageSize\" - represents a size (in bytes) of message Additionally, the following field names are allowed for Exchange: \"IsRead\" - Indicates whether the message has been read \"HasAttachment\" - Indicates whether or not the message has attachments \"IsSubmitted\" - Indicates whether the message has been submitted to the Outbox \"ContentClass\" - represents a content class of item Additionally, the following field names are allowed for pst/ost files: \"MessageClass\" - Represents a message class \"ContainerClass\" - Represents a folder container class \"Importance\" - Represents a message importance \"MessageSize\" - represents a size (in bytes) of message \"FolderName\" - represents a folder name \"ContentsCount\" - represents a total number of items in the folder \"UnreadContentsCount\" - represents the number of unread items in the folder. \"Subfolders\" - Indicates whether or not the folder has subfolders \"Read\" - the message is marked as having been read \"HasAttachment\" - the message has at least one attachment \"Unsent\" - the message is still being composed \"Unmodified\" - the message has not been modified since it was first saved (if unsent) or it was delivered (if sent) \"FromMe\" - the user receiving the message was also the user who sent the message \"Resend\" - the message includes a request for a resend operation with a non-delivery report \"NotifyRead\" - the user who sent the message has requested notification when a recipient first reads it \"NotifyUnread\" - the user who sent the message has requested notification when a recipient deletes it before reading or the Message object expires \"EverRead\" - the message has been read at least once The field value (<Field value>) can take the following values: For text fields - any string, For date type fields - the string of \"d-MMM-yyy\" format, ex. \"10-Feb-2009\", For flags (fields of boolean type) - either \"True\", or \"False\"
129
+ # The query string should have the following view. The example of a simple expression: '<Field name>' <Comparison operator> '<Field value>', where &lt;Field Name&gt; - the name of a message field through which filtering is made, &lt;Comparison operator&gt; - comparison operators, as their name implies, allow to compare message field and specified value, &lt;Field value&gt; - value to be compared with a message field. The number of simple expressions can make a compound one, ex.: (<Simple expression 1> & <Simple expression 2>) | <Simple expression 3 >, where \"&amp;\" - logical-AND operator, \"|\" - logical-OR operator At present the following values are allowed as a field name (<Field name>): \"To\" - represents a TO field of message, \"Text\" - represents string in the header or body of the message, \"Bcc\" - represents a BCC field of message, \"Body\" - represents a string in the body of message, \"Cc\" - represents a CC field of message, \"From\" - represents a From field of message, \"Subject\" - represents a string in the subject of message, \"InternalDate\" - represents an internal date of message, \"SentDate\" - represents a sent date of message Additionally, the following field names are allowed for IMAP-protocol: \"Answered\" - represents an /Answered flag of message \"Seen\" - represents a /Seen flag of message \"Flagged\" - represents a /Flagged flag of message \"Draft\" - represents a /Draft flag of message \"Deleted\" - represents a Deleted/ flag of message \"Recent\" - represents a Deleted/ flag of message \"MessageSize\" - represents a size (in bytes) of message Additionally, the following field names are allowed for Exchange: \"IsRead\" - Indicates whether the message has been read \"HasAttachment\" - Indicates whether or not the message has attachments \"IsSubmitted\" - Indicates whether the message has been submitted to the Outbox \"ContentClass\" - represents a content class of item The field value (<Field value>) can take the following values: For text fields - any string, For date type fields - the string of \"d-MMM-yyy\" format, ex. \"10-Feb-2009\", For flags (fields of boolean type) - either \"True\", or \"False\"
130
130
  # @param [ClientMessageListRequest] request Request object.
131
131
  # @return [MailMessageBaseList]
132
132
  def list(request)
@@ -55,7 +55,7 @@ module AsposeEmailCloud
55
55
  attr_accessor :format
56
56
 
57
57
  # Get messages from folder, filtered by query
58
- # The query string should have the following view. The example of a simple expression: &#39;&lt;Field name&gt;&#39; &lt;Comparison operator&gt; &#39;&lt;Field value&gt;&#39;, where &amp;lt;Field Name&amp;gt; - the name of a message field through which filtering is made, &amp;lt;Comparison operator&amp;gt; - comparison operators, as their name implies, allow to compare message field and specified value, &amp;lt;Field value&amp;gt; - value to be compared with a message field. The number of simple expressions can make a compound one, ex.: (&lt;Simple expression 1&gt; &amp; &lt;Simple expression 2&gt;) | &lt;Simple expression 3 &gt;, where \&quot;&amp;amp;\&quot; - logical-AND operator, \&quot;|\&quot; - logical-OR operator At present the following values are allowed as a field name (&lt;Field name&gt;): \&quot;To\&quot; - represents a TO field of message, \&quot;Text\&quot; - represents string in the header or body of the message, \&quot;Bcc\&quot; - represents a BCC field of message, \&quot;Body\&quot; - represents a string in the body of message, \&quot;Cc\&quot; - represents a CC field of message, \&quot;From\&quot; - represents a From field of message, \&quot;Subject\&quot; - represents a string in the subject of message, \&quot;InternalDate\&quot; - represents an internal date of message, \&quot;SentDate\&quot; - represents a sent date of message Additionally, the following field names are allowed for IMAP-protocol: \&quot;Answered\&quot; - represents an /Answered flag of message \&quot;Seen\&quot; - represents a /Seen flag of message \&quot;Flagged\&quot; - represents a /Flagged flag of message \&quot;Draft\&quot; - represents a /Draft flag of message \&quot;Deleted\&quot; - represents a Deleted/ flag of message \&quot;Recent\&quot; - represents a Deleted/ flag of message \&quot;MessageSize\&quot; - represents a size (in bytes) of message Additionally, the following field names are allowed for Exchange: \&quot;IsRead\&quot; - Indicates whether the message has been read \&quot;HasAttachment\&quot; - Indicates whether or not the message has attachments \&quot;IsSubmitted\&quot; - Indicates whether the message has been submitted to the Outbox \&quot;ContentClass\&quot; - represents a content class of item Additionally, the following field names are allowed for pst/ost files: \&quot;MessageClass\&quot; - Represents a message class \&quot;ContainerClass\&quot; - Represents a folder container class \&quot;Importance\&quot; - Represents a message importance \&quot;MessageSize\&quot; - represents a size (in bytes) of message \&quot;FolderName\&quot; - represents a folder name \&quot;ContentsCount\&quot; - represents a total number of items in the folder \&quot;UnreadContentsCount\&quot; - represents the number of unread items in the folder. \&quot;Subfolders\&quot; - Indicates whether or not the folder has subfolders \&quot;Read\&quot; - the message is marked as having been read \&quot;HasAttachment\&quot; - the message has at least one attachment \&quot;Unsent\&quot; - the message is still being composed \&quot;Unmodified\&quot; - the message has not been modified since it was first saved (if unsent) or it was delivered (if sent) \&quot;FromMe\&quot; - the user receiving the message was also the user who sent the message \&quot;Resend\&quot; - the message includes a request for a resend operation with a non-delivery report \&quot;NotifyRead\&quot; - the user who sent the message has requested notification when a recipient first reads it \&quot;NotifyUnread\&quot; - the user who sent the message has requested notification when a recipient deletes it before reading or the Message object expires \&quot;EverRead\&quot; - the message has been read at least once The field value (&lt;Field value&gt;) can take the following values: For text fields - any string, For date type fields - the string of \&quot;d-MMM-yyy\&quot; format, ex. \&quot;10-Feb-2009\&quot;, For flags (fields of boolean type) - either \&quot;True\&quot;, or \&quot;False\&quot;
58
+ # The query string should have the following view. The example of a simple expression: &#39;&lt;Field name&gt;&#39; &lt;Comparison operator&gt; &#39;&lt;Field value&gt;&#39;, where &amp;lt;Field Name&amp;gt; - the name of a message field through which filtering is made, &amp;lt;Comparison operator&amp;gt; - comparison operators, as their name implies, allow to compare message field and specified value, &amp;lt;Field value&amp;gt; - value to be compared with a message field. The number of simple expressions can make a compound one, ex.: (&lt;Simple expression 1&gt; &amp; &lt;Simple expression 2&gt;) | &lt;Simple expression 3 &gt;, where \&quot;&amp;amp;\&quot; - logical-AND operator, \&quot;|\&quot; - logical-OR operator At present the following values are allowed as a field name (&lt;Field name&gt;): \&quot;To\&quot; - represents a TO field of message, \&quot;Text\&quot; - represents string in the header or body of the message, \&quot;Bcc\&quot; - represents a BCC field of message, \&quot;Body\&quot; - represents a string in the body of message, \&quot;Cc\&quot; - represents a CC field of message, \&quot;From\&quot; - represents a From field of message, \&quot;Subject\&quot; - represents a string in the subject of message, \&quot;InternalDate\&quot; - represents an internal date of message, \&quot;SentDate\&quot; - represents a sent date of message Additionally, the following field names are allowed for IMAP-protocol: \&quot;Answered\&quot; - represents an /Answered flag of message \&quot;Seen\&quot; - represents a /Seen flag of message \&quot;Flagged\&quot; - represents a /Flagged flag of message \&quot;Draft\&quot; - represents a /Draft flag of message \&quot;Deleted\&quot; - represents a Deleted/ flag of message \&quot;Recent\&quot; - represents a Deleted/ flag of message \&quot;MessageSize\&quot; - represents a size (in bytes) of message Additionally, the following field names are allowed for Exchange: \&quot;IsRead\&quot; - Indicates whether the message has been read \&quot;HasAttachment\&quot; - Indicates whether or not the message has attachments \&quot;IsSubmitted\&quot; - Indicates whether the message has been submitted to the Outbox \&quot;ContentClass\&quot; - represents a content class of item The field value (&lt;Field value&gt;) can take the following values: For text fields - any string, For date type fields - the string of \&quot;d-MMM-yyy\&quot; format, ex. \&quot;10-Feb-2009\&quot;, For flags (fields of boolean type) - either \&quot;True\&quot;, or \&quot;False\&quot;
59
59
  # @param [String] folder A folder in email account
60
60
  # @param [String] account Email account
61
61
  # @param [String] query_string A MailQuery search string
@@ -37,12 +37,16 @@ module AsposeEmailCloud
37
37
  # Email account folder to move thread to.
38
38
  # @return [String]
39
39
  attr_accessor :destination_folder
40
+ # Email account folder to move thread from.
41
+ # @return [String]
42
+ attr_accessor :source_folder
40
43
  # Attribute mapping from ruby-style variable name to JSON key.
41
44
  def self.attribute_map
42
45
  {
43
46
  :'account_location' => :'accountLocation',
44
47
  :'thread_id' => :'threadId',
45
- :'destination_folder' => :'destinationFolder'
48
+ :'destination_folder' => :'destinationFolder',
49
+ :'source_folder' => :'sourceFolder'
46
50
  }
47
51
  end
48
52
 
@@ -51,7 +55,8 @@ module AsposeEmailCloud
51
55
  {
52
56
  :'account_location' => :'StorageFileLocation',
53
57
  :'thread_id' => :'String',
54
- :'destination_folder' => :'String'
58
+ :'destination_folder' => :'String',
59
+ :'source_folder' => :'String'
55
60
  }
56
61
  end
57
62
 
@@ -59,13 +64,16 @@ module AsposeEmailCloud
59
64
  # @param [StorageFileLocation] account_location Email client account configuration location on storage.
60
65
  # @param [String] thread_id Thread identifier.
61
66
  # @param [String] destination_folder Email account folder to move thread to.
67
+ # @param [String] source_folder Email account folder to move thread from.
62
68
  def initialize(
63
69
  account_location: nil,
64
70
  thread_id: nil,
65
- destination_folder: nil)
71
+ destination_folder: nil,
72
+ source_folder: nil)
66
73
  self.account_location = account_location if account_location
67
74
  self.thread_id = thread_id if thread_id
68
75
  self.destination_folder = destination_folder if destination_folder
76
+ self.source_folder = source_folder if source_folder
69
77
  end
70
78
 
71
79
  # Show invalid properties with the reasons. Usually used together with valid?
@@ -141,7 +149,8 @@ module AsposeEmailCloud
141
149
  self.class == o.class &&
142
150
  account_location == o.account_location &&
143
151
  thread_id == o.thread_id &&
144
- destination_folder == o.destination_folder
152
+ destination_folder == o.destination_folder &&
153
+ source_folder == o.source_folder
145
154
  end
146
155
 
147
156
  # @see the `==` method
@@ -153,7 +162,7 @@ module AsposeEmailCloud
153
162
  # Calculates hash code according to all attributes.
154
163
  # @return [Fixnum] Hash code
155
164
  def hash
156
- [account_location, thread_id, destination_folder].hash
165
+ [account_location, thread_id, destination_folder, source_folder].hash
157
166
  end
158
167
 
159
168
  # Builds the object from hash
@@ -11,5 +11,5 @@ Swagger Codegen version: 2.4.9
11
11
  =end
12
12
 
13
13
  module AsposeEmailCloud
14
- VERSION = '20.12.0'
14
+ VERSION = '21.4.0'
15
15
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: aspose_email_cloud
3
3
  version: !ruby/object:Gem::Version
4
- version: 20.12.0
4
+ version: 21.4.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Aspose.Email team
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2020-12-30 00:00:00.000000000 Z
11
+ date: 2021-04-13 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: faraday
@@ -28,22 +28,22 @@ dependencies:
28
28
  name: json
29
29
  requirement: !ruby/object:Gem::Requirement
30
30
  requirements:
31
- - - "~>"
32
- - !ruby/object:Gem::Version
33
- version: '2.1'
34
31
  - - ">="
35
32
  - !ruby/object:Gem::Version
36
33
  version: 2.1.0
34
+ - - "~>"
35
+ - !ruby/object:Gem::Version
36
+ version: '2.1'
37
37
  type: :runtime
38
38
  prerelease: false
39
39
  version_requirements: !ruby/object:Gem::Requirement
40
40
  requirements:
41
- - - "~>"
42
- - !ruby/object:Gem::Version
43
- version: '2.1'
44
41
  - - ">="
45
42
  - !ruby/object:Gem::Version
46
43
  version: 2.1.0
44
+ - - "~>"
45
+ - !ruby/object:Gem::Version
46
+ version: '2.1'
47
47
  - !ruby/object:Gem::Dependency
48
48
  name: mimemagic
49
49
  requirement: !ruby/object:Gem::Requirement
@@ -142,22 +142,22 @@ dependencies:
142
142
  name: rspec
143
143
  requirement: !ruby/object:Gem::Requirement
144
144
  requirements:
145
- - - "~>"
146
- - !ruby/object:Gem::Version
147
- version: '3.6'
148
145
  - - ">="
149
146
  - !ruby/object:Gem::Version
150
147
  version: 3.6.0
148
+ - - "~>"
149
+ - !ruby/object:Gem::Version
150
+ version: '3.6'
151
151
  type: :development
152
152
  prerelease: false
153
153
  version_requirements: !ruby/object:Gem::Requirement
154
154
  requirements:
155
- - - "~>"
156
- - !ruby/object:Gem::Version
157
- version: '3.6'
158
155
  - - ">="
159
156
  - !ruby/object:Gem::Version
160
157
  version: 3.6.0
158
+ - - "~>"
159
+ - !ruby/object:Gem::Version
160
+ version: '3.6'
161
161
  - !ruby/object:Gem::Dependency
162
162
  name: vcr
163
163
  requirement: !ruby/object:Gem::Requirement
@@ -499,7 +499,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
499
499
  - !ruby/object:Gem::Version
500
500
  version: '0'
501
501
  requirements: []
502
- rubygems_version: 3.1.4
502
+ rubygems_version: 3.0.3
503
503
  signing_key:
504
504
  specification_version: 4
505
505
  summary: A ruby wrapper for Aspose.Email for Cloud