Problem sending email

yes and also the hello of your server…the IP has no problem only DNS badly recorded

I will still look.
I only changed the IPs at Gandi and it had been working like this for over a year.
Thank you
I will check the DNS

Salut Frederic,

I just added a PTR record for the myhelo:

image

I copied your DKIM and ajusted the record:


Try the test again to see if it’s working.

Michel-André

Here is the result

https://www.mail-tester.com/test-t6swbg78p

Salut Stéphane,

What do you think of the DKIM that I copied before and the result"

Peut-être le 12 heures d’attente ?

Michel-André

DNS are not immediate, you indeed need to wait, moreover you can do only 3 tests/24 hours with mail-tester.com.

Salut Stéphane,

I added a A record for myhelo.
image

Is that the correct way ?

Michel-André

not sure :

read this email_protection_resources [NethServer Wiki]

this is what I have on my custom helo

[root@prometheus ~]# config getprop postfix HeloHost
prometheus.de-labrusse.fr

it is the FQDN of my server, it is a valid dns entry in my dns provider

Salut Stéphane,

I have a CNAME for mail:
image

If I try to enter a MX record, I receive:
image

Should I delete the CNAME and replace it with a MX record ?

Michel-André

I find it , may be help,but on the old config I only replace the IPs
It’s a crazy story

https://marketplace.whmcs.com/product/3210-gandinet-registrar

DNS is the only way to distinct a spammer and a honest server email.

BUT BUT you can be sure spammers are better than us to record their dns :smiley:

don’t shoot i am kidding :stuck_out_tongue:

[root@fred ~]# config setprop postfix HeloHost myhelo.fio01.com
[root@fred ~]#
[root@fred ~]#
[root@fred ~]# signal-event nethserver-mail-common-save
[root@fred ~]#
[root@fred ~]#
[root@fred ~]# config getprop postfix HeloHost
myhelo.fio01.com
[root@fred ~]#
[root@fred ~]#
[root@fred ~]#

Now it should be correct.

So we have to wait a few hours to see what will it give.

Michel-André

why to not simply use the real FQDN of the server

:-?

Yes i know now :wink:

1 Like

Salut Spéphane,

How about that ?

[root@fred ~]# config setprop postfix HeloHost fred.fio01.com
[root@fred ~]#
[root@fred ~]# signal-event nethserver-mail-common-save
[root@fred ~]#
[root@fred ~]#
[root@fred ~]# config getprop postfix HeloHost
fred.fio01.com
[root@fred ~]#

Michel-André

to compare

╭─stephdl@leo.lan ~/dev/git_work  ‹master› 
╰─➤  host fred.fio01.com                                                                                          1 ↵

fred.fio01.com is an alias for fio01.com.
fio01.com has address 82.65.81.211
╭─stephdl@leo.lan ~/dev/git_work  ‹master› 
╰─➤  host prometheus.de-labrusse.fr
prometheus.de-labrusse.fr has address 164.132.77.216
prometheus.de-labrusse.fr mail is handled by 20 mx00.1and1.fr.
prometheus.de-labrusse.fr mail is handled by 21 mx01.1and1.fr.
prometheus.de-labrusse.fr mail is handled by 10 mail.de-labrusse.fr.

for me fred.fio01.com is not a FQDN but an alias

Salut Stéphane,

[root@fred ~]# config setprop postfix HeloHost fio01.com
[root@fred ~]#
[root@fred ~]#
[root@fred ~]# signal-event nethserver-mail-common-save
[root@fred ~]#
[root@fred ~]#
[root@fred ~]# config getprop postfix HeloHost
fio01.com
[root@fred ~]#

Is that OK ?

Michel-André

if this domain name point to the server yes

Hi Stéphane,

Do you mean the FQDN or the name-of-the-server.FQDN ?

Michel-André

FQDN is name.domain.com (fully qualified domain name)

when I look to your DNS, I cannot see a MX, it is something important

╰─➤  dig any fio01.com @8.8.4.4

; <<>> DiG 9.11.21-RedHat-9.11.21-1.fc32 <<>> any fio01.com @8.8.4.4
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44607
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;fio01.com.			IN	ANY

;; ANSWER SECTION:
fio01.com.		10799	IN	A	82.65.81.211
fio01.com.		10799	IN	NS	ns-150-a.gandi.net.
fio01.com.		10799	IN	NS	ns-228-b.gandi.net.
fio01.com.		10799	IN	NS	ns-223-c.gandi.net.
fio01.com.		10799	IN	SOA	ns1.gandi.net. hostmaster.gandi.net. 1597763352 10800 3600 604800 10800
fio01.com.		1799	IN	TXT	"v=DMARC1; p=none"
fio01.com.		1799	IN	TXT	"v=spf1 a:fred.fio01.com mx:mail.fio01.com ip4:82.65.81.211/32 ~all"
fio01.com.		1799	IN	TXT	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2YflmDziJ60TJHbr7YjADaOWxqG+6LbY2n96vuTWD8XuALyDQ1qHJKcNTSjRxfwPyS6QMBp/5fvPtTJovUn0Kkxh" "NggUYW0ycrqHUtOA1Pw5yORg53OmKytLWnsfnfIpZZ+D71jXH7r35otEUL6InFoeC2XQOD5/NdLweCc3rL6Uy/3nO7+G5ZMM1nU1jo2uWuOaDV+n90+WE2yVbkJtich+qj1QrlUd4lvC/UEqA/rhWN" "cs1IVG1WDRRWIOShwwOFAZmCQFa/mL7sDyHiJau19CLihaNwaKK2kbA7BU6DsxM2zO2ihh5iz5q7D7OnxS56IqEhwyOFNeKGaiRMFDrwIDAQAB"

;; Query time: 51 msec
;; SERVER: 8.8.4.4#53(8.8.4.4)
;; WHEN: mar. août 18 17:36:59 CEST 2020
;; MSG SIZE  rcvd: 716

this is mine

╰─➤  dig any de-labrusse.fr

; <<>> DiG 9.11.21-RedHat-9.11.21-1.fc32 <<>> any de-labrusse.fr
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62322
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;de-labrusse.fr.			IN	ANY

;; ANSWER SECTION:
de-labrusse.fr.		3599	IN	A	164.132.77.216
de-labrusse.fr.		21599	IN	NS	ns1092.ui-dns.biz.
de-labrusse.fr.		21599	IN	NS	ns1092.ui-dns.org.
de-labrusse.fr.		21599	IN	NS	ns1092.ui-dns.de.
de-labrusse.fr.		21599	IN	NS	ns1092.ui-dns.com.
de-labrusse.fr.		21599	IN	SOA	ns1092.ui-dns.biz. hostmaster.1and1.fr. 2017072501 28800 7200 604800 300
de-labrusse.fr.		3599	IN	MX	10 mail.de-labrusse.fr.
de-labrusse.fr.		3599	IN	MX	20 mx00.1and1.fr.
de-labrusse.fr.		3599	IN	MX	21 mx01.1and1.fr.

;; Query time: 75 msec
;; SERVER: 192.168.12.241#53(192.168.12.241)
;; WHEN: mar. août 18 17:35:05 CEST 2020
;; MSG SIZE  rcvd: 298

mail.de-labrusse.fr is a valid FQDN

╰─➤  host mail.de-labrusse.fr
mail.de-labrusse.fr has address 164.132.77.216
mail.de-labrusse.fr mail is handled by 10 164.132.77.216.