Hello!
I have decied to create my own (and first) server for my company and I am at a halt. I have aquired a domain and dns services from simply(dot)com and I am having trouble setting the mailserver up correctly. Firstly, right now I cannot send nor recieve email but I don’t get any error in the frontend. When I check the everything.txt I only see a single error:
PROCESSING:0023969F: Filter ClamAV(127.0.0.1:3310):[ERROR]: Could not connect to filter
PROCESSING:0023969F: Error connecting to socket filter: ClamAV(127.0.0.1:3310)
Ok Seems I didn’t have ClamAv installed, core issue is still not fixed, but I got ClamAV to connect, now I need to get SpamAssassing to work then we’ll see.
Update:
Both Spamassassin and ClamAV are installed an running and detected by Axigen now. but still can’t send nor recieve emails.
Update: Seems to fail at the actual send now, but does find the recipient nameserver, in contrast to earlier.
In the log-snippet below; I have replaced the recipient email domain with ex.se to keep the line lengths a bit shorter
To clarify: It finds the correct MX entries, but somehow fails to actually send it.
PROCESSING:002617E0: Relay mail: found IPv4 MX entry 130.240.42.20 for domain ex.se with priority 5
PROCESSING:002617E0: Relay mail: found IPv6 MX entry 2001:6b0:10:42::42:20 for domain ex.se with priority 5
PROCESSING:002617E0: Relay mail: found IPv6 MX entry 2001:6b0:10:42::42:13 for domain ex.se with priority 5
PROCESSING:002617E0: Relay mail: found IPv4 MX entry 130.240.42.13 for domain ex.se with priority 5
PROCESSING:002617E0: Relay mail: found IPv6 MX entry 2001:6b0:10:42::42:20 for domain ex.se with priority 10
PROCESSING:002617E0: Relay mail: found IPv4 MX entry 130.240.42.13 for domain ex.se with priority 10
PROCESSING:002617E0: Relay mail: found IPv6 MX entry 2001:6b0:10:42::42:13 for domain ex.se with priority 10
PROCESSING:002617E0: Relay mail: found IPv4 MX entry 130.240.42.20 for domain ex.se with priority 10
PROCESSING:002617E0: Use 2001:6b0:10:42::42:20 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B0: Relay mail 2617E0: connecting to 2001:6b0:10:42::42:20:25
SMTP-OUT:000000B0: Relay mail 2617E0: unable to connect to 2001:6b0:10:42::42:20:25: Det går inte att hitta nätverksplatsen. Information om hur nätverksfel kan felsökas finns i Windows Hjälp.
SMTP-OUT:000000B0: Use 130.240.42.13 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B1: Relay mail 2617E0: connecting to 130.240.42.13:25
PROCESSING:002617E0: Shepherd thread received signal for delivery
PROCESSING:002617E0: Shepherd thread finished delivery signal
PROCESSING:002617E0: Unable to bind mail: Det går inte att hitta sökvägen.
SMTP-OUT:000000B1: Relay mail 2617E0: unable to connect to 130.240.42.13:25: Tidsgränsen för semaforen har uppnåtts.
SMTP-OUT:000000B1: Use 2001:6b0:10:42::42:13 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B2: Relay mail 2617E0: connecting to 2001:6b0:10:42::42:13:25
SMTP-OUT:000000B2: Relay mail 2617E0: unable to connect to 2001:6b0:10:42::42:13:25: Det går inte att hitta nätverksplatsen. Information om hur nätverksfel kan felsökas finns i Windows Hjälp.
SMTP-OUT:000000B2: Use 130.240.42.20 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B3: Relay mail 2617E0: connecting to 130.240.42.20:25
SMTP-OUT:000000B3: Relay mail 2617E0: unable to connect to 130.240.42.20:25: Tidsgränsen för semaforen har uppnåtts.
SMTP-OUT:000000B3: Unable to use 130.240.42.20 to relay mail 2617E0 for domain ex.se; try next relay
SMTP-OUT:000000B3: Use 130.240.42.13 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B3: Use 2001:6b0:10:42::42:13 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B3: Use 2001:6b0:10:42::42:20 to relay mail 2617E0 for domain ex.se
SMTP-OUT:000000B3: Relay mail 2617E0: no more relays for ex.se
SMTP-OUT:000000B3: Delivery attempt completed for mail 2617E0; 1 recipients remaining; reschedule for delivery
SMTP-OUT:000000B3: Set mail state to SEND FAILURE
Hello,
From shared log I understand that Axigen is unable to connect to any external mail server on port 25 (which this is usually a common practice of residential ISPs that tries to block spam content to be initiated from their network).
In order to double check that you have / haven’t access to “internet” destinations on TCP port 25 please check the following command (from the server / virtual instance / container you are running Axigen)
$ telnet -4 us1.axigen.com 25
Trying 184.173.55.100...
If all is fine you should get:
Connected to us1.axigen.com.
Escape character is '^]'.
220 us1.axigen.com This is AXIGEN
and you could just exist with quit command
quit
221-us1.axigen.com Axigen ESMTP is closing connection
221 Good bye
Connection closed by foreign host.
If you are receiving connection timeout or connection refused (or similar) you should double check with your network support team or your Service Provider for Internet connection for the reason of blocking access to external destinations on port 25.
HTH,
Ioan