https://wiki.zimbra.com/api.php?action=feedcontributions&user=Yutaka&feedformat=atomZimbra :: Tech Center - User contributions [en]2024-03-28T16:09:38ZUser contributionsMediaWiki 1.39.0https://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=37662Yutaka-Notes about Extensible Classes In ZimbraStore2012-02-20T04:09:38Z<p>Yutaka: </p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZCS7's ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By extending this with your own class, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By extending this with your own class, you can modify a message when the message is stored to the disk.<br />
This is basically to modify MimeMessage and execute saveChange. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==<br />
<br />
==com.zimbra.cs.mailbox.MailboxListener==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36517Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-25T12:35:28Z<p>Yutaka: /* com.zimbra.cs.mime.MimeVisitor[mutator] */</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZCS7's ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By extending this with your own class, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By extending this with your own class, you can modify a message when the message is stored to the disk.<br />
This is basically to modify MimeMessage and execute saveChange. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36509Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:30:56Z<p>Yutaka: </p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZCS7's ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By extending this with your own class, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By extending this with your own class, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36508Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:18:21Z<p>Yutaka: /* com.zimbra.cs.mime.MimeVisitor[mutator] */</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By extending this with your own class, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By extending this with your own class, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36507Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:17:30Z<p>Yutaka: /* com.zimbra.cs.mime.MimeVisitor[converter] */</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By extending this with your own class, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36506Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:14:36Z<p>Yutaka: /* com.zimbra.cs.account.AttributeCallback */</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By extending this with your own class, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register your own class to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36505Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:13:34Z<p>Yutaka: /* com.zimbra.cs.service.AuthProvider */</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By extending this with your own class, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register your own class to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes&diff=36504Yutaka-Notes2011-08-24T19:10:26Z<p>Yutaka: /* Tips for customizing ZCS7.1 */</p>
<hr />
<div>==Tips for customizing ZCS7.1 ==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore<br />
<br />
==Tips for ZimbraDesktop2.0==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes-ZD2.0</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-forCustmizingZCS7&diff=36503Yutaka-Notes-forCustmizingZCS72011-08-24T19:08:10Z<p>Yutaka: moved Yutaka-Notes-forCustmizingZCS7 to Yutaka-Notes about Extensible Classes In ZimbraStore</p>
<hr />
<div>#REDIRECT [[Yutaka-Notes about Extensible Classes In ZimbraStore]]</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36502Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T19:08:10Z<p>Yutaka: moved Yutaka-Notes-forCustmizingZCS7 to Yutaka-Notes about Extensible Classes In ZimbraStore</p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36501Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T14:09:30Z<p>Yutaka: </p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By extending this with your own class, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register your own class to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36500Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T13:51:13Z<p>Yutaka: </p>
<hr />
<div>''Here is the list of classes which you can extend to enhance zimbra standard functionality of ZimbraStore with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36499Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T13:44:37Z<p>Yutaka: </p>
<hr />
<div><br />
''Here is the list of classes which you can extend to enhance zimbra standard functionality with your own classes.''<br />
<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36498Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-24T13:42:03Z<p>Yutaka: </p>
<hr />
<div><br />
Here are the list of classes which you can extend to enhance zimbra standard fnctionality.<br />
<br />
==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36485Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-21T13:35:49Z<p>Yutaka: </p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mailbox.ScheduledTask==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36447Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T02:30:28Z<p>Yutaka: </p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[converter]==<br />
By this, you can modify the message on the fly when a message is fetched from the store to be sent back to client or prepared for forwarding and indexing.<br />
These modification is not sotred on disk.<br />
<br />
Sample is here;<br />
com.zimbra.cs.mime.TnefConverter<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor[mutator]==<br />
By this, you can modify the message when a message is stored to the dislk.<br />
This is basically to create copy of original MimeMessage and replace the original with it. So it could have some impact to DiskI/O.<br />
<br />
Sample is here;<br />
No sample.<br />
<br />
[Note] You have to register this to com.zimbra.cs.mime.MimeVisitor.</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36446Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T02:15:21Z<p>Yutaka: </p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.<br />
<br />
==com.zimbra.cs.mime.MimeVisitor==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36445Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T02:02:06Z<p>Yutaka: </p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to com.zimbra.cs.security.sasl.Authenticator<br />
<br />
==com.zimbra.cs.account.AttributeCallback==<br />
By this, you can implement custom function which is called right before/after a certain LDAP field is modified.<br />
<br />
Sample is here;<br />
com.zimbra.cs.account.callback.AccountStatus<br />
<br />
[Note] You have to register this to zimbra-attrs.xml and rebuild ZimbraServer project as far as I remember.</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36444Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T01:47:13Z<p>Yutaka: </p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider<br />
<br />
==com.zimbra.cs.security.sasl.Authenticator==<br />
By this, you can add SASL mechanism for IMAP/POP. But to use the custome SASL mechanism, you also needs to customize Zimbra Proxy(Nginx/nginxlookup), which requires you to modify core code.<br />
<br />
Sample is here;<br />
com.zimbra.cs.security.sasl.PlainAuthenticator<br />
<br />
[Note] You have to register this to =com.zimbra.cs.security.sasl.Authenticator</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36443Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T01:01:37Z<p>Yutaka: /* com.zimbra.cs.lmtpserver.LmtpCallback */</p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]You have to register this to com.zimbra.cs.lmtpserver.ZimbraLmtpBackend<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36442Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T01:00:07Z<p>Yutaka: /* com.zimbra.cs.lmtpserver.LmtpCallback */</p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
Sample is here;com.zimbra.cs.mailbox.QuotaWarning<br />
<br />
[Note]<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36441Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T00:58:35Z<p>Yutaka: /* LmtpCallback */</p>
<hr />
<div>==com.zimbra.cs.lmtpserver.LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36440Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T00:57:21Z<p>Yutaka: /* AuthProvider */</p>
<hr />
<div>==LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
<br />
==com.zimbra.cs.service.AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.<br />
<br />
Sample is here;<br />
com.zimbra.cs.service.ZimbraAuthProvider<br />
<br />
[Note] You have to register this to com.zimbra.cs.service.AuthProvider</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36439Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T00:39:55Z<p>Yutaka: /* AuthProvider */</p>
<hr />
<div>==LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
<br />
==AuthProvider==<br />
By this, you can implement to genearate custom auth token and to validate that.</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36438Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-12T00:01:54Z<p>Yutaka: </p>
<hr />
<div>==LmtpCallback==<br />
By this, you can register your custom function to be called when a messege is receive with lmtp.<br />
<br />
<br />
==AuthProvider==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes&diff=36437Yutaka-Notes2011-08-11T23:51:07Z<p>Yutaka: </p>
<hr />
<div>==Tips for customizing ZCS7.1 ==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes-forCustmizingZCS7<br />
<br />
==Tips for ZimbraDesktop2.0==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes-ZD2.0</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes&diff=36436Yutaka-Notes2011-08-11T23:48:00Z<p>Yutaka: moved Yutaka-Notes to Yutaka-Notes-forCustmizingZCS7</p>
<hr />
<div>#REDIRECT [[Yutaka-Notes-forCustmizingZCS7]]</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36435Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-11T23:48:00Z<p>Yutaka: moved Yutaka-Notes to Yutaka-Notes-forCustmizingZCS7</p>
<hr />
<div>==Tips for customizing ZCS7.1 ==<br />
<br />
<br />
<br />
==Tips for ZimbraDesktop2.0==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes-ZD2.0</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36434Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-11T23:43:37Z<p>Yutaka: </p>
<hr />
<div>==Tips for customizing ZCS7.1 ==<br />
<br />
<br />
<br />
==Tips for ZimbraDesktop2.0==<br />
<br />
http://wiki.zimbra.com/wiki/Yutaka-Notes-ZD2.0</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36433Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-11T23:42:01Z<p>Yutaka: </p>
<hr />
<div>==Tips for ZimbraDesktop2.0==<br />
<br />
#REDIRECT [[Yutaka-Notes-ZD2.0]]</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes_about_Extensible_Classes_In_ZimbraStore&diff=36429Yutaka-Notes about Extensible Classes In ZimbraStore2011-08-11T13:30:55Z<p>Yutaka: moved Yutaka-Notes to Yutaka-Notes-ZD2.0</p>
<hr />
<div>#REDIRECT [[Yutaka-Notes-ZD2.0]]</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=36428Yutaka-Notes-ZD2.02011-08-11T13:30:55Z<p>Yutaka: moved Yutaka-Notes to Yutaka-Notes-ZD2.0</p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your account by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
8|acct|local@host.local|ffffffff-ffff-ffff-ffff-ffffffffffff|0<br />
13|acct|((your mail address))|69ae21ef-21c4-4782-b0d9-0999bbf71b57|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where entry_id=13 AND name="zimbraPrefMailDefaultCharset";<br />
entry_id|name|value<br />
13|zimbraPrefMailDefaultCharset|iso-2022-jp<br />
</pre><br />
<br />
==Network proxy setting in ZimbraDesktop2.0==<br />
<br />
This tip's modifiaction step is pretty much same as previous one.<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your conf entry by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where name="zimbraHttpProxyURL";<br />
1|zimbraHttpProxyURL|http://(userid):(password)@(proxy host name):(proxy port number)<br />
</pre><br />
<br />
Detail about the data format of zimbraHttpProxyURL fields:<br />
http://wiki.zimbra.com/wiki/ZCS_4.5_HTTP_Proxy_Guide</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21209Yutaka-Notes-ZD2.02010-10-11T22:15:46Z<p>Yutaka: /* Network proxy setting in ZimbraDesktop2.0 */</p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your account by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
8|acct|local@host.local|ffffffff-ffff-ffff-ffff-ffffffffffff|0<br />
13|acct|((your mail address))|69ae21ef-21c4-4782-b0d9-0999bbf71b57|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where entry_id=13 AND name="zimbraPrefMailDefaultCharset";<br />
entry_id|name|value<br />
13|zimbraPrefMailDefaultCharset|iso-2022-jp<br />
</pre><br />
<br />
==Network proxy setting in ZimbraDesktop2.0==<br />
<br />
This tip's modifiaction step is pretty much same as previous one.<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your conf entry by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where name="zimbraHttpProxyURL";<br />
1|zimbraHttpProxyURL|http://(userid):(password)@(proxy host name):(proxy port number)<br />
</pre><br />
<br />
Detail about the data format of zimbraHttpProxyURL fields:<br />
http://wiki.zimbra.com/wiki/ZCS_4.5_HTTP_Proxy_Guide</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21208Yutaka-Notes-ZD2.02010-10-11T22:13:05Z<p>Yutaka: /* Network proxy setting in ZimbraDesktop2.0 */</p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your account by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
8|acct|local@host.local|ffffffff-ffff-ffff-ffff-ffffffffffff|0<br />
13|acct|((your mail address))|69ae21ef-21c4-4782-b0d9-0999bbf71b57|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where entry_id=13 AND name="zimbraPrefMailDefaultCharset";<br />
entry_id|name|value<br />
13|zimbraPrefMailDefaultCharset|iso-2022-jp<br />
</pre><br />
<br />
==Network proxy setting in ZimbraDesktop2.0==<br />
<br />
This tip's modifiaction step is pretty much same as previous one.<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your conf entry by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where name="zimbraHttpProxyURL";<br />
1|zimbraHttpProxyURL|http://(userid):(password)@(proxy host name):(proxy port number)<br />
</pre></div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21188Yutaka-Notes-ZD2.02010-10-07T21:54:36Z<p>Yutaka: /* To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0 */</p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your account by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
8|acct|local@host.local|ffffffff-ffff-ffff-ffff-ffffffffffff|0<br />
13|acct|((your mail address))|69ae21ef-21c4-4782-b0d9-0999bbf71b57|0<br />
</pre><br />
<br />
Then insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where entry_id=13 AND name="zimbraPrefMailDefaultCharset";<br />
entry_id|name|value<br />
13|zimbraPrefMailDefaultCharset|iso-2022-jp<br />
</pre><br />
<br />
==Network proxy setting in ZimbraDesktop2.0==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21187Yutaka-Notes-ZD2.02010-10-07T21:52:55Z<p>Yutaka: /* To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0 */</p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
When you have sqlite3.exe in C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe, <br />
you can start cli with <br />
<br />
<pre><br />
>"C:\Program Files\Zimbra\Zimbra Desktop\win32\sqlite3.exe" "C:\Documents and Settings\((user name))\Local Settings\Application Data\Zimbra\Zimbra Desktop\sqlite\zimbra.db"<br />
</pre><br />
<br />
Then check the entry id for your account by<br />
<br />
<pre><br />
sqlite> select * from directory;<br />
entry_id|entry_type|entry_name|zimbra_id|modified<br />
1|conf|config||0<br />
2|cos|default|179297db-04de-44e3-a5cd-e347baf688ea|0<br />
8|acct|local@host.local|ffffffff-ffff-ffff-ffff-ffffffffffff|0<br />
13|acct|((your mail address))|69ae21ef-21c4-4782-b0d9-0999bbf71b57|0<br />
</pre><br />
<br />
Then you insert the data with the entry id;<br />
<br />
<pre><br />
sqlite> select * from directory_attrs where entry_id=13 AND name="zimbraPrefMailDefaultCharset";<br />
entry_id|name|value<br />
13|zimbraPrefMailDefaultCharset|iso-2022-jp<br />
</pre><br />
<br />
==Network proxy setting in ZimbraDesktop2.0==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21183Yutaka-Notes-ZD2.02010-10-05T19:11:11Z<p>Yutaka: </p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop2.0==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
<br />
==To Change zimbraPrefMailDefaultCharset in ZimbraDesktop2.0==<br />
<br />
<br />
<br />
==Network proxy setting in ZimbraDesktop2.0==</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21182Yutaka-Notes-ZD2.02010-10-05T19:04:44Z<p>Yutaka: </p>
<hr />
<div>==To Use Extended ISO-2022-JP in ZimbraDesktop==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP</div>Yutakahttps://wiki.zimbra.com/index.php?title=Yutaka-Notes-ZD2.0&diff=21181Yutaka-Notes-ZD2.02010-10-05T19:04:12Z<p>Yutaka: Created page with '==To Use Extended ISO-2022-JP== Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like …'</p>
<hr />
<div>==To Use Extended ISO-2022-JP==<br />
<br />
Modify JVM parameter in zdesktop.conf of C:\Documents and Settings\(user)\Local Settings\Application Data\Zimbra\Zimbra Desktop\conf folder like below:<br />
<br />
<pre><br />
java.arg.14=-Dzimbra.config=${DATA_ROOT}\conf\localconfig.xml<br />
java.arg.15=-Dzimbra.home=${DATA_ROOT}<br />
java.arg.16=-Djava.io.tmpdir=${DATA_ROOT}\data\tmp\java<br />
java.arg.17=-Djava.net.useSystemProxies=true<br />
java.arg.18=-Dsun.net.inetaddr.ttl=10<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP<br />
<br />
#********************************************************************<br />
# Application Properties<br />
#********************************************************************<br />
app.arg.1=${DATA_ROOT}\jetty\etc\jetty.xml<br />
</pre><br />
<br />
<br />
You specify x-windows-iso2022jp as ISO-2022-JP by the line,<br />
java.arg.19=-Dsun.nio.cs.map=x-windows-iso2022jp/ISO-2022-JP</div>Yutaka