I can surf through my gateway but not send any emails?
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Gentoo, Redhat 9, SuSE 9.0, 9.2, Win XP
Posts: 149
Rep:
I can surf through my gateway but not send any emails?
This problem sort appeared out of nowhere. I use my rh9 box as a gateway with a firewall and then surf from my other machines on teh net including some WXP machines and other Linux boxes. For some reason I am not able to send any emails through from any machines other than my gateway? All machines can still surf no problem, just the sendign of email that is an issue?
i thougth your firewall could be block smtp port in FORWARD chain or something could be wrong in other chains, but it seems ok.
just im confused about ippp0. does ifconfig show "ippp0" or "ppp0" ?
but if clients can surf, this musnt be a issue.
may be the problem is MTU of ippp0 - it should be a bit small than ethernet's MTU (1500)... I'm not absolutely sure, but if "ifconfig ippp0" shows you that mtu is smaller than 1500 try this:
where is the mail server?
on the gate or outside your LAN?
if the mail server is outside, can you trace with traceroute?
some interestring in the result of ping from the gate... may be ttl=1 or lost packets...
may be it's stupid things, but really have no idea what's the problem, sorry
Distribution: Gentoo, Redhat 9, SuSE 9.0, 9.2, Win XP
Posts: 149
Original Poster
Rep:
I am still not getting anywhere with this problem. I can ping the smtp server from the clients no problem. But everytime I send a message I get the following error message:
Code:
An error occured while sending mail. The mail server responded:
<email@address.com>: Relay access denied. Please
verify that your email address is correct in your mail
Prefrences and try again
Is this problem appears only on sending?
I think problem is in the relay-access policy on the smtp server, on your gate everything is ok.
May be on the mail server is added header-check, or some other new anti-spam rules... sorry, at the present I'm not familiar with mail servers, just starting reading about postfix
May be the solution is to organize your own smtp-server on the gateway... or... just ask the mail-server administrator for some solution
oki im here is a firewall wall script give it a try may be it solves your problem
to run the script do...
chmod +x scriptname
=========
./scriptname
!/bin/bash
# Rules for gateway
#Clear \ Flush all the rules from the different chains and tables
iptables --flush
iptables --flush INPUT #Flush the INPUT chain
iptables --flush OUTPUT #Flush the OUTPUT chain
iptables --flush FORWARD #Flush the FORWARD chain
iptables -t nat --flush #Flush the nat table
iptables -t mangle --flush #Flush the mangle table
iptables --delete-chain #Delete any pre-existing chains
iptables -t nat --delete-chain #Delete any pre-existing chains from nat table
iptables -t mangle --delete-chain #Delete any pre-existing chains from the mangle table
#Setting the default Policies for the chains
iptables --policy INPUT DROP #Setting the default policy for INPUT chain
iptables --policy FORWARD ACCEPT #Setting the default plicy for FORWARD chain
iptables --policy OUTPUT ACCEPT #Setting the default policy for the OUTPUT chain
#Accepting traffic for and to internal interface
iptables -A INPUT -i lo -j ACCEPT #Allowing unlimited loopback traffic
iptables -A OUTPUT -o lo -j ACCEPT #Allowing unlimited loopback traffic
# Using Connection State to By-Pass checking
# Creating the rules
#iptables -t nat -A POSTROUTING -o ippp0 -j MASQUERADE
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A OUTPUT -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
# Allowing ssh to remote servers
iptables -A OUTPUT -p tcp --dport 22 -j ACCEPT
iptables -A INPUT -p tcp --dport 22 -j ACCEPT
iptables -A FORWARD -p tcp --dport 22 -j ACCEPT
Distribution: Gentoo, Redhat 9, SuSE 9.0, 9.2, Win XP
Posts: 149
Original Poster
Rep:
OK, it was what most of us suspected in the end. My service provider made some changes to his mail server and that messed me around. Changed the corresponding settings and away I go....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.