@tomav i already made a pull request for kopano support (#335) of this project. In order to generalize this issue i would suggest instead of only making a config step for kopano we could make this one for the virtual_transport in general. This could be useful for people that need to be more flexible regarding the configuration of the postfix lmtp client and is also much cleaner (compared to my first implementation)
to make this work we would need two more environment variables:
And also for my particular needs it would be easy without double checks (see implementation of #335, check for SMTP_ONLY = 1) to integrate this into my kopano env, e.g. virtual_transport = lmtp:address-to-kopano-instance:2003.
To get an idea for this feature maybe have a look at (for a quick overview):
http://wiki.linuxquestions.org/wiki/Postfix_virtual_transport
@tomav i already made a pull request for kopano support (#335) of this project. In order to generalize this issue i would suggest instead of only making a config step for kopano we could make this one for the virtual_transport in general. This could be useful for people that need to be more flexible regarding the configuration of the postfix lmtp client and is also much cleaner (compared to my first implementation)
to make this work we would need two more environment variables:
And also for my particular needs it would be easy without double checks (see implementation of #335, check for SMTP_ONLY = 1) to integrate this into my kopano env, e.g. virtual_transport = lmtp:address-to-kopano-instance:2003.
To get an idea for this feature maybe have a look at (for a quick overview):
http://wiki.linuxquestions.org/wiki/Postfix_virtual_transport