separation port and encryption method

[abcnorio]

using Zimbra 8.7RC2 on ubuntu server 16.04 within a VM (virtualbox) it is not possible to separate port and encryption method using bsmtp, e.g. a provider wants port 25 along with STARTTLS (instead of using port 587). Filling in port 25 is not stored and replaced by 587 automatically.

thanks for fixing this, best leo

[adriangibanelbtactic]

1) How would you recommend on implementing it? An on/off switch with: Set me recommended ports automatically, perhaps?

2) In the meanwhile as a workaround you can save your settings (even if they are wrong) and later on modify them thanks to zmprov.

Check current settings:

zmprov getAccount account@domain.com zimbraZimletUserProperties | grep 'com_btactic_bsmtp'

Change them:

zmprov modifyAccount account@domain.com -zimbraZimletUserProperties com_btactic_bsmtp:port:587
zmprov modifyAccount account@domain.com +zimbraZimletUserProperties com_btactic_bsmtp:port:25

Then logout and login back so that the new settings are taken into account and I think it should work.

[abcnorio]

Am 07.07.2016 um 11:47 schrieb Adrian Gibanel Lopez:

thanks, changing the port does work. But using it to send mails does nothing.

I tried to send out without bsmtp and watched /var/log/mail.log and it showed a clear error message, because the auth to my provider (relay) was not ok (using a local address with .xx domain). This was to be expected.

Using bsmtp did not show anything in the log although the mail was properly stored in the "Sent" folder that was chosen while configuring bsmtp.

btw - via webapp bsmtp still shows "port 587" although the commandline shows a proper port 25 (I even rebooted just to be sure).

Any suggestions? Any other place where I can observe whether bsmtp works? At least postfix does not seem to be involved.

thanks and best leo

1) How would you recommend on implementing it? An on/off switch with: Set me recommended ports automatically, perhaps?

2) In the meanwhile as a workaround you can save your settings (even if they are wrong) and later on modify them thanks to zmprov.

Check current settings:

|zmprov getAccount account@domain.com zimbraZimletUserProperties | grep 'com_btactic_bsmtp' |

Change them:

|zmprov modifyAccount account@domain.com -zimbraZimletUserProperties com_btactic_bsmtp:port:587 zmprov modifyAccount account@domain.com +zimbraZimletUserProperties com_btactic_bsmtp:port:25 |

Then logout and login back so that the new settings are taken into account and I think it should work.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/btactic/bsmtp/issues/4#issuecomment-231033136, or mute the thread https://github.com/notifications/unsubscribe/ATV1ogRH1ZK6F0gJEPYEhx2ioqoy1jJ-ks5qTMsygaJpZM4JEP8j.

[adriangibanelbtactic]

thanks, changing the port does work. But using it to send mails does nothing.

Ok.

I tried to send out without bsmtp and watched /var/log/mail.log and it showed a clear error message, because the auth to my provider (relay) was not ok (using a local address with .xx domain). This was to be expected.

I see.

Using bsmtp did not show anything in the log although the mail was properly stored in the "Sent" folder that was chosen while configuring bsmtp.

The zimlet does not generate any log. Feel free to fork it, implement it thanks to a conditional settings, and send us a pull request.

You can also try to login into another system that you control yourself so that you can see what happens in the server side.

btw - via webapp bsmtp still shows "port 587" although the commandline shows a proper port 25 (I even rebooted just to be sure).

I think that given our current javascript implementation it's what's to be expected. Pull requests welcome.

Any suggestions? Any other place where I can observe whether bsmtp works? At least postfix does not seem to be involved.

Well, you can try to hack: https://github.com/btactic/bsmtp/blob/master/com_btactic_bsmtp/smtp.jsp so that https://github.com/btactic/bsmtp/blob/master/com_btactic_bsmtp/smtp.jsp#L97-L99 logs the exception string somewhere.