Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 09:29
    randrusiak commented #381
  • May 24 15:29
    ukwuezeobinna commented #399
  • May 24 15:29
    louis-lau commented #399
  • May 24 15:28
    ukwuezeobinna commented #399
  • May 24 14:13
    louis-lau commented #399
  • May 24 14:09

    andris9 on master

    Force rehashing of DES hashes (compare)

  • May 24 14:04

    andris9 on feature-des-hash

    (compare)

  • May 24 14:04
    andris9 closed #400
  • May 24 14:04

    andris9 on master

    Added support for DES password … Merge pull request #400 from no… (compare)

  • May 24 14:04
    andris9 opened #400
  • May 24 14:01

    andris9 on feature-des-hash

    Added support for DES password … (compare)

  • May 24 13:15

    andris9 on master

    Webauthn registration now only … Merge pull request #398 from ji… (compare)

  • May 24 13:15
    andris9 closed #398
  • May 24 12:05
    ukwuezeobinna commented #399
  • May 24 12:04
    ukwuezeobinna commented #399
  • May 24 11:52
    louis-lau commented #399
  • May 24 11:47
    ukwuezeobinna commented #399
  • May 24 11:47
    ukwuezeobinna commented #399
  • May 24 11:39
    louis-lau commented #399
  • May 24 11:38
    ukwuezeobinna commented #399
Louis
@louis:laureys.me
[m]
There's no point in testing two different things haha
Like I said, something is blocking access to port 465
Mohammed M R Zourob
@dash7ou
@louis:laureys.me let me explain to u the direct port in instance ip is 587 and working fine, but when I try to connect to smtp on domain name use traefik its not working because container work on 587 port but treafik config to connect to this container is 465
Louis
@louis:laureys.me
[m]
That's not why
Traefik listens on port 465, and forwards the traffic to the container on port 587
Mohammed M R Zourob
@dash7ou
Yup I know that
Louis
@louis:laureys.me
[m]
Either Traefik isn't running
Or something is blocking access to port 465
Mohammed M R Zourob
@dash7ou
no when I try to open wildduck webmail its working
port 443 working fine
Louis
@louis:laureys.me
[m]
Then traefik is running
Mohammed M R Zourob
@dash7ou
ya I know that why I can not know what exactly the problem
Louis
@louis:laureys.me
[m]
Maybe something else was already listening on port 465?
So docker couldn't let Traefik listen on it
You would have gotten a warning from docker
Mohammed M R Zourob
@dash7ou
Nope because if that right traefik container will not working and told me this port already used
Louis
@louis:laureys.me
[m]
Yep
So, something must be blocking port 465
Only answer I have for ya ;)
Mohammed M R Zourob
@dash7ou
Nope all containers working fine, I told u when I try ip instance direct emails send and smtp connect success
Louis
@louis:laureys.me
[m]
I'm talking about networking though. Not containers.
Could be a firewall for example
Mohammed M R Zourob
@dash7ou
I am not sure maybe the problem with cloudflare because I can not see any thing in logs
Louis
@louis:laureys.me
[m]
Because you're never connecting
Mohammed M R Zourob
@dash7ou
No I have disabled ufw because I am using amazon network
Louis
@louis:laureys.me
[m]
Are you sure amazon doesn't block port 465?
Mohammed M R Zourob
@dash7ou
hm let me check that again to make sure no problem with 465 port
wait there is something strange that happened, when I run curl -v smtps://my.domain from same instance its give me success response @louis:laureys.me
Louis
@louis:laureys.me
[m]
You mean the same instance that's hosting containers?
Mohammed M R Zourob
@dash7ou
yup but not used smtp://localhost, using domain name smtps://my.domain
Louis
@louis:laureys.me
[m]
Linux should route that internally if the hostname is set correctly. So that probably means amazon is indeed blocking port 465
Mohammed M R Zourob
@dash7ou
I do not think so there is anything on internet says aws block port 465
Andris Reinman
@andris9
you can also use openssl to test tls ports
$ openssl s_client -crlf -connect smtp.gmail.com:465
...
220 smtp.gmail.com ESMTP h19sm1432911lfu.138 - gsmtp
any other response - you are firewalled and can't use these ports
Mohammed M R Zourob
@dash7ou
@andris9
139933307688256:error:0200206F:system library:connect:Connection refused:../crypto/bio/b_sock2.c:110:
139933307688256:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111:
connect:errno=111
Louis
@louis:laureys.me
[m]
Same error unsurprisingly haha
Mohammed M R Zourob
@dash7ou
@louis:laureys.me Is there any config i need to check it in config folder ?
Louis
@louis:laureys.me
[m]
Your wildduck config is correct.
I can keep repeating it, but something is blocking access to port 465 ;)
Mohammed M R Zourob
@dash7ou
ya when I use webmail send and receive emails working fine
Louis
@louis:laureys.me
[m]
Well yeah, that doesn't use port 465
Mohammed M R Zourob
@dash7ou
yup I know that its using local network
Mohammed M R Zourob
@dash7ou
@louis:laureys.me I discovered what exactly the issue, its blocked connect to smtp from local host when I try to connect to smtp from other instance its working fine.
@louis:laureys.me "hello" is a reserved username this issue show up when I try to create hello@x.x
Mohammed M R Zourob
@dash7ou
@andris9 If u have any suggestions pls told me
Andris Reinman
@andris9
There is no limitations on usernames if you are creating accounts directly via the API. Username limitation is only when using the public signup form to prevent malicious users to register addresses like postmaster@domain and then taking over the domain name etc.
Mohammed M R Zourob
@dash7ou
Ya I have created it use api and its working fine thanks @andris9
dkbr-lab
@dkbr-lab
You can also register usernames containing @ via the API, which for my usage purposes is helpful. It can cause a few other quirks elsewhere, however, as username validation errors can occur.
Mohammed M R Zourob
@dash7ou

@andris9 is this config in pools.toml in zone-mat folder config effect my connection to smtp from any where

local IP addresses that can be used for outbound tcp connections
Server process must be able to locally bind to these addresses

[[default]]
address="0.0.0.0"
name="x.email"

Andris Reinman
@andris9
"0.0.0.0" means that default IP is used for routing (you might have multiple IP's set up). "x.email" is used with "EHLO x.email" command when establishing connections to MX servers