Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Sep 25 21:24
    vaelu commented #426
  • Sep 25 21:21
    vaelu commented #426
  • Sep 25 21:21
    louis-lau commented #426
  • Sep 25 21:16
    louis-lau commented #426
  • Sep 25 21:16
    louis-lau commented #426
  • Sep 25 21:14
    louis-lau commented #426
  • Sep 25 21:05
    vaelu commented #426
  • Sep 25 18:54
    louis-lau commented #426
  • Sep 25 18:54
    louis-lau commented #426
  • Sep 25 17:09
    vaelu opened #426
  • Sep 23 13:12

    andris9 on master

    Fixed a typo Merge pull request #14 from Taa… (compare)

  • Sep 23 13:12
    andris9 closed #14
  • Sep 23 13:09
    TaaviE opened #14
  • Sep 20 12:49

    andris9 on zms-49

    started with import stream pars… (compare)

  • Sep 20 12:35

    andris9 on zms-49

    started with export/import feat… (compare)

  • Sep 20 08:28

    andris9 on v1.35.1

    (compare)

  • Sep 20 08:28

    andris9 on master

    v1.35.1 (compare)

  • Sep 20 08:26

    andris9 on v1.37.5

    (compare)

  • Sep 20 08:26

    andris9 on master

    v1.37.5 (compare)

  • Sep 20 07:03

    andris9 on master

    v1.35.0 (compare)

Andris Reinman
@andris9
this is because by default wildduck users port 587, not 465 for SMTP MSA server
if you you want to use 465, then change the port number and also set secure=true
Mohammed M R Zourob
@dash7ou
treafik redirect connection from 465 to 587 @andris9
Louis
@louis:laureys.me
[m]
We already talked about this dash7ou ;)
Traefik seems to be working fine, you'll need to figure out yourself what's going wrong with your networking.
Mohammed M R Zourob
@dash7ou
Thanks @louis:laureys.me , I am working on this
Mohammed M R Zourob
@dash7ou

@louis:laureys.me I noticed something I think the issue with traefik because HTTPS connection work but when I try
openssl s_client -crlf -starttls smtp -connect cudy.email:465 ==> failed

openssl s_client -crlf -starttls pop3 -connect cudy.email:995 ==> failed
openssl s_client -crlf -starttls imap -connect cudy.email:993 => give me CONNECTED(00000003)

@andris9 What do u think ?

Andris Reinman
@andris9
when connecting to TLS ports, do not use the STARTTLS syntax
# tls ports (465, 993, 995)
$ openssl s_client -crlf -connect <host>:<port>
# starttls ports (587, 110)
openssl s_client -crlf -starttls <proto> -connect <host>:<port>
Louis
@louis:laureys.me
[m]
I still think curl is easier to use hahaha.
Mohammed M R Zourob
@dash7ou
@louis:laureys.me 995, 993 working fine still 465 not working :(
@andris9
Louis
@louis:laureys.me
[m]
Have you asked amazon yet? :)
Mohammed M R Zourob
@dash7ou
I have checked vpc out & income bound and security group every thing fine
@louis:laureys.me
Louis
@louis:laureys.me
[m]
Sure, but have you actually asked them? haha
They can block things without it showing in your dashboard
Mohammed M R Zourob
@dash7ou
@louis-lau Is there is a way I can disable the signup page in webmail?
Louis
@louis:laureys.me
[m]
Sure. Take a look at the webmail config.
Mohammed M R Zourob
@dash7ou
@louis:laureys.me thanks
appsynergyinc
@appsynergyinc
When trying to set alias of noc@domain.com I get an error of being reserved? Also after using install script, how to access the API with postman. Can I set the API key after the install script?
Louis
@louis:laureys.me
[m]
Because wildduck webmail registration is public, it has a number of reserved addresses. I think you can disable them in the config. Or you can create it directly through the wildduck API.
I think the API listens on port 8080 on localhost by default.
appsynergyinc
@appsynergyinc
Ah. Thanks
Louis
@louis:laureys.me
[m]
And yeah for the API key just alter the wildduck config
appsynergyinc
@appsynergyinc
and then just restart the service right?
Louis
@louis:laureys.me
[m]
Yup
appsynergyinc
@appsynergyinc
What is the best way to remotely access the API without disrupting the application from accessing?
Just got our /24 operational. Long day :)
Louis
@louis:laureys.me
[m]
If you only need postman access, I'd probably just create an ssh tunnel to access it
appsynergyinc
@appsynergyinc
Thanks.
Louis
@louis:laureys.me
[m]
If you need permanent access from another server you can set the API key and setup TLS for the API.
appsynergyinc
@appsynergyinc
Might just do that.
Louis
@louis:laureys.me
[m]
👍
Be careful with it. If not properly secured it gives access to all users and their messages
appsynergyinc
@appsynergyinc
I will keep that in mind. I will check to make sure that isn't the case.
I'm coming from many years of using poste io... Its horrible. Its time to make the switch.
appsynergyinc
@appsynergyinc
I basically just needed to get mail on my domain running in a pinch as I was expecting emails. I will customize this like crazy. 5 minutes and I was already receiving mail.
Andris Reinman
@andris9
@channel product news - some config options were deprecated and moved to central config system. Eg. you do not have to set maxStorage value in every WildDuck server anymore to define default allowed disk quota. This value (and some other values) can now be edited centrally either via API endpoint or via a simple built-in config editor. See the details from the documentation
Louis
@louis:laureys.me
[m]
With a config UI! How nice!
Could a migration be run for the toml values? I can see this causing confusion.
Andris Reinman
@andris9
yeah, this was needed because we had a lot of issues where API reported some user to have sufficient quota but in reality emails were rejected due to quota being full. This happened when the user did not have a custom quota size set and API server had different default maxStorage set than the MX server
toml values are preferred if set
Louis
@louis:laureys.me
[m]
Ahh, that's a good solution
Andris Reinman
@andris9
you have to delete the values from toml files to migrate to the new system
user specific value > toml value > central value
appsynergyinc
@appsynergyinc
Any security related changes?
Louis
@louis:laureys.me
[m]
👍
Yeah in this case having a global config instead of an instance config makes more sense.
Just realized I still need to fix the wildduck-dockerized config... Will get to that soon.
Andris Reinman
@andris9
nothing security specific, expect a bugfix for API HTTPS keys where ca option was ignored, so if you used cert, key and ca for API HTTPS then clients rejected HTTPS connections as the certificate chain was not included in the server response. If you used certificate bundles instead of separate ca value, then nothing changed