You're mistaken. It has absolutely nothing to do with sending, and
everything to do with receiving. ;)
On 08/24/2011 11:29 AM, William Olson wrote:
I believe that is for sending mail only ... not receiving. If I am not
mistaken.
Bill
http://www.goodcleanemail.com
http://www.freebsdrocks.net<http://www.centosrocks.net>
On Wed, Aug 24, 2011 at 2:28 PM, Eric Shubert <e...@shubes.net
<mailto:e...@shubes.net>> wrote:
Sorry, that's something I've never seen before. I'm guessing it's a
patch to qmail-smtpd, but that's not worth much.
As a short term work-around, you might try adding an entry to the
tcp.smtp file for the server in question, with the RELAYCLIENT=""
variable set, eg:
70.254.229.27 <tel:70.254.229.27>:RELAYCLIENT="",...(plus whatever
other variables your server uses typically)
This will essentially make your server an open relay for that IP
address. I expect this would work, but be careful with it. And don't
forget to "qmailctl cdb" after changing the tcp.smtp file.
--
-Eric 'shubes'
On 08/24/2011 11:03 AM, Rob Wright wrote:
Thanks for the reply. It's definitely not spamdyke, as we do not
have this
installed. When Inter7 did the setup for is SpamAssassin was
installed.
Here's what I've got in my log file, it's qmail-smtpd doing the
rejection.
@400000004e5539281689fb3c tcpserver: ok 10664
mail.poncacity.net:70.254.229.__3:25 :70.254.229.27
<tel:70.254.229.27>::53562
@400000004e5539281aedc6a4 CHKUSER accepted rcpt: from
<rwright@callisto.poncacity.__net:unknown:> remote
<callisto.poncacity.net:unknow__n:70.254
.229.27> rcpt<rwri...@poncacity.net
<mailto:rwri...@poncacity.net>> : found existing recipient
@400000004e5539281db9851c qmail-smtpd: senders must have valid
reverse DNS
@400000004e5539281dbe47dc tcpserver: end 10664 status 256
Part of the problem here is that I can't figure out what they've
hacked to get
qmail-smtpd to do the rejection. In my /var/qmail/control
directory there is
an 'rdns' file with a value of "1"; rdns checking is either on
or off.
Any further ideas? I suppose this may be a lesson for the boss
to "install
your own mail server" but that bridge is already crossed. If
there's no clear
answer I'll just have to call Inter7 for support and let them
deal with it.
Rob
On Wednesday 24 August 2011 11:49:44 Eric Shubert wrote:
That would take care of things if the rejection is due to an
RBL, but
the rejection is stated as being due to lack of rDNS, which is
different. The only thing I know of that rejects due to
missing rDNS
(using qmail) is spamdyke (a very good anti-spam tool btw).
What specifically is causing the reject? You might post a
sample from
your smtp log if you can't tell. If it's spamdyke, then the
spamdyke
config has several ways of whitelisting.
http://cr.yp.to/ucspi-tcp/__rblsmtpd.html
<http://cr.yp.to/ucspi-tcp/rblsmtpd.html>
Edit your tcp.smtp file and put the address in and set
RBLSMTPD="" and it
will bypass the RBL check for that IP address.
Afterwards, rebuild your
tcp.smtp.cdb file (depending on how your built your
toaster it'll be as
easy as "qmailctl cdb", or some other manual command)
Hope that helps.
On 11-08-24 9:14 AM, "Rob
Wright"<debianrob@poncacity.__net
<mailto:debian...@poncacity.net>> wrote:
Greetings. I hope this list is still intact and that
I'm on-topic. I've
searched for a solution and haven't been able to
come up with anything.
I've got a problem sprung up recently and can't
quite figure out how to
get
around it. While I'm waiting for a bureaucracy to
unsnaggle some DNS
information on their side, is there anyway for us to
whitelist a single
mail
server that's being rejected for not having rDNS?
The mail server is
known to
us and I feel comfortable with taking this action.
Hopefully this won't
be a
permanent solution but just a dirty hack while I
wait for others to do
their
jobs.
We've got a vanilla Inter7 installed vpopmail/qmail
system and I have
not been
able to figure out of this is do-able or not. If
it's possible how can I
go
about doing so?
Thanks for any help or pointers.
Rob Wright
debian...@poncacity.net <mailto:debian...@poncacity.net>
--
-Eric 'shubes'
!DSPAM:4e5544dc32711335127836!
