nodemailer/wildduck

Discord: https://wildduck.email/discord

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

Mohammed M R Zourob

@dash7ou

I can not understand what accully happened there when I try other instance its working fine, but now I am trying to connect to it use smtp client but its not working.. @andris9

Is there any file I need to check it to make sure connection not blocked in config file ?

@andris9

set to true to start in TLS mode if using port 465
this probably does not work as TLS support with 465 in ZoneMTA is a bit buggy
secure=false

@andris9 this need to be true ?

feeder.tom file in zone-mta folder

Andris Reinman

@andris9

by default nothing is blocked. wildduck installer is tested on digitalocean servers. for testing you can also set up a server in digitalocean, run the installer, see if evrything works and then compare it with your actual server if there are any differences. eg. sometimes security features like AppArmor block things in unexpected ways

default SMTP port is 587

you can test it like this:

openssl s_client -starttls smtp -crlf -connect 1.2.3.4:587

Mohammed M R Zourob

@dash7ou

I have test that on instance Ip direct with 587 before working fine but when I use domain name + port 465 for smtp its not working @andris9

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.

Where communities thrive

People

Repo info

Activity