Adam Drake wrote:
>
[ snip ]
> Shorewall/rules
[ snip ]
> # Added A.Drake to allow pop3 access to qmail on firewall
> ACCEPT loc fw tcp 110
> ACCEPT loc fw tcp 25
> ACCEPT fw net tcp 110
> ACCEPT fw net tcp 25
Again, I do not know shorewall; but, regardless of these settings, I
still get this:
# nmap -sT -p 25 drakeweb.homeip.net
Starting nmap V. 2.54BETA31 ( www.insecure.org/nmap/ )
Interesting ports on 173-58.SPEEDe.golden.net (216.75.173.58):
Port State Service
25/tcp filtered smtp
*Something* is still blocking/filtering your port tcp 25 -- so, *NO*
Email can possibly get in from the internet.
[ snip ]
> qmail/me
>
> mail.drakeweb.homeip.net
Since tinydns is serving *only* private.network, here you need the name
of your internal mail server.
> qmail/rcpthosts
>
> drakeweb.homeip.net
Here, you need *both* the internal _and_ external mail server names.
> qmail/virtualdomains
>
> drakeweb.homeip.net:lrpqmail
> mail.drakeweb.homeip.net:lrpqmail
This could be left blank.
> qmail/plusdomain
Here you may need your internal domain.
> qmail/defaultdomain
Since tinydns is serving *only* private.network, you may need that here.
> qmail/local
Actually, this file is `locals' -- and, you need here *both* the
internal _and_ external mail server names.
[ snip ]
> Any ideas? The DYNDNS service I use says not to include MX entries if you
> only have one IP address. I am running tinydns - here's the content of the
> private file:
>
> .private.network::localhost
> .1.168.192.in-addr.arpa::localhost
> +firewall.private.network:192.168.1.254
> @drakeweb.homeip.net::mail.drakeweb.homeip.net
> =gabriel.private.network:192.168.1.10
> =daisy.private.network:192.168.1.11
> =solomon.private.network:192.168.1.13
This probably cannot work. You probably need to do something like this:
@private.network:192.168.1.254:mail.private.network
@1.168.192.in-addr.arpa::mail.private.network
Obviously, based on what you've posted, I cannot know what, if anything,
you are doing for public dns. However, it looks as though dyndns.org is
handling all of your public dns; so, this may indicate a problem:
# dnsqr ptr 58.173.75.216.in-addr.arpa
12 58.173.75.216.in-addr.arpa:
82 bytes, 1+1+0+0 records, response, noerror
query: 12 58.173.75.216.in-addr.arpa
answer: 58.173.75.216.in-addr.arpa 900 PTR 173-58.speede.golden.net
# dnsqr any 173-58.speede.golden.net
255 173-58.speede.golden.net:
58 bytes, 1+1+0+0 records, response, noerror
query: 255 173-58.speede.golden.net
answer: 173-58.speede.golden.net 900 A 216.75.173.58
# dnsqr any drakeweb.homeip.net
255 drakeweb.homeip.net:
53 bytes, 1+1+0+0 records, response, noerror
query: 255 drakeweb.homeip.net
answer: drakeweb.homeip.net 60 A 216.75.173.58
The problem is that your reverse dns does *not* resolve to the same name
that you are using:
drakeweb.homeip.net != 173-58.speede.golden.net
hth
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
