Commit 051a895
committed
exmdb: remodel exmdb_server::deliver_message's way of vivified mails
The deliver_message handler would only add message_id into the notify
set if the DELIVERY_DO_RULES flag was given. However, when
lda_twostep_processor is used, the DO_RULES flag for server-side rule
processing is not set, since the client is supposed to take care of
everything, new mail notification included.
Now, in a twist, clients are not so much listening for events of type
fnevNewMail, but rather fnevObjectCreated on content tables.
When TWOSTEP was enabled, exmdb_server::deliver_message would not
emit fnevObjectCreated, but lib/ruleproc.cpp would immediately call
exmdb_server::notify_new_mail, which did emit fnevObjectCreated. In
9152bab, lib/ruleproc.cpp was changed from notify_new_mail to
transport_new_mail, so deliver_message should have received a change
to send fnevObjectCreated, but that did not happen.
Fixes: gromox-2.46-89-g9152babd7
References: GXH-154, GXL-616, DESK-3712, DESK-3715, DESK-37161 parent 5a0315f commit 051a895
1 file changed
+6
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
70 | 70 | | |
71 | 71 | | |
72 | 72 | | |
| 73 | + | |
| 74 | + | |
73 | 75 | | |
74 | 76 | | |
75 | 77 | | |
| |||
3563 | 3565 | | |
3564 | 3566 | | |
3565 | 3567 | | |
3566 | | - | |
3567 | | - | |
| 3568 | + | |
| 3569 | + | |
3568 | 3570 | | |
3569 | 3571 | | |
3570 | 3572 | | |
| |||
3777 | 3779 | | |
3778 | 3780 | | |
3779 | 3781 | | |
| 3782 | + | |
| 3783 | + | |
3780 | 3784 | | |
3781 | 3785 | | |
3782 | 3786 | | |
| |||
0 commit comments