nodemailer/wildduck

Discord: https://wildduck.email/discord

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.

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.

Where communities thrive

People

Repo info

Activity