eventmachine 0.12.6-x86-mswin32-60 → 0.12.8-x86-mswin32-60

Sign up to get free protection for your applications and to get access to all the features.
Files changed (116) hide show
  1. data/{docs/README → README} +21 -13
  2. data/Rakefile +14 -4
  3. data/docs/DEFERRABLES +0 -5
  4. data/docs/INSTALL +2 -4
  5. data/docs/LEGAL +1 -1
  6. data/docs/LIGHTWEIGHT_CONCURRENCY +0 -2
  7. data/docs/PURE_RUBY +0 -2
  8. data/docs/RELEASE_NOTES +0 -2
  9. data/docs/SMTP +0 -7
  10. data/docs/SPAWNED_PROCESSES +0 -4
  11. data/docs/TODO +0 -2
  12. data/eventmachine.gemspec +41 -32
  13. data/examples/ex_channel.rb +43 -0
  14. data/examples/ex_queue.rb +2 -0
  15. data/examples/helper.rb +2 -0
  16. data/ext/cmain.cpp +685 -586
  17. data/ext/cplusplus.cpp +15 -6
  18. data/ext/ed.cpp +1732 -1522
  19. data/ext/ed.h +407 -380
  20. data/ext/em.cpp +2263 -1937
  21. data/ext/em.h +223 -186
  22. data/ext/eventmachine.h +111 -98
  23. data/ext/eventmachine_cpp.h +1 -0
  24. data/ext/extconf.rb +4 -0
  25. data/ext/kb.cpp +81 -82
  26. data/ext/pipe.cpp +349 -351
  27. data/ext/project.h +21 -0
  28. data/ext/rubymain.cpp +1047 -847
  29. data/ext/ssl.cpp +38 -1
  30. data/ext/ssl.h +5 -1
  31. data/java/src/com/rubyeventmachine/Application.java +7 -3
  32. data/java/src/com/rubyeventmachine/EmReactor.java +16 -1
  33. data/java/src/com/rubyeventmachine/tests/ConnectTest.java +25 -3
  34. data/lib/{protocols → em}/buftok.rb +16 -5
  35. data/lib/em/callback.rb +26 -0
  36. data/lib/em/channel.rb +57 -0
  37. data/lib/em/connection.rb +505 -0
  38. data/lib/em/deferrable.rb +144 -165
  39. data/lib/em/file_watch.rb +54 -0
  40. data/lib/em/future.rb +24 -25
  41. data/lib/em/messages.rb +1 -1
  42. data/lib/em/process_watch.rb +44 -0
  43. data/lib/em/processes.rb +119 -113
  44. data/lib/em/protocols.rb +35 -0
  45. data/lib/em/protocols/header_and_content.rb +138 -0
  46. data/lib/em/protocols/httpclient.rb +263 -0
  47. data/lib/em/protocols/httpclient2.rb +582 -0
  48. data/lib/{protocols → em/protocols}/line_and_text.rb +2 -2
  49. data/lib/em/protocols/linetext2.rb +160 -0
  50. data/lib/{protocols → em/protocols}/memcache.rb +37 -7
  51. data/lib/em/protocols/object_protocol.rb +39 -0
  52. data/lib/em/protocols/postgres3.rb +247 -0
  53. data/lib/em/protocols/saslauth.rb +175 -0
  54. data/lib/em/protocols/smtpclient.rb +331 -0
  55. data/lib/em/protocols/smtpserver.rb +547 -0
  56. data/lib/em/protocols/stomp.rb +200 -0
  57. data/lib/{protocols → em/protocols}/tcptest.rb +21 -25
  58. data/lib/em/queue.rb +61 -0
  59. data/lib/em/spawnable.rb +53 -56
  60. data/lib/em/streamer.rb +92 -74
  61. data/lib/em/timers.rb +55 -0
  62. data/lib/em/version.rb +3 -0
  63. data/lib/eventmachine.rb +1636 -1926
  64. data/lib/evma.rb +1 -1
  65. data/lib/jeventmachine.rb +106 -101
  66. data/lib/pr_eventmachine.rb +47 -36
  67. data/tasks/project.rake +2 -1
  68. data/tests/client.crt +31 -0
  69. data/tests/client.key +51 -0
  70. data/tests/test_attach.rb +18 -0
  71. data/tests/test_basic.rb +285 -231
  72. data/tests/test_channel.rb +63 -0
  73. data/tests/test_connection_count.rb +2 -2
  74. data/tests/test_epoll.rb +162 -163
  75. data/tests/test_errors.rb +36 -36
  76. data/tests/test_exc.rb +22 -25
  77. data/tests/test_file_watch.rb +49 -0
  78. data/tests/test_futures.rb +77 -93
  79. data/tests/test_hc.rb +2 -2
  80. data/tests/test_httpclient.rb +55 -52
  81. data/tests/test_httpclient2.rb +153 -155
  82. data/tests/test_inactivity_timeout.rb +30 -0
  83. data/tests/test_kb.rb +8 -9
  84. data/tests/test_ltp2.rb +274 -277
  85. data/tests/test_next_tick.rb +135 -109
  86. data/tests/test_object_protocol.rb +37 -0
  87. data/tests/test_process_watch.rb +48 -0
  88. data/tests/test_processes.rb +128 -95
  89. data/tests/test_proxy_connection.rb +92 -0
  90. data/tests/test_pure.rb +1 -5
  91. data/tests/test_queue.rb +44 -0
  92. data/tests/test_running.rb +9 -14
  93. data/tests/test_sasl.rb +32 -34
  94. data/tests/test_send_file.rb +175 -176
  95. data/tests/test_servers.rb +37 -41
  96. data/tests/test_smtpserver.rb +47 -55
  97. data/tests/test_spawn.rb +284 -291
  98. data/tests/test_ssl_args.rb +1 -1
  99. data/tests/test_ssl_methods.rb +1 -1
  100. data/tests/test_ssl_verify.rb +82 -0
  101. data/tests/test_timers.rb +81 -88
  102. data/tests/test_ud.rb +0 -7
  103. data/tests/testem.rb +1 -1
  104. metadata +52 -36
  105. data/lib/em/eventable.rb +0 -39
  106. data/lib/eventmachine_version.rb +0 -31
  107. data/lib/protocols/header_and_content.rb +0 -129
  108. data/lib/protocols/httpcli2.rb +0 -803
  109. data/lib/protocols/httpclient.rb +0 -270
  110. data/lib/protocols/linetext2.rb +0 -161
  111. data/lib/protocols/postgres.rb +0 -261
  112. data/lib/protocols/saslauth.rb +0 -179
  113. data/lib/protocols/smtpclient.rb +0 -308
  114. data/lib/protocols/smtpserver.rb +0 -556
  115. data/lib/protocols/stomp.rb +0 -153
  116. data/tests/test_eventables.rb +0 -77
@@ -0,0 +1,547 @@
1
+ #--
2
+ #
3
+ # Author:: Francis Cianfrocca (gmail: blackhedd)
4
+ # Homepage:: http://rubyeventmachine.com
5
+ # Date:: 16 July 2006
6
+ #
7
+ # See EventMachine and EventMachine::Connection for documentation and
8
+ # usage examples.
9
+ #
10
+ #----------------------------------------------------------------------------
11
+ #
12
+ # Copyright (C) 2006-07 by Francis Cianfrocca. All Rights Reserved.
13
+ # Gmail: blackhedd
14
+ #
15
+ # This program is free software; you can redistribute it and/or modify
16
+ # it under the terms of either: 1) the GNU General Public License
17
+ # as published by the Free Software Foundation; either version 2 of the
18
+ # License, or (at your option) any later version; or 2) Ruby's License.
19
+ #
20
+ # See the file COPYING for complete licensing information.
21
+ #
22
+ #---------------------------------------------------------------------------
23
+ #
24
+ #
25
+
26
+ module EventMachine
27
+ module Protocols
28
+
29
+ # This is a protocol handler for the server side of SMTP.
30
+ # It's NOT a complete SMTP server obeying all the semantics of servers conforming to
31
+ # RFC2821. Rather, it uses overridable method stubs to communicate protocol states
32
+ # and data to user code. User code is responsible for doing the right things with the
33
+ # data in order to get complete and correct SMTP server behavior.
34
+ #
35
+ #--
36
+ # Useful paragraphs in RFC-2821:
37
+ # 4.3.2: Concise list of command-reply sequences, in essence a text representation
38
+ # of the command state-machine.
39
+ #
40
+ # STARTTLS is defined in RFC2487.
41
+ # Observe that there are important rules governing whether a publicly-referenced server
42
+ # (meaning one whose Internet address appears in public MX records) may require the
43
+ # non-optional use of TLS.
44
+ # Non-optional TLS does not apply to EHLO, NOOP, QUIT or STARTTLS.
45
+ class SmtpServer < EventMachine::Connection
46
+ include Protocols::LineText2
47
+
48
+ HeloRegex = /\AHELO\s*/i
49
+ EhloRegex = /\AEHLO\s*/i
50
+ QuitRegex = /\AQUIT/i
51
+ MailFromRegex = /\AMAIL FROM:\s*/i
52
+ RcptToRegex = /\ARCPT TO:\s*/i
53
+ DataRegex = /\ADATA/i
54
+ NoopRegex = /\ANOOP/i
55
+ RsetRegex = /\ARSET/i
56
+ VrfyRegex = /\AVRFY\s+/i
57
+ ExpnRegex = /\AEXPN\s+/i
58
+ HelpRegex = /\AHELP/i
59
+ StarttlsRegex = /\ASTARTTLS/i
60
+ AuthRegex = /\AAUTH\s+/i
61
+
62
+
63
+ # Class variable containing default parameters that can be overridden
64
+ # in application code.
65
+ # Individual objects of this class will make an instance-local copy of
66
+ # the class variable, so that they can be reconfigured on a per-instance
67
+ # basis.
68
+ #
69
+ # Chunksize is the number of data lines we'll buffer before
70
+ # sending them to the application. TODO, make this user-configurable.
71
+ #
72
+ @@parms = {
73
+ :chunksize => 4000,
74
+ :verbose => false
75
+ }
76
+ def self.parms= parms={}
77
+ @@parms.merge!(parms)
78
+ end
79
+
80
+
81
+
82
+ def initialize *args
83
+ super
84
+ @parms = @@parms
85
+ init_protocol_state
86
+ end
87
+
88
+ def parms= parms={}
89
+ @parms.merge!(parms)
90
+ end
91
+
92
+ # In SMTP, the server talks first. But by a (perhaps flawed) axiom in EM,
93
+ # #post_init will execute BEFORE the block passed to #start_server, for any
94
+ # given accepted connection. Since in this class we'll probably be getting
95
+ # a lot of initialization parameters, we want the guts of post_init to
96
+ # run AFTER the application has initialized the connection object. So we
97
+ # use a spawn to schedule the post_init to run later.
98
+ # It's a little weird, I admit. A reasonable alternative would be to set
99
+ # parameters as a class variable and to do that before accepting any connections.
100
+ #
101
+ # OBSOLETE, now we have @@parms. But the spawn is nice to keep as an illustration.
102
+ #
103
+ def post_init
104
+ #send_data "220 #{get_server_greeting}\r\n" (ORIGINAL)
105
+ #(EM.spawn {|x| x.send_data "220 #{x.get_server_greeting}\r\n"}).notify(self)
106
+ (EM.spawn {|x| x.send_server_greeting}).notify(self)
107
+ end
108
+
109
+ def send_server_greeting
110
+ send_data "220 #{get_server_greeting}\r\n"
111
+ end
112
+
113
+ def receive_line ln
114
+ @@parms[:verbose] and $>.puts ">>> #{ln}"
115
+
116
+ return process_data_line(ln) if @state.include?(:data)
117
+
118
+ case ln
119
+ when EhloRegex
120
+ process_ehlo $'.dup
121
+ when HeloRegex
122
+ process_helo $'.dup
123
+ when MailFromRegex
124
+ process_mail_from $'.dup
125
+ when RcptToRegex
126
+ process_rcpt_to $'.dup
127
+ when DataRegex
128
+ process_data
129
+ when RsetRegex
130
+ process_rset
131
+ when VrfyRegex
132
+ process_vrfy
133
+ when ExpnRegex
134
+ process_expn
135
+ when HelpRegex
136
+ process_help
137
+ when NoopRegex
138
+ process_noop
139
+ when QuitRegex
140
+ process_quit
141
+ when StarttlsRegex
142
+ process_starttls
143
+ when AuthRegex
144
+ process_auth $'.dup
145
+ else
146
+ process_unknown
147
+ end
148
+ end
149
+
150
+ # TODO - implement this properly, the implementation is a stub!
151
+ def process_vrfy
152
+ send_data "250 Ok, but unimplemented\r\n"
153
+ end
154
+ # TODO - implement this properly, the implementation is a stub!
155
+ def process_help
156
+ send_data "250 Ok, but unimplemented\r\n"
157
+ end
158
+ # TODO - implement this properly, the implementation is a stub!
159
+ def process_expn
160
+ send_data "250 Ok, but unimplemented\r\n"
161
+ end
162
+
163
+ #--
164
+ # This is called at several points to restore the protocol state
165
+ # to a pre-transaction state. In essence, we "forget" having seen
166
+ # any valid command except EHLO and STARTTLS.
167
+ # We also have to callback user code, in case they're keeping track
168
+ # of senders, recipients, and whatnot.
169
+ #
170
+ # We try to follow the convention of avoiding the verb "receive" for
171
+ # internal method names except receive_line (which we inherit), and
172
+ # using only receive_xxx for user-overridable stubs.
173
+ #
174
+ # init_protocol_state is called when we initialize the connection as
175
+ # well as during reset_protocol_state. It does NOT call the user
176
+ # override method. This enables us to promise the users that they
177
+ # won't see the overridable fire except after EHLO and RSET, and
178
+ # after a message has been received. Although the latter may be wrong.
179
+ # The standard may allow multiple DATA segments with the same set of
180
+ # senders and recipients.
181
+ #
182
+ def reset_protocol_state
183
+ init_protocol_state
184
+ s,@state = @state,[]
185
+ @state << :starttls if s.include?(:starttls)
186
+ @state << :ehlo if s.include?(:ehlo)
187
+ receive_transaction
188
+ end
189
+ def init_protocol_state
190
+ @state ||= []
191
+ end
192
+
193
+
194
+ #--
195
+ # EHLO/HELO is always legal, per the standard. On success
196
+ # it always clears buffers and initiates a mail "transaction."
197
+ # Which means that a MAIL FROM must follow.
198
+ #
199
+ # Per the standard, an EHLO/HELO or a RSET "initiates" an email
200
+ # transaction. Thereafter, MAIL FROM must be received before
201
+ # RCPT TO, before DATA. Not sure what this specific ordering
202
+ # achieves semantically, but it does make it easier to
203
+ # implement. We also support user-specified requirements for
204
+ # STARTTLS and AUTH. We make it impossible to proceed to MAIL FROM
205
+ # without fulfilling tls and/or auth, if the user specified either
206
+ # or both as required. We need to check the extension standard
207
+ # for auth to see if a credential is discarded after a RSET along
208
+ # with all the rest of the state. We'll behave as if it is.
209
+ # Now clearly, we can't discard tls after its been negotiated
210
+ # without dropping the connection, so that flag doesn't get cleared.
211
+ #
212
+ def process_ehlo domain
213
+ if receive_ehlo_domain domain
214
+ send_data "250-#{get_server_domain}\r\n"
215
+ if @@parms[:starttls]
216
+ send_data "250-STARTTLS\r\n"
217
+ end
218
+ if @@parms[:auth]
219
+ send_data "250-AUTH PLAIN LOGIN\r\n"
220
+ end
221
+ send_data "250-NO-SOLICITING\r\n"
222
+ # TODO, size needs to be configurable.
223
+ send_data "250 SIZE 20000000\r\n"
224
+ reset_protocol_state
225
+ @state << :ehlo
226
+ else
227
+ send_data "550 Requested action not taken\r\n"
228
+ end
229
+ end
230
+
231
+ def process_helo domain
232
+ if receive_ehlo_domain domain.dup
233
+ send_data "250 #{get_server_domain}\r\n"
234
+ reset_protocol_state
235
+ @state << :ehlo
236
+ else
237
+ send_data "550 Requested action not taken\r\n"
238
+ end
239
+ end
240
+
241
+ def process_quit
242
+ send_data "221 Ok\r\n"
243
+ close_connection_after_writing
244
+ end
245
+
246
+ def process_noop
247
+ send_data "250 Ok\r\n"
248
+ end
249
+
250
+ def process_unknown
251
+ send_data "500 Unknown command\r\n"
252
+ end
253
+
254
+ #--
255
+ # So far, only AUTH PLAIN is supported but we should do at least LOGIN as well.
256
+ # TODO, support clients that send AUTH PLAIN with no parameter, expecting a 3xx
257
+ # response and a continuation of the auth conversation.
258
+ #
259
+ def process_auth str
260
+ if @state.include?(:auth)
261
+ send_data "503 auth already issued\r\n"
262
+ elsif str =~ /\APLAIN\s+/i
263
+ plain = ($'.dup).unpack("m").first # Base64::decode64($'.dup)
264
+ discard,user,psw = plain.split("\000")
265
+ if receive_plain_auth user,psw
266
+ send_data "235 authentication ok\r\n"
267
+ @state << :auth
268
+ else
269
+ send_data "535 invalid authentication\r\n"
270
+ end
271
+ #elsif str =~ /\ALOGIN\s+/i
272
+ else
273
+ send_data "504 auth mechanism not available\r\n"
274
+ end
275
+ end
276
+
277
+ #--
278
+ # Unusually, we can deal with a Deferrable returned from the user application.
279
+ # This was added to deal with a special case in a particular application, but
280
+ # it would be a nice idea to add it to the other user-code callbacks.
281
+ #
282
+ def process_data
283
+ unless @state.include?(:rcpt)
284
+ send_data "503 Operation sequence error\r\n"
285
+ else
286
+ succeeded = proc {
287
+ send_data "354 Send it\r\n"
288
+ @state << :data
289
+ @databuffer = []
290
+ }
291
+ failed = proc {
292
+ send_data "550 Operation failed\r\n"
293
+ }
294
+
295
+ d = receive_data_command
296
+
297
+ if d.respond_to?(:callback)
298
+ d.callback(&succeeded)
299
+ d.errback(&failed)
300
+ else
301
+ (d ? succeeded : failed).call
302
+ end
303
+ end
304
+ end
305
+
306
+ def process_rset
307
+ reset_protocol_state
308
+ receive_reset
309
+ send_data "250 Ok\r\n"
310
+ end
311
+
312
+ def unbind
313
+ connection_ended
314
+ end
315
+
316
+ #--
317
+ # STARTTLS may not be issued before EHLO, or unless the user has chosen
318
+ # to support it.
319
+ # TODO, must support user-supplied certificates.
320
+ #
321
+ def process_starttls
322
+ if @@parms[:starttls]
323
+ if @state.include?(:starttls)
324
+ send_data "503 TLS Already negotiated\r\n"
325
+ elsif ! @state.include?(:ehlo)
326
+ send_data "503 EHLO required before STARTTLS\r\n"
327
+ else
328
+ send_data "220 Start TLS negotiation\r\n"
329
+ start_tls
330
+ @state << :starttls
331
+ end
332
+ else
333
+ process_unknown
334
+ end
335
+ end
336
+
337
+
338
+ #--
339
+ # Requiring TLS is touchy, cf RFC2784.
340
+ # Requiring AUTH seems to be much more reasonable.
341
+ # We don't currently support any notion of deriving an authentication from the TLS
342
+ # negotiation, although that would certainly be reasonable.
343
+ # We DON'T allow MAIL FROM to be given twice.
344
+ # We DON'T enforce all the various rules for validating the sender or
345
+ # the reverse-path (like whether it should be null), and notifying the reverse
346
+ # path in case of delivery problems. All of that is left to the calling application.
347
+ #
348
+ def process_mail_from sender
349
+ if (@@parms[:starttls]==:required and !@state.include?(:starttls))
350
+ send_data "550 This server requires STARTTLS before MAIL FROM\r\n"
351
+ elsif (@@parms[:auth]==:required and !@state.include?(:auth))
352
+ send_data "550 This server requires authentication before MAIL FROM\r\n"
353
+ elsif @state.include?(:mail_from)
354
+ send_data "503 MAIL already given\r\n"
355
+ else
356
+ unless receive_sender sender
357
+ send_data "550 sender is unacceptable\r\n"
358
+ else
359
+ send_data "250 Ok\r\n"
360
+ @state << :mail_from
361
+ end
362
+ end
363
+ end
364
+
365
+ #--
366
+ # Since we require :mail_from to have been seen before we process RCPT TO,
367
+ # we don't need to repeat the tests for TLS and AUTH.
368
+ # Note that we don't remember or do anything else with the recipients.
369
+ # All of that is on the user code.
370
+ # TODO: we should enforce user-definable limits on the total number of
371
+ # recipients per transaction.
372
+ # We might want to make sure that a given recipient is only seen once, but
373
+ # for now we'll let that be the user's problem.
374
+ #
375
+ # User-written code can return a deferrable from receive_recipient.
376
+ #
377
+ def process_rcpt_to rcpt
378
+ unless @state.include?(:mail_from)
379
+ send_data "503 MAIL is required before RCPT\r\n"
380
+ else
381
+ succeeded = proc {
382
+ send_data "250 Ok\r\n"
383
+ @state << :rcpt unless @state.include?(:rcpt)
384
+ }
385
+ failed = proc {
386
+ send_data "550 recipient is unacceptable\r\n"
387
+ }
388
+
389
+ d = receive_recipient rcpt
390
+
391
+ if d.respond_to?(:set_deferred_status)
392
+ d.callback(&succeeded)
393
+ d.errback(&failed)
394
+ else
395
+ (d ? succeeded : failed).call
396
+ end
397
+
398
+ =begin
399
+ unless receive_recipient rcpt
400
+ send_data "550 recipient is unacceptable\r\n"
401
+ else
402
+ send_data "250 Ok\r\n"
403
+ @state << :rcpt unless @state.include?(:rcpt)
404
+ end
405
+ =end
406
+ end
407
+ end
408
+
409
+
410
+ # Send the incoming data to the application one chunk at a time, rather than
411
+ # one line at a time. That lets the application be a little more flexible about
412
+ # storing to disk, etc.
413
+ # Since we clear the chunk array every time we submit it, the caller needs to be
414
+ # aware to do things like dup it if he wants to keep it around across calls.
415
+ #
416
+ # DON'T reset the transaction upon disposition of the incoming message.
417
+ # This means another DATA command can be accepted with the same sender and recipients.
418
+ # If the client wants to reset, he can call RSET.
419
+ # Not sure whether the standard requires a transaction-reset at this point, but it
420
+ # appears not to.
421
+ #
422
+ # User-written code can return a Deferrable as a response from receive_message.
423
+ #
424
+ def process_data_line ln
425
+ if ln == "."
426
+ if @databuffer.length > 0
427
+ receive_data_chunk @databuffer
428
+ @databuffer.clear
429
+ end
430
+
431
+
432
+ succeeded = proc {
433
+ send_data "250 Message accepted\r\n"
434
+ }
435
+ failed = proc {
436
+ send_data "550 Message rejected\r\n"
437
+ }
438
+
439
+ d = receive_message
440
+
441
+ if d.respond_to?(:set_deferred_status)
442
+ d.callback(&succeeded)
443
+ d.errback(&failed)
444
+ else
445
+ (d ? succeeded : failed).call
446
+ end
447
+
448
+ @state.delete :data
449
+ else
450
+ # slice off leading . if any
451
+ ln.slice!(0...1) if ln[0] == 46
452
+ @databuffer << ln
453
+ if @databuffer.length > @@parms[:chunksize]
454
+ receive_data_chunk @databuffer
455
+ @databuffer.clear
456
+ end
457
+ end
458
+ end
459
+
460
+
461
+ #------------------------------------------
462
+ # Everything from here on can be overridden in user code.
463
+
464
+ # The greeting returned in the initial connection message to the client.
465
+ def get_server_greeting
466
+ "EventMachine SMTP Server"
467
+ end
468
+ # The domain name returned in the first line of the response to a
469
+ # successful EHLO or HELO command.
470
+ def get_server_domain
471
+ "Ok EventMachine SMTP Server"
472
+ end
473
+
474
+ # A false response from this user-overridable method will cause a
475
+ # 550 error to be returned to the remote client.
476
+ #
477
+ def receive_ehlo_domain domain
478
+ true
479
+ end
480
+
481
+ # Return true or false to indicate that the authentication is acceptable.
482
+ def receive_plain_auth user, password
483
+ true
484
+ end
485
+
486
+ # Receives the argument of the MAIL FROM command. Return false to
487
+ # indicate to the remote client that the sender is not accepted.
488
+ # This can only be successfully called once per transaction.
489
+ #
490
+ def receive_sender sender
491
+ true
492
+ end
493
+
494
+ # Receives the argument of a RCPT TO command. Can be given multiple
495
+ # times per transaction. Return false to reject the recipient.
496
+ #
497
+ def receive_recipient rcpt
498
+ true
499
+ end
500
+
501
+ # Sent when the remote peer issues the RSET command.
502
+ # Since RSET is not allowed to fail (according to the protocol),
503
+ # we ignore any return value from user overrides of this method.
504
+ #
505
+ def receive_reset
506
+ end
507
+
508
+ # Sent when the remote peer has ended the connection.
509
+ #
510
+ def connection_ended
511
+ end
512
+
513
+ # Called when the remote peer sends the DATA command.
514
+ # Returning false will cause us to send a 550 error to the peer.
515
+ # This can be useful for dealing with problems that arise from processing
516
+ # the whole set of sender and recipients.
517
+ #
518
+ def receive_data_command
519
+ true
520
+ end
521
+
522
+ # Sent when data from the remote peer is available. The size can be controlled
523
+ # by setting the :chunksize parameter. This call can be made multiple times.
524
+ # The goal is to strike a balance between sending the data to the application one
525
+ # line at a time, and holding all of a very large message in memory.
526
+ #
527
+ def receive_data_chunk data
528
+ @smtps_msg_size ||= 0
529
+ @smtps_msg_size += data.join.length
530
+ STDERR.write "<#{@smtps_msg_size}>"
531
+ end
532
+
533
+ # Sent after a message has been completely received. User code
534
+ # must return true or false to indicate whether the message has
535
+ # been accepted for delivery.
536
+ def receive_message
537
+ @@parms[:verbose] and $>.puts "Received complete message"
538
+ true
539
+ end
540
+
541
+ # This is called when the protocol state is reset. It happens
542
+ # when the remote client calls EHLO/HELO or RSET.
543
+ def receive_transaction
544
+ end
545
+ end
546
+ end
547
+ end