Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Have a question related to a bad experience I got some time back.
I'm running a server and have several domain names pointing to it, but I don't have static IP. I update the IP automaticly through nameservers at zoneedit and it works fine.
Sendmail is working fine, I can send, recieve and relay mail. But currently I block the port 25 for following reason.
When I accept incoming connections on port 25 through my firewall my server is somehow blacklisted after some time (happened only once recently, never before) and the consequence is that all traffic to my server is blocked from some locations such as schoolnetworks etc...
The reason given was that mailservers on dynamic ip is a spam server.
How can I avoid this problem with my current setup?
I'm using Debian sarge with sendmail and iptables for filtering ports.
Same problem here, AOL, Cingular, Netscape, many others will not allow my sendmail to talk to them. I kept two MUA's set up, one for my domain, and another for my ISP, for a long time. THEN, I discovered "SmartHost" in sendmail. I _think_ this is how it works. He will try to communicate, but, if he doesn't get a receipt, he switches to the ISP server, and sends the mail. I have only a few weeks experience with this, but it certainly seems to be working. You can find setup information all over the web.
thanks I will look into smarthost, but I have never had any problems sending mail.
The problem lies in that my dynamic ip adress is banned by some organizations because the server doesn't meet some criteria. Is it simply because dynamic ip and mailserver is a no go, or does the sendmail server have to have some special settings set so that it avoid getting blacklisted as spamserver?
If I use smarthost I don't think that alone will change the fact that my IP gets banned? Having a banned IP for whatever reason can be really frustrating since it usually doesn't just keep you from sending or recieving mail, but all traffic is blocked from certain location (those who use the spamblock organizations lists).
Yes, you are right, it's the dynamic IP that causes this. Has nothing to do with your email agent, it's just the IP block that you are assigned from. Now, sendmail will NOT get a receipt from these places, rather, a bounce message is returned. He ignores that, and switches to your ISP's mail server, which will NOT be a dynamic addy, and therefore becomes acceptable to those places. The mail goes through n/p. This process is totally transparent to you, and can only be seen by looking in the mail logs. The ISP's addy will NOT be banned, and your IP will not be seen as the sending agent. Now, If someone knows more about this, please chime in, as I am going on little more than observation as to how this works. But, it ENDED the issue for me.
My problem now is this (if it is a problem). When hitting mailq I notice that all the messages sent turns up with the message:
(Deferred: Connection timed out with mail.theispdomainaddresscom.)
Last night I was so tired so I didn't bother to test more and today the test mails where actually waiting in my inbox. Looking in the log it seems like all mail was sent through my ISP How is the smarthost function working anyway? Is it queing up all messages for delivery in certain intervals or does it actually try to send the messages instantly? If the last is true my ISP seems to be too slow for the timout.
I tested again today and all mail sent is actually delivered, but not instantly so it seems like there is some interval for smarthost (correct me if I'm wrong).
Do you really think the AuthInfo should have "mail.myispdomain.com" as well instead of "myispdomain.com"? Looking in the log it seems like the request is actually handled by some other subdomain "xxxx.myispdomain.com" and I was afraid that making the auth too specific might make it fail.