Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: smeerbartje on August 05, 2008, 11:34:42 AM
-
I have a problem sending emails through my provider's smtp server. I have set the smtp server (smtp.ru.nl) into the admin pages: Address of Internet provider's mail server and no authentication, since this server does not require authentication.
When I try to send an email with, for example, a PHP script, the mail stays in the queue. The logfiles show the following errors:
1217878171.130205500 qp 7427: to=remote.rogier@bladiebla.com, uid=102, ddelay=90000.904626, xdelay=0.020269, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/)
1217878171.130215500 qp 7430: to=remote.rogier@bladiebla.com, uid=102, ddelay=90000.471096, xdelay=0.025255, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/)
1217878171.130251500 qp 7433: to=remote.rogier@bladiebla.com, uid=102, ddelay=90000.200754, xdelay=0.034582, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/)
1217878171.160778500 qp 7436: to=remote.rogier@bladiebla.com, uid=102, ddelay=89999.479803, xdelay=0.030583, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/)
I don't get it, because I can send emails from my desktop computer by using the same email server. What am I doing wrong?
-
It could be a dns problem if your other PC's use the isp dns server while the sme server use the internet root servers.
When I do "ping smtp.ru.nl" I got "can not be resolved".
Try that ping from Workstations and from the sme server. (I guess that the sme server is running as server only ?)
Post result from the two pings here.
If it should apear to be a dns problem it should work by replacing the smtp.ru.nl with the proper ip, I guess.
-
It could be a dns problem if your other PC's use the isp dns server while the sme server use the internet root servers.
When I do "ping smtp.ru.nl" I got "can not be resolved".
Try that ping from Workstations and from the sme server. (I guess that the sme server is running as server only ?)
Post result from the two pings here.
If it should apear to be a dns problem it should work by replacing the smtp.ru.nl with the proper ip, I guess.
Hi, here are the results of the ping to the server:
login as: root
root@195.169.214.146's password:
Last login: Tue Aug 5 11:49:10 2008 fm 62.140.137.125
[root@vhe-490181 ~]# ping smtp.ru.nl
PING smtp.ru.nl (131.174.66.167) 56(84bytes of data.
64 bytes from smtp.ru.nl (131.174.66.1): icmp_seq=0 ttl=253 time=0.436 ms
64 bytes from smtp.ru.nl (131.174.66.1): icmp_seq=1 ttl=253 time=0.453 ms
64 bytes from smtp.ru.nl (131.174.66.1): icmp_seq=2 ttl=253 time=0.447 ms
64 bytes from smtp.ru.nl (131.174.66.1): icmp_seq=3 ttl=253 time=0.456 ms
64 bytes from smtp.ru.nl (131.174.66.167): icmp_seq=4 ttl=253 time=0.546 ms
64 bytes from smtp.ru.nl (131.174.66.167): icmp_seq=5 ttl=253 time=0.434 ms
64 bytes from smtp.ru.nl (131.174.66.167): icmp_seq=6 ttl=253 time=0.431 ms
64 bytes from smtp.ru.nl (131.174.66.167): icmp_seq=7 ttl=253 time=0.443 ms
This is from the server. On my desktop computer, I got the same answers (but cannot post it now). So both computers can reach the server. What an I doing wrong?
-
From your original post:
(Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/
The remote mail server at 131.174.66.167 thinks there are too many open connections from your system (or from your IP address as perceived by smtp.ru.nl, which may be completely different).
If I try telnet 131.174.66.167 smtp I *should* get an SMTP greeting. Instead I get a TCP timeout.
There seems to be a problem with 131.174.66.167 (smtp.ru.nl).
-
From your original post:
(Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_my_ip_address/
The remote mail server at 131.174.66.167 thinks there are too many open connections from your system (or from your IP address as perceived by smtp.ru.nl, which may be completely different).
If I try telnet 131.174.66.167 smtp I *should* get an SMTP greeting. Instead I get a TCP timeout.
There seems to be a problem with 131.174.66.167 (smtp.ru.nl).
No, there is no problem with 131.174.66.167. The server is only usable for people in the same IP range. Both my server (which is a gateway) and the clients are in the range. Therefore they can ping and "use" the smtp server. When I do a telnet at the server, the following is the output:
login as: root
root@123.123.123.123's password:
Last login: Tue Aug 5 12:36:05 2008 fm 62.140.137.125
[root@vhe-490181 ~]# telnet smtp.ru.nl5
Trying 131.174.66.167...
Connected to smtp.ru.nl.
Escape character is '^]'.
220 smtp.ru.nl ESMTP Postfix
HELO smtp.ru.nl
250 smtp.ru.nl
mail from: my@email.com
250 2.1.0 Ok
rcpt to: my@email.com
250 2.1.5 Ok
data
354 End data with <CR><LF>.<CR><LF>
Subject: test, sent under telnet
this is a very nice test.
.
250 2.0.0 Ok: queued as 5272E8DC2D
Problem is that the mail is NOT delivered by the smtp server to the address. Strange isn't it? I will try to do THE SAME telnet session from my desktop computer tonight. (I'm on my work right now)
What is wrong?
-
The server is only usable for people in the same IP range.
Doh!
You'll need to repeat your telnet session from the SME server itself to figure out why the SME can't relay.
If your work system is behind the SME, your results will be affected by the setting of Security::Proxy settings::SMTP proxy status. If the SMTP proxy is enabled, then the SME will intercept all attempted outbound connections on port 25 and re-direct them to itself.
It is still the case that 131.174.66.167 is complaining about "too many connections from my ip address". Can you contact the admin for 131.174.66.167 to find out what the limits are? I have had an ISP that would refuse all email relay after a certain daily limit was reached - is this the case here? (In my case the limit was 50 emails per day - not even enough for a single home user! - but as soon as I called they increased the limit for me...)
-
I don't think we are at the same level here :). I did a telnet session from a SSH session on the server. So the mail has been sent by a telnet session on the server itself. In my last post, I told you guys the mail did not reach te recipient. But after 30 minutes the mail arrived correctly.
So, the problem must be somewhere in the SME server and not the SMTP server. When I do a telnet session, the server can send mails, but a process like PHP cannot send mails. In the server manager the smtp address is named correctly.
-
Seems like it is not the dns thing I was thinking about.
There is a small utility called " iptraf " that can be installed via yum.
Via iptraf you can nonitor a picture of how packets is streaming out and in from your server.
So using iptraf, you can monitor if your server is trying to send mail, like you want it to, if the receiving server ansver like expected, how many connections that is open etc.
-
I have a problem sending emails through my provider's smtp server. I have set the smtp server (smtp.ru.nl) into the admin pages: Address of Internet provider's mail server and no authentication, since this server does not require authentication.
When I try to send an email with, for example, a PHP script, the mail stays in the queue.
You should not be trying to send mail from a PHP script via your provider's SMTP server. Your PHP should send via localhost, and your SME server will queue the mail, and then send via your provider's SMTP server.
Your message is off-topic for this forum, because it concerns a PHP script which is not part of the SME Server 7.x CDROM install.
-
You should not be trying to send mail from a PHP script via your provider's SMTP server. Your PHP should send via localhost, and your SME server will queue the mail, and then send via your provider's SMTP server.
Your message is off-topic for this forum, because it concerns a PHP script which is not part of the SME Server 7.x CDROM install.
I don't think this message is off-topic, because my server is NOT able to send emails. It is not only PHP (running on the server) wich cannot send it. The problem is more abstract and is a server issue; therefore on-topic.
Is there a way to check if the server is able te send mails? For example, is it possible to send an email from the server console? And how?
-
Is there a way to check if the server is able te send mails? For example, is it possible to send an email from the server console? And how?
go to http://your.server.IP.address/webmail
log in as a user on the machine and send an e-mail. If this does not send you have a server problem.
-
I don't think this message is off-topic, because my server is NOT able to send emails. It is not only PHP (running on the server) wich cannot send it. The problem is more abstract and is a server issue; therefore on-topic.
Is there a way to check if the server is able te send mails? For example, is it possible to send an email from the server console? And how?
if you can't send mail via webmail or console with
echo "test test" > /tmp/testmsg
mail -s "my subject" emailaddress < /tmp/testmsg
then raise a bug in bugzilla
Thank you
Stefano
BTW, try to send a message directly, bypassing isp's smtp server and look in log files
-
"Is there a way to check if the server is able te send mails?"
The iptraf utility can be used to see if your own server is trying to send mail and if the remote server gives the proper answer.
To build in the buildt in web mail function is a good idea. I allways use that for testing the mail function. (Because this eleminationg pop problems etc.)
-
I installed the "E-Mail queue management"-RPM which creates the ability to manage the mailing queue in the server manager. When I use the "Try to send the queued messages now"-function, it says "Cannot send mails, qmail is not running". I did not shut down qmail or something... how can I start qmail?
And another thing: I cannot log on to webmail. When I go to server-address/webmail, the Horde application is showed, but no user can login. (Message: Login failed). I'm sure I use the correct user/pass combination. What is wrong with my system?
-
You are not trying to use the e-mail address as the user name by chance?
You should for sure be able to login as admin on that screen with your admin/root password.
Can you login to the server-manager panel and see for sure what your valid user names are?
-
You are not trying to use the e-mail address as the user name by chance?
You should for sure be able to login as admin on that screen with your admin/root password.
Can you login to the server-manager panel and see for sure what your valid user names are?
I cannot login as username "admin" and the corresponding password.
-
If I remember it right using web mail will require to use another loginname (acount) than root or admin.
Correction: Last message was uncorrect. I just did a remote logon on the webmail as admin and it worked.
I just tried to do a test using iptraf to monitor the treffic. I could see the connection at port 25, but it was not as detailed as I expected.
When I testing my mail server I just use to send a mail from my webmail to my gmail acount, and then an answer back.
By the way, near 100 % of the errors I hava had on the SME server since the first versions of e-smith have been due to my own modifications or incorrect use. I can not remember one serious problem that has ben due to the server itself, or occouring on an unmodified server.
(Thats the reason I run a near unmodified server today, and it has bee zero problems over time.)
-
Hmmm....
admin works fine on my servers. (root doesn't work)
Can you login to server-manager with admin?
He is getting a message that qmail is stopped but would that stop him from logging into webmail?
-
He is getting a message that qmail is stopped but would that stop him from logging into webmail?
I just did a test by stopping qmail on my test server. I was still able to log into webmail as admin.
-
I just tested out a slightly bether method (than ip traf) to see the ip packet traffic between the two mail servers.
From shell, type: ' tcpdump port 25 ' (tcpdump, a standard function on a sme server.)
This lists all packets to and from port 25, the mail server.
Using this command I could see a listing of all 28 packets needed to send a two word message to my gmail acount.
Iptraf might work bether when the connection does not work, then you can se the 'hanging connection'. When things work like they should the traffic passes so quicly so that iptraf will not be able to detect all of it. ' tcpdump port 25 ' on the other hand lists each of the individual packets on port 25.
Or slightely bether: tcpdump -i eth0 tcp port 25 (and -v or -vv can also be used to obtain more information.)
Or the clearest and most easy to read picture might be this one: tcpdump -i eth0 -n tcp port 25
http://www.tcpdump.org/tcpdump_man.html
-
"Is there a way to check if the server is able te send mails?"
The iptraf utility can be used to see if your own server is trying to send mail and if the remote server gives the proper answer.
You don't need such an additional tool. The qmail log file will show all successful and unsuccessful attempts to send mail.
-
Problem is that the mail is NOT delivered by the smtp server to the address. Strange isn't it?
Perhaps not so strange. The test message you sent is not a valid email message, as it does not have a To: or Date: header.
If you send a test message which has a valid format, and that is accepted by your ISP's smtp server, but not delivered to the recipient, then you will have to talk to your ISP. Nobody here can help you determine what they are doing with your email.
-
Can we summarize this set of problems?
We start here:
my server is NOT able to send emails
and advance to here:
I installed the "E-Mail queue management"-RPM which creates the ability to manage the mailing queue in the server manager. When I use the "Try to send the queued messages now"-function, it says "Cannot send mails, qmail is not running". I did not shut down qmail or something... how can I start qmail?
and here is another thing:
I cannot log on to webmail. When I go to server-address/webmail, the Horde application is showed, but no user can login. (Message: Login failed). I'm sure I use the correct user/pass combination.
It seems to me that we have multiple things broken here.
some questions>
1. What is the server version and history?
2. What contribs are installed?
3. What is the "E-Mail queue management"-RPM and where did it come from?
4. When did this problem start and what was installed just prior to the onset?
5. Can you send mail from the SME to local users on the SME inside the Lan? (user1@SME.Domain.com > User2@SME.Domain.com)
-
Can we summarize this set of problems?
I think it's time to raise a bug
-
You don't need such an additional tool. The qmail log file will show all successful and unsuccessful attempts to send mail.
Well I think that when the server does not do wat it is intended to do, it can have basically two reasons:
1. Reason one - a networking problem.
2. Reason two - a server problem.
When it comes to the alternative one, the case is that in allmost all cases you can troubleshoot the networking part of the problem with a 100 persent degree of presission using only a few simple tools. (iptraf, tcpdump, ping, traceroute, ifconfig and namap as I can remember them at the moment, and only nmap and iptraf will have to be installed via simple yum commands. The other is standard already built in Linux commands.)
If all network problems were trobleshooted with a presition level were all network related problems were solved and were all information about the networking traffic were known, then I think some of the treads in this forum would have been shorter and simpler.
My personal opininon is this: When there is a server problem, use first two-tree-five minutes on the network related problems. Get 100 persent ansvers for these questions. Then use the required time for the server rlelated questions.
I think that the server logs says what hapens and when it hapends, but it does not allways answer into detail why things does not work, and how it does not work. This is often very easy to find out about using the network tools, and this aditional info might also lead to a more simple trobleshooting of the server itself ??!!
During the years from the earliest revisions of the e-smith, 100 persent of the problems I have had with the SME server has been related to data communication or the improper modifications I have made myself. During the years I can not remember one serious problem, that has been traced down to be due to the basic unmodified server itself. (But other people might have other experiences.)
Anyhow I think it is not a drawback to allways have a 100 persent picture of the network related problems, and it is actually and usually quite easy to have.
-
After restarting the server, I was able to logon to horde. I used tcpdump (tcpdump -i eth0 -n tcp port 25) and monitored the smtp port while I tried to send a message to my emailaddress. This is the output of tcpdump:
09:23:22.739173 IP 195.169.214.146.41244 > 131.174.66.167.smtp: S 1872787004:1872787004(0) win 5840 <mss 1460,sackOK,timestamp 297011964 0,nop,wscale 2>
09:23:22.739510 IP 131.174.66.167.smtp > 195.169.214.146.41244: S 3456365655:3456365655(0) ack 1872787005 win 5792 <mss 1460,sackOK,timestamp 2314402756 297011964,nop,wscale 2>
09:23:22.739584 IP 195.169.214.146.41244 > 131.174.66.167.smtp: . ack 1 win 1460 <nop,nop,timestamp 297011965 2314402756>
09:23:22.740999 IP 131.174.66.167.smtp > 195.169.214.146.41244: P 1:31(30) ack 1 win 1448 <nop,nop,timestamp 2314402757 297011965>
09:23:22.741067 IP 195.169.214.146.41244 > 131.174.66.167.smtp: . ack 31 win 1460 <nop,nop,timestamp 297011966 2314402757>
09:23:22.741229 IP 195.169.214.146.41244 > 131.174.66.167.smtp: P 1:21(20) ack 31 win 1460 <nop,nop,timestamp 297011966 2314402757>
09:23:22.741472 IP 131.174.66.167.smtp > 195.169.214.146.41244: . ack 21 win 1448 <nop,nop,timestamp 2314402757 297011966>
09:23:22.741519 IP 131.174.66.167.smtp > 195.169.214.146.41244: P 31:47(16) ack 21 win 1448 <nop,nop,timestamp 2314402757 297011966>
09:23:22.741675 IP 195.169.214.146.41244 > 131.174.66.167.smtp: P 21:54(33) ack 47 win 1460 <nop,nop,timestamp 297011967 2314402757>
09:23:22.742176 IP 131.174.66.167.smtp > 195.169.214.146.41244: P 47:61(14) ack 54 win 1448 <nop,nop,timestamp 2314402757 297011967>
09:23:22.742382 IP 195.169.214.146.41244 > 131.174.66.167.smtp: P 54:92(38) ack 61 win 1460 <nop,nop,timestamp 297011968 2314402757>
09:23:22.784105 IP 131.174.66.167.smtp > 195.169.214.146.41244: . ack 92 win 1448 <nop,nop,timestamp 2314402767 297011968>
And the corresponding lines in the "sendmail style log"
1218094233.766218500 qp 9758: to=remote.rogier.lommers@philips.com, uid=453, ddelay=431.036773, xdelay=30.006169, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<admin@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
1218094243.771040500 warning: trouble opening remote/21/624517; will try again later
1218094269.763614500 warning: trouble opening remote/5/624041; will try again later
1218094281.762461500 warning: trouble opening remote/1/624796; will try again later
1218094283.762344500 warning: trouble opening remote/8/624803; will try again later
1218094283.762350500 warning: trouble opening remote/5/624800; will try again later
1218094283.762354500 warning: trouble opening remote/11/624806; will try again later
1218094283.762358500 warning: trouble opening remote/2/624797; will try again later
1218094298.760831500 warning: trouble opening remote/15/624488; will try again later
1218094310.759679500 warning: trouble opening remote/17/624490; will try again later
1218094323.765368500 warning: trouble opening remote/4/624500; will try again later
1218094345.758316500 warning: trouble opening remote/7/624480; will try again later
1218094355.757370500 warning: trouble opening remote/4/624546; will try again later
1218094367.756218500 warning: trouble opening remote/21/624517; will try again later
1218094393.753709500 warning: trouble opening remote/5/624041; will try again later
1218094405.752565500 warning: trouble opening remote/1/624796; will try again later
1218094407.752450500 warning: trouble opening remote/2/624797; will try again later
1218094407.752456500 warning: trouble opening remote/11/624806; will try again later
1218094407.752460500 warning: trouble opening remote/5/624800; will try again later
1218094407.752465500 warning: trouble opening remote/8/624803; will try again later
1218094422.750935500 warning: trouble opening remote/15/624488; will try again later
1218094434.749792500 warning: trouble opening remote/17/624490; will try again later
1218094447.748535500 warning: trouble opening remote/4/624500; will try again later
1218094469.746438500 warning: trouble opening remote/7/624480; will try again later
1218094479.745468500 warning: trouble opening remote/4/624546; will try again later
1218094491.744318500 warning: trouble opening remote/21/624517; will try again later
1218094517.741824500 warning: trouble opening remote/5/624041; will try again later
1218094529.740675500 warning: trouble opening remote/1/624796; will try again later
1218094531.740547500 warning: trouble opening remote/5/624800; will try again later
1218094531.740553500 warning: trouble opening remote/8/624803; will try again later
1218094531.740558500 warning: trouble opening remote/11/624806; will try again later
1218094531.740562500 warning: trouble opening remote/2/624797; will try again later
1218094546.739043500 warning: trouble opening remote/15/624488; will try again later
1218094558.737889500 warning: trouble opening remote/17/624490; will try again later
1218094571.736643500 warning: trouble opening remote/4/624500; will try again later
1218094593.734534500 warning: trouble opening remote/7/624480; will try again later
1218094603.733571500 warning: trouble opening remote/4/624546; will try again later
1218094615.732423500 warning: trouble opening remote/21/624517; will try again later
1218094641.729930500 warning: trouble opening remote/5/624041; will try again later
1218094653.728781500 warning: trouble opening remote/1/624796; will try again later
1218094655.728654500 warning: trouble opening remote/2/624797; will try again later
1218094655.728660500 warning: trouble opening remote/11/624806; will try again later
1218094655.728665500 warning: trouble opening remote/8/624803; will try again later
1218094655.728669500 warning: trouble opening remote/5/624800; will try again later
1218094670.727150500 warning: trouble opening remote/15/624488; will try again later
1218094682.725998500 warning: trouble opening remote/17/624490; will try again later
1218094695.724752500 warning: trouble opening remote/4/624500; will try again later
1218094717.722640500 warning: trouble opening remote/7/624480; will try again later
1218094726.740722500 warning: trouble opening remote/4/624546; will try again later
1218094739.734533500 warning: trouble opening remote/21/624517; will try again later
1218094756.771076500 qp 29934: to=remote.rogier@lommers.org, uid=102, ddelay=40031.467533, xdelay=30.030365, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<anonymous@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
1218094765.770032500 warning: trouble opening remote/5/624041; will try again later
1218094777.768881500 warning: trouble opening remote/1/624796; will try again later
1218094779.768755500 warning: trouble opening remote/8/624803; will try again later
1218094779.768761500 warning: trouble opening remote/5/624800; will try again later
1218094779.768765500 warning: trouble opening remote/11/624806; will try again later
1218094779.768769500 warning: trouble opening remote/2/624797; will try again later
1218094794.767265500 warning: trouble opening remote/15/624488; will try again later
1218094806.766100500 warning: trouble opening remote/17/624490; will try again later
1218094819.764854500 warning: trouble opening remote/4/624500; will try again later
1218094841.762747500 warning: trouble opening remote/7/624480; will try again later
1218094850.761877500 warning: trouble opening remote/4/624546; will try again later
1218094863.760647500 warning: trouble opening remote/21/624517; will try again later
1218094889.758149500 warning: trouble opening remote/5/624041; will try again later
1218094901.756993500 warning: trouble opening remote/1/624796; will try again later
1218094903.756894500 warning: trouble opening remote/2/624797; will try again later
1218094903.756900500 warning: trouble opening remote/11/624806; will try again later
1218094903.756904500 warning: trouble opening remote/5/624800; will try again later
1218094903.756908500 warning: trouble opening remote/8/624803; will try again later
-
And the corresponding lines in the "sendmail style log"
1218094233.766218500 qp 9758: to=remote.rogier.lommers@philips.com, uid=453, ddelay=431.036773, xdelay=30.006169, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<admin@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
You have no problem connecting to your ISP's mail server, but you are attempting to send an email with an invalid domain address - lommers.local. Configure your SME server with a valid domain name and you won't see this problem.
1218094243.771040500 warning: trouble opening remote/21/624517; will try again later
You have broken your mail queue, probably by using tools that you shouldn't have used. Don't try to fix a problem until you understand what the problem is.
-
You have broken your mail queue, probably by using tools that you shouldn't have used. Don't try to fix a problem until you understand what the problem is.
How do you see that I have broken my queue? And by the way, I only used tools, originating from the contribs.org page. :-?
Is it possible to repair the queue? Or just delete the whole queue and start all over? Please provide more information. Just mentionning that I have broken the queue does not help me any further. At least tell me how to fix it.
-
http://forums.contribs.org/index.php?topic=41680.0
This link shows how to rebuild a mail queue. I personally have never used it and do not completely understand what each command does. You will have to figure out which part you need and will lose all current mail in the queue
-
I installed the "E-Mail queue management"-RPM which creates the ability to manage the mailing queue in the server manager. When I use the "Try to send the queued messages now"-function, it says "Cannot send mails, qmail is not running". I did not shut down qmail or something... how can I start qmail?
I wonder if it does not look like CharlieBrady is right.
Isn't a improper configured server together with an extra new rpm the whole problem ?
By the way is this rpm a part of the SME server as it is intended to be used ? (I don't know, but I would not expect that any rpm tha can be downloaded or installed will work well.)
My personal opinion is that the first thing one should do before making any modifcations at all is to chek if the basic unmodified server does work. If it does not than it is time to check network connection and to solve those problems. Then it is time for doing modifications, after your basic setup has been verified and tested. One thing I think is important is to do things step by step, and to verify each step, before the next one.
-
I wonder if it does not look like CharlieBrady is right.
Isn't a improper configured server together with an extra new rpm the whole problem ?
By the way is this rpm a part of the SME server as it is intended to be used ? (I don't know, but I would not expect that any rpm tha can be downloaded or installed will work well.)
My personal opinion is that the first thing one should do before making any modifcations at all is to chek if the basic unmodified server does work. If it does not than it is time to check network connection and to solve those problems. Then it is time for doing modifications, after your basic setup has been verified and tested. One thing I think is important is to do things step by step, and to verify each step, before the next one.
Well, the whole point of installing the server queue management RPM is because my server could not send emails. Let me tell you guys what happened.
The server is a normal home-server, only used for routing my internet connection via the university network (100 mbit up/down :)) This network only allows us to send emails through the university smtp server (smtp.ru.nl) at port 25. After installing a CLEAN sme server, I could not mail. So I filled in the smtp.ru.nl at the mail options page at the administration pages. Then I still could not send emails and got errors in the email logs. Because of all the "test" emails, the queue was getting bigger and bigger so I thought it would be better to install the queue manager RPM, which enables me to delete all the queued mails. And now we are here....
By the way. I don't use the mail functionality of the server. I only want to make some cron-jobs on the server to send me some kind of statistics or something. (just for fun) All the client computers (the server is also a gateway) make a direct connection to smtp.ru.nl, without problems. Only the server cannot connect to this server. Strange, isn't it?
Now please, someone tell me how to fix this. I really don't think the problem is that big, because all the clients can mail (without using the server's mailer deamon), except the server itself. What to do next?
-
I is something strange with the configuration or something like that. Where does this address lommers.local come from ? What is the configured server name ?
If the server does not work, a modification is the last thing I would be thinking about. The first thing would be to check the configuration and then the network connection.
-
I would try a couple of things.
1> If there are only a couple of users, little or no data and the server is just used for a router. At this point I would reinstall and start from scratch.
2> If you choose not to take option one and the mails in the queue are not important I would rebuild the queue with the instructions from the other link. I would then first try to send a message with webmail to two users on your SME lan to make sure the server is working correctly. Then you can attempt to get the mail forwarding to work.
-
I would try a couple of things.
1> If there are only a couple of users, little or no data and the server is just used for a router. At this point I would reinstall and start from scratch.
2> If you choose not to take option one and the mails in the queue are not important I would rebuild the queue with the instructions from the other link. I would then first try to send a message with webmail to two users on your SME lan to make sure the server is working correctly. Then you can attempt to get the mail forwarding to work.
Dear all,
I just cleaned the entire email queue like described in the thread mentioned above. After this I tried to send an email from one local user to another. This email was delivered fine. After this I tried to send to an external email address (in fact, I tried three addresses) and this email was not received fine. The following entries are in the logfile:
1218102452.522793500 qp 8266: to=remote.email2@test.nl, uid=453, ddelay=10001.493172, xdelay=0.027207, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_195.169.214.146/)
1218102454.541138500 qp 14138: to=remote.email1@test.nl, uid=0, ddelay=401.397242, xdelay=0.003915, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_195.169.214.146/)
1218102482.523364500 qp 8266: to=remote.email1@test.nl, uid=453, ddelay=10031.493743, xdelay=30.027789, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<admin@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
1218103156.485937500 qp 29934: to=remote.email1@test.nl, uid=102, ddelay=48431.182394, xdelay=30.007164, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<anonymous@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
1218103488.483695500 qp 13645: to=remote.email2@test.nl, uid=453, ddelay=1681.494225, xdelay=0.010174, stat=Deferred (Connected_to_131.174.66.167_but_greeting_failed./Remote_host_said:_421_4.7.0_smtp.ru.nl_Error:_too_many_connections_from_195.169.214.146/)
1218103518.484904500 qp 13645: to=remote.email1@test.nl, uid=453, ddelay=1711.495434, xdelay=30.011393, stat=Deferred (131.174.66.167_does_not_like_recipient./Remote_host_said:_450_4.1.8_<admin@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_on_131.174.66.167./)
1218103578.479744500 qp 9412: to=remote.email1@test.nl, uid=453, ddelay=10060.782638, xdelay=60.044976, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218103714.474681500 qp 14138: to=remote.email1@test.nl, uid=0, ddelay=1661.330785, xdelay=60.002517, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218104163.997736500 qp 9758: to=remote.email2@test.nl, uid=453, ddelay=10361.268291, xdelay=360.515390, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218105528.877251500 qp 13645: to=remote.email1@test.nl, uid=453, ddelay=3721.887781, xdelay=0.010334, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218105654.873447500 qp 14138: to=remote.email1@test.nl, uid=0, ddelay=3601.729551, xdelay=0.008610, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218105888.851647500 qp 13645: to=remote.email2@test.nl, uid=453, ddelay=4081.862177, xdelay=359.984720, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218106732.809077500 qp 7518: to=remote.email1@test.nl, uid=453, ddelay=14885.253761, xdelay=0.008797, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218106852.805466500 qp 8266: to=remote.email1@test.nl, uid=453, ddelay=14401.775845, xdelay=0.008497, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218106852.941741500 qp 8266: to=remote.email2@test.nl, uid=453, ddelay=14401.912120, xdelay=0.144762, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218107919.180736500 qp 9412: to=remote.email1@test.nl, uid=453, ddelay=14401.483630, xdelay=0.342043, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218108203.179467500 qp 9758: to=remote.email2@test.nl, uid=453, ddelay=14400.450022, xdelay=0.026017, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218108368.172284500 qp 13645: to=remote.email1@test.nl, uid=453, ddelay=6561.182814, xdelay=0.008631, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218108368.310051500 qp 13645: to=remote.email2@test.nl, uid=453, ddelay=6561.320581, xdelay=0.146387, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218108514.303875500 qp 14138: to=remote.email1@test.nl, uid=0, ddelay=6461.159979, xdelay=60.002503, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
1218112008.307259500 qp 13645: to=remote.email1@test.nl, uid=453, ddelay=10201.317789, xdelay=0.338617, stat=Deferred (Sorry,_I_wasn't_able_to_establish_an_SMTP_connection._(#4.4.1)/)
Somehow the server is not able to send mails through my providers SMTP server. When I try to send an email by using a telnet session (from the server's console) via exactly the same smtp server (guide (http://www.yuki-onna.co.uk/email/smtp.html)), the mail has been sent out perfectly. This means there is nothing wrong with the communication (infrastructure) between the server and the smtp server.
-
From the log:
Remote_host_said:_450_4.1.8_<anonymous@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_
Why ?
-
From the log:
Remote_host_said:_450_4.1.8_<anonymous@lommers.local>:_Sender_address_rejected:_Domain_not_found/Giving_up_
Why ?
Thank you for you reply, but what do you mean by this? The smtp server is telling that he (or she :)) cannot find the domain lommers.local? That's obvious, because it is my local domain.
-
well
it's something (good and) normal that smtp servers refuse mail from unknown domain because of spammers..
so, if your isp smtp server doesn't need auth, you have to change the domain on your server.
IMO your problem is not network related or SME related.. it a bad/wrong configuration..
ciao
Stefano
-
well
it's something (good and) normal that smtp servers refuse mail from unknown domain because of spammers..
so, if your isp smtp server doesn't need auth, you have to change the domain on your server.
IMO your problem is not network related or SME related.. it a bad/wrong configuration..
ciao
Stefano
But when I try to send a mail by using my desktop computer it am able to send mails. (via Outlook, static internal IP address, the server provides the connection to the internet)
What do I need to change on the server (domain) to be able to send mails on the server?
-
Logon to console or via remote ssh terminal using username "admin" and passwors as for root, and you will see.
-
Your delegated mailserver is using a filter that requires a domain name that is resolvable. (in other words a real domain that has internet DNS records set for it.)
From your guide ref above:
You will then need to delcare where you are sending the email from:
HELO local.domain.name - dont worry too much about your local domain name although you really should use your exact fully qualified domain name as seen by the outside world the mail server has no choice but to take your word for it as of RFC822-RFC1123
You DO need to worry about that domain. If you were attempting to send this to an SME server with the local domain it would also be rejected as we reject non-resolveable domains by default.
Do the test above but put in a real resolveable domain name and see if it will go through.
-
disregard my post above. I did not see this part:
When I try to send an email by using a telnet session (from the server's console) via exactly the same smtp server (guide), the mail has been sent out perfectly.