Mail Server

14 posts / 0 new
Last post
#1 Mon, 12/29/2008 - 07:14
datateam

Mail Server

Hello I have some experience with Virtualmin, but I had a small break in use. I installed Ubuntu 8.04, updated packages to the latest version, and run the configuration script. The installation went well, start checking the script - all ok. I've created a new domain and started to test the mail. I send a message from the newly created account, Virtualmin writes a message "sent", but when I'm checking there is now new messages. In the other side also does not work. I checked the rule in the firewall - added exceptions, the status information report all services running properly.

Thanks for help Rafaƅ

Fri, 03/31/2006 - 18:54
Joe
Joe's picture

Yep, Virtualmin is very flexible. You can disable the local mailserver, and you can choose not to create mailboxes on the local machine (or create them on an LDAP server). You can also configure your DNS templates to point the MX record and mail.domain.tld to the other server.

It's pretty difficult to say exactly what you'll need, as the possibilities are pretty wide open--probably the simplest thing is to just disable mailbox and alias creation:

In Module Configuration find the option "Mailbox and alias configuration enabled?" and set it to No.

And also disable all mail related modules for server owners in the "Feature modules available to server administrators" section. Server Templates can be used to setup alternate DNS entries, as well--so you don't have to manually create the MX records to point to your other server.

--

Check out the forum guidelines!

Mon, 12/29/2008 - 17:19
andreychek

Hi Rafal,

Try looking in the Email logs. If there's a problem, those should tell you what's going on. On Ubuntu, you can find those in /var/log/mail.log.
-Eric

Sun, 06/07/2009 - 07:34 (Reply to #3)
eustachy

Hello

PróbowaÅ

Sun, 06/07/2009 - 07:34 (Reply to #4)
eustachy

Hello

PróbowaÅ

Tue, 12/30/2008 - 07:44 (Reply to #5)
ronald
ronald's picture

check DNS

WARNING: MX records points to a CNAME. CNAMEs are not allowed in MX records, according to RFC974, RFC1034 3.6.2, RFC1912 2.4, and RFC2181 10.3. The problem MX record(s) are:
mail.lava.pl points to ['jupiter.lava.pl']
This is not ok per the RFCs and can cause problems including mail being lost!

Tue, 12/30/2008 - 14:55 (Reply to #6)
eustachy

This my zone file
[code:1]
ttl 38400
@ IN SOA ns1.uos.pl. root.uos.pl. (
1230565944
10800
3600
604800
38400 )
@ IN NS ns1.uos.pl.
@ IN NS ns2.lava.pl.
ns1.uos.pl. IN A 85.89.182.168
ns.uos.pl. IN A 85.89.182.168
belfast.uos.pl. IN A 85.89.182.168
ns2.uos.pl. IN A 85.89.182.16
uos.pl. IN A 85.89.182.168
www.uos.pl. IN A 85.89.182.168
ftp.uos.pl. IN A 85.89.182.168
m.uos.pl. IN A 85.89.182.168
localhost.uos.pl. IN A 127.0.0.1
webmail.uos.pl. IN A 85.89.182.168
admin.uos.pl. IN A 85.89.182.168
mail.uos.pl. IN A 85.89.182.168
uos.pl. IN MX 5 mail.uos.pl.
uos.pl. IN TXT "v=spf1 a mx a:uos.pl ip4:85.89.182.168 ?all"
[/code:1]

Tue, 12/30/2008 - 15:12 (Reply to #7)
andreychek

Okay, it doesn't look like port 25 (SMTP) is open on mail.uos.pl.

My guess is that either there's some firewall software running on your server blocking that port, or that your ISP is blocking it.
-Eric

Tue, 12/30/2008 - 20:06 (Reply to #8)
eustachy

This is strange. I can connect from localhost, but from web I can't. I'don't configure nothing.All the things do installation script. When I'm looking in the webmin->firewall port 25 is accepting incoming connections.

Tue, 12/30/2008 - 23:42 (Reply to #9)
ronald
ronald's picture

check DNS namely the nameservers.

http://www.intodns.com/uos.pl

<div class='quote'>ERROR: One or more of your nameservers did not respond:
The ones that did not responded are:
85.89.182.168</div>

<div class='quote'>ERROR: looks like you have lame nameservers. The following nameservers are lame:
212.191.5.120</div>
<div class='quote'>Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!</div>

<div class='quote'>ERROR: I could not get any A records for www.uos.pl!</div>

Tue, 12/30/2008 - 23:49 (Reply to #10)
ronald
ronald's picture

and in the words of: http://www.squish.net/dnscheck/dnscheck.cgi

DNS check results for ns.uos.pl:
<div class='quote'>ns2.lava.pl 85.89.160.82 BIND: 9.3.1
ns2.lava.pl 212.191.5.120 BIND: 8.4.7-REL-NOESW
ns3.lava.pl 212.191.5.121 BIND: 9.2.4</div>

<div class='quote'>Asking ns1.uos.pl (85.89.182.168) for ns.uos.pl (type ANY)
Error: ns1.uos.pl (85.89.182.168): Resolve for ns.uos.pl. (ANY) failed: query timed out</div>

<div class='quote'>
Asking ns2.lava.pl (212.191.5.120) for ns.uos.pl (type ANY)
Referral: uos.pl is at ns1.uos.pl (85.89.182.168)
Referral: uos.pl is at ns2.lava.pl (212.191.5.120) Security: Server ns2.lava.pl (212.191.5.120) is recursive</div>

<div class='quote'>

Asking ns2.lava.pl (212.191.5.120) for ns.uos.pl (type ANY)
Loop detected! Probable cause is lame delegation to server with cached NS data</div>

<div class='quote'>Results
0.0% of queries will end in failure at 198.41.0.4 (A.ROOT-SERVERS.NET) - nameserver loop detected
10.3% of queries will end in failure at 194.0.1.2 (H-DNS.pl) - nameserver loop detected
67.3% of queries will end in failure at 85.89.182.168 (ns1.uos.pl) - query timed out
22.4% of queries will end in failure at 212.191.5.120 (ns2.lava.pl) - nameserver loop detected</div>

Tue, 12/30/2008 - 23:55 (Reply to #11)
ronald
ronald's picture

for IP 212.191.5.120: if this is on a campus/university of some kind, their firewall may be an issue
for the other IP, is it at home and have you configured the router?

Sun, 06/07/2009 - 07:34 (Reply to #12)
eustachy

Hello

Thanks for your suggestion. I call my Internet Provider, and they block my 25 port. They told me,that they didn't know I have my own mail server. Stupidos.

Thanks
Rafa&Aring;

Tue, 12/30/2008 - 00:10
eustachy

I writed in Polish,this is the english transation: I tried to re distribution system to another and this time I use CentOS 5.2.

When try to edit my post: Oops! You've hit a bug in the forum software. It'll be fixed soon

Topic locked