I had done the setup of Qmail server on redhat 9 and successfully send and receiving the mail locally for mail.rrchokhani.com but when i send the mail to remote host like gmail or yahoo or rediff it remains only in the qmailctl-queue

[root@localhost root]# qmailctl stat
/service/qmail-send: up (pid 10426) 538 seconds
/service/qmail-send/log: up (pid 8298) 2437 seconds
/service/qmail-smtpd: up (pid 10357) 596 seconds
/service/qmail-smtpd/log: up (pid 8300) 2437 seconds
messages in queue: 1
messages in queue but not yet preprocessed: 0
[root@localhost root]# qmailctl queue
messages in queue: 1
messages in queue but not yet preprocessed: 0
15 Nov 2010 11:01:07 GMT #1090780 1597 <satish.kadam@mail.rrchokhani.com>
remote satish.kadam1975@rediffmail.com
[root@localhost root]#

Also i had done the below command

echo '127.:allow,RELAYCLIENT=""' >>/etc/tcp.smtp

but still mail is in the qmailctl queue it does not go from qmailctl-queue

Regards

Satish

Hi,

Take a look at qmail-send logs (and maybe qmail-smtpd) to see what happens.

Regards

In the /var/log/qmail/current showing below errors.


@400000004ce0c736167cd40c starting delivery 1: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0c736167ce3ac status: local 0/10 remote 1/20
@400000004ce0c8b3012feabc delivery 1: deferral: Connected_to_202.137.234.30_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/@400000004ce0c8b3012ffe44 status: local 0/10 remote 0/20
@400000004ce0cbe6010ad68c starting delivery 2: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0cbe6010ae62c status: local 0/10 remote 1/20
@400000004ce0cd6134a2effc delivery 2: deferral: Connected_to_119.252.147.10_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce0cd6134a30384 status: local 0/10 remote 0/20
@400000004ce0d3b63449bff4 starting delivery 3: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0d3b63449cf94 status: local 0/10 remote 1/20
@400000004ce0d53208959414 delivery 3: deferral: Connected_to_119.252.147.10_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce0d5320895a79c status: local 0/10 remote 0/20
@400000004ce0dea60831addc starting delivery 4: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0dea60831bd7c status: local 0/10 remote 1/20
@400000004ce0dea701a8c054 delivery 4: deferral: Connected_to_119.252.147.10_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce0dea701a8d3dc status: local 0/10 remote 0/20
@400000004ce0ecb6019f7d3c starting delivery 5: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0ecb6019f8cdc status: local 0/10 remote 1/20
@400000004ce0ee3b00656ecc delivery 5: deferral: Connected_to_202.137.234.30_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce0ee3b00658254 status: local 0/10 remote 0/20
@400000004ce0fde63b707fd4 starting delivery 6: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce0fde63b708f74 status: local 0/10 remote 1/20
@400000004ce0ff6226ea5954 delivery 6: deferral: Connected_to_119.252.147.10_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce0ff6226ea68f4 status: local 0/10 remote 0/20
@400000004ce112362693f80c starting delivery 7: msg 1090780 to remote satish.kadam1975@rediffmail.com
@400000004ce11236269403c4 status: local 0/10 remote 1/20
@400000004ce113bd3467e6b4 delivery 7: deferral: Connected_to_119.252.144.10_but_greeting_failed./Remote_host_said:_553_550_Mail_from_114.143.28.239_blocked,_please_contact_postmaster@lotuslive.com/
@400000004ce113bd3467f654 status: local 0/10 remote 0/20
@400000004ce11cde1f593ee4 status: exiting
@400000004ce11cde205cb0dc status: local 0/10 remote 0/20

Please Suggest any clues.

Regards

Satish

Hi,

If you put on IP here or here, you'll see that it's blacklisted in a couple of rbl databases, so I guess that's the reason your mail is rejected.
See from the links there how to remove your server from the rbl lists.

Regards

I had removed my ip from PBL listing should i send the mail to other host after that.


Regards

Satish

Hi,

Good you've removed your server from the rbl lists. Do you have any clue why it was listed there?
You should eliminate the reason for which you get blacklisted, or you'll be blacklisted again.
Anyway, you can try to send an email and watch the logs to see how it goes

Regards

I think we have trojan or spam in our network for that reason our ip got blacklisted so i have a new question arise in mind.

Which Iptables Rules will block the spam or tojan which slows down the internet.my internet proxy server is redhat9 and i had downloaded some iptables rules which i want to give you for the brief.


#!/bin/sh
# Initial SIMPLE IP Masquerade test for 2.4.x kernels
# using IPTABLES.
#
# Once IP Masquerading has been tested, with this simple
# ruleset, it is highly recommended to use a stronger
# IPTABLES ruleset either given later in this HOWTO or
# from another reputable resource.
#
#
#
# Log:
# 0.75 - Added more kernel modules to the comments section
# 0.74 - the ruleset now uses modprobe vs. insmod
# 0.73 - REJECT is not a legal policy yet; back to DROP
# 0.72 - Changed the default block behavior to REJECT not DROP
# 0.71 - Added clarification that PPPoE users need to use
# "ppp0" instead of "eth0" for their external interface
# 0.70 - Added commented option for IRC nat module
# - Added additional use of environment variables
# - Added additional formatting
# 0.63 - Added support for the IRC IPTABLES module
# 0.62 - Fixed a typo on the MASQ enable line that used eth0
# instead of $EXTIF
# 0.61 - Changed the firewall to use variables for the internal
# and external interfaces.
# 0.60 - 0.50 had a mistake where the ruleset had a rule to DROP
# all forwarded packets but it didn't have a rule to ACCEPT
# any packets to be forwarded either
# - Load the ip_nat_ftp and ip_conntrack_ftp modules by default
# 0.50 - Initial draft
#

echo -e "\n\nLoading simple rc.firewall version $FWVER..\n"


# The location of the iptables and kernel module programs
#
# If your Linux distribution came with a copy of iptables,
# most likely all the programs will be located in /sbin. If
# you manually compiled iptables, the default location will
# be in /usr/local/sbin
#
# ** Please use the "whereis iptables" command to figure out
# ** where your copy is and change the path below to reflect
# ** your setup
#
IPTABLES=/sbin/iptables
DEPMOD=/sbin/depmod
MODPROBE=/sbin/modprobe


#Setting the EXTERNAL and INTERNAL interfaces for the network
#
# Each IP Masquerade network needs to have at least one
# external and one internal network. The external network
# is where the natting will occur and the internal network
# should preferably be addressed with a RFC1918 private address
# scheme.
#
# For this example, "eth0" is external and "eth1" is internal"
#
#
# NOTE: If this doesnt EXACTLY fit your configuration, you must
# change the EXTIF or INTIF variables above. For example:
#
# If you are a PPPoE or analog modem user:
#
# EXTIF="ppp0"
#
#
EXTIF="eth1"
INTIF="eth0"
echo " External Interface: $EXTIF"
echo " Internal Interface: $INTIF"


#======================================================================
#== No editing beyond this line is required for initial MASQ testing ==


echo -en " loading modules: "

# Need to verify that all modules have all required dependencies
#
echo " - Verifying that all kernel modules are ok"
$DEPMOD -a

# With the new IPTABLES code, the core MASQ functionality is now either
# modular or compiled into the kernel. This HOWTO shows ALL IPTABLES
# options as MODULES. If your kernel is compiled correctly, there is
# NO need to load the kernel modules manually.
#
# NOTE: The following items are listed ONLY for informational reasons.
# There is no reason to manual load these modules unless your
# kernel is either mis-configured or you intentionally disabled
# the kernel module autoloader.
#

# Upon the commands of starting up IP Masq on the server, the
# following kernel modules will be automatically loaded:
#
# NOTE: Only load the IP MASQ modules you need. All current IP MASQ
# modules are shown below but are commented out from loading.
# ===============================================================

echo "----------------------------------------------------------------------"

#Load the main body of the IPTABLES module - "iptable"
# - Loaded automatically when the "iptables" command is invoked
#
# - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "ip_tables, "
$MODPROBE ip_tables


#Load the IPTABLES filtering module - "iptable_filter"
# - Loaded automatically when filter policies are activated


#Load the stateful connection tracking framework - "ip_conntrack"
#
# The conntrack module in itself does nothing without other specific
# conntrack modules being loaded afterwards such as the "ip_conntrack_ftp"
# module
#
# - This module is loaded automatically when MASQ functionality is
# enabled
#
# - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "ip_conntrack, "
$MODPROBE ip_conntrack


#Load the FTP tracking mechanism for full FTP tracking
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_conntrack_ftp, "
$MODPROBE ip_conntrack_ftp


#Load the IRC tracking mechanism for full IRC tracking
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_conntrack_irc, "
$MODPROBE ip_conntrack_irc


#Load the general IPTABLES NAT code - "iptable_nat"
# - Loaded automatically when MASQ functionality is turned on
#
# - Loaded manually to clean up kernel auto-loading timing issues
#
echo -en "iptable_nat, "
$MODPROBE iptable_nat


#Loads the FTP NAT functionality into the core IPTABLES code
# Required to support non-PASV FTP.
#
# Enabled by default -- insert a "#" on the next line to deactivate
#
echo -en "ip_nat_ftp, "
$MODPROBE ip_nat_ftp


#Loads the IRC NAT functionality into the core IPTABLES code
# Required to support NAT of IRC DCC requests
#
# Disabled by default -- remove the "#" on the next line to activate
#
#echo -e "ip_nat_irc"
#$MODPROBE ip_nat_irc

echo "----------------------------------------------------------------------"

# Just to be complete, here is a partial list of some of the other
# IPTABLES kernel modules and their function. Please note that most
# of these modules (the ipt ones) are automatically loaded by the
# master kernel module for proper operation and don't need to be
# manually loaded.
# --------------------------------------------------------------------
#
# ip_nat_snmp_basic - this module allows for proper NATing of some
# SNMP traffic
#
# iptable_mangle - this target allows for packets to be
# manipulated for things like the TCPMSS
# option, etc.
#
# --
#
# ipt_mark - this target marks a given packet for future action.
# This automatically loads the ipt_MARK module
#
# ipt_tcpmss - this target allows to manipulate the TCP MSS
# option for braindead remote firewalls.
# This automatically loads the ipt_TCPMSS module
#
# ipt_limit - this target allows for packets to be limited to
# to many hits per sec/min/hr
#
# ipt_multiport - this match allows for targets within a range
# of port numbers vs. listing each port individually
#
# ipt_state - this match allows to catch packets with various
# IP and TCP flags set/unset
#
# ipt_unclean - this match allows to catch packets that have invalid
# IP/TCP flags set
#
# iptable_filter - this module allows for packets to be DROPped,
# REJECTed, or LOGged. This module automatically
# loads the following modules:
#
# ipt_LOG - this target allows for packets to be
# logged
#
# ipt_REJECT - this target DROPs the packet and returns
# a configurable ICMP packet back to the
# sender.
#

echo -e " Done loading modules.\n"



#CRITICAL: Enable IP forwarding since it is disabled by default since
#
# Redhat Users: you may try changing the options in
# /etc/sysconfig/network from:
#
# FORWARD_IPV4=false
# to
# FORWARD_IPV4=true
#
echo " Enabling forwarding.."
echo "1" > /proc/sys/net/ipv4/ip_forward


# Dynamic IP users:
#
# If you get your IP address dynamically from SLIP, PPP, or DHCP,
# enable this following option. This enables dynamic-address hacking
# which makes the life with Diald and similar programs much easier.
#
echo " Enabling DynamicAddr.."
echo "1" > /proc/sys/net/ipv4/ip_dynaddr


# Enable simple IP forwarding and Masquerading
#
# NOTE: In IPTABLES speak, IP Masquerading is a form of SourceNAT or SNAT.
#
# NOTE #2: The following is an example for an internal LAN address in the
# 192.168.0.x network with a 255.255.255.0 or a "24" bit subnet mask
# connecting to the Internet on external interface "eth0". This
# example will MASQ internal traffic out to the Internet but not
# allow non-initiated traffic into your internal network.
#
#
# ** Please change the above network numbers, subnet mask, and your
# *** Internet connection interface name to match your setup
#


#Clearing any previous configuration
#
# Unless specified, the defaults for INPUT and OUTPUT is ACCEPT
# The default for FORWARD is DROP (REJECT is not a valid policy)
#
echo " Clearing any existing rules and setting default policy.."
$IPTABLES -P INPUT ACCEPT
$IPTABLES -F INPUT
$IPTABLES -P OUTPUT ACCEPT
$IPTABLES -F OUTPUT
$IPTABLES -P FORWARD DROP
$IPTABLES -F FORWARD
$IPTABLES -t nat -F

echo " FWD: Allow all connections OUT and only existing and related ones IN"
$IPTABLES -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED -j ACCEPT
$IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT
#$IPTABLES -A FORWARD -j LOG

echo " Enabling SNAT (MASQUERADE) functionality on $EXTIF"
$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE

echo -e "\nrc.firewall-2.4 v$FWVER done.\n"


Above is my iptables rules which gives help me alot in my day today work

If you have any iptables rules which will block spam(trojan)in the network and also my day today will run then it will be helpful for me.

Thanks

Regards

Satish

Hi,

You should clean your network from whatever infected host is sending out spam. Check your logs to find the culprit and shut it down until you clean it.
Besides, you can't distinguish spam from a legitimate email with iptables.

Regards

After cleaning of my total network with antivirus and formatting of some systems i don't have any spam problem right now and the static ip is also not in the banned list but now i am facing strange problem when sending to any rediffmail or yahoo id the mail is going but it goes after 3-4 hours when i check in the logs it shows me starting deliver for the message but when i check in the qmailctl stat it shows me messages pending to send,can we set the smtp which will send messages after 2 0r 3 minutes, which file has to be edit to do this.

Regards

Satish

Hi,

I guess that your server is still grey-listed at those domains (because of the previous spamming attempts), that's why there is delay in mail delivery.
Does mail gets delivered immediately in other domains?

If you want to use another smtp server with better reputation as a smarthost, to send out your mail, you can add in /var/qmail/control/smtproutes a line:
and restart qmail

Regards

Thanks i will try from this smtp and get u know.

Regards

Satish

after adding the smarthost.domain.com in the /var/qmail/control/smtproutes the mail bounces and giving following error

Hi. This is the qmail-send program at mail.rrchokhani.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<satish.kadam1975@rediffmail.com>:
Sorry, I couldn't find any host named smarthost.domain.com. (#5.1.2)

Can i get a free smtp server to send messages

Regards

Satish

You're supposed to replace smarthost.domain.com with the actual mail server of your ISP.