> Andy Brown writes:
> I'm thinking that mailq.totalise.co.uk might have some sort
> junk-busting
> block on dynamic IPs that dont resolve to the Sender's
> domain. So when it
> sees this: (again, I let you line-wrap it)
>
> > Received: from modem-179.vanadium.dialup.pol.co.uk
> ([62.136.22.179] helo=marimba.home.net)
>
> it freaks out. Is this plausible?
>
> Perhaps if I reconfigure postfix to use
> myhostname = nowtsfree.freeserve.co.uk
> instead of
> myhostname = marimba.home.net
> when I go online, it might work for outgoing email.
> But that doesn't seem right for non-outgoing mail.
This could be the nub of the problem. I had problems a year or so ago with
Demon, the domain name I chose for my home lan was suddenly registered for
real by someone else, and I ended up trying to send stuff through the
external interface because real live DNS suddenly worked. I got a warning
over their 'acceptable use' policy rules. I changed to an internal domain
name which couldn't be used outside by giving it an TLD name that is not in
use.
If you use an inernal name for you lan, you must be sure there are no
conflicts with external names, i.e. make sure that you either use a real
live domain name that you own, or use a dummy one that CAN'T exist on the
internet.
It could, as you suggest, be rejecting your mail because it can not decide
who is trying to connect. This could be an inti-spam policy, a clumsy
attempt to block relaying or something like that. It would help if your
mail is sent externally as though it comes from your real external domain,
and then if there are any internal conflicts, deal with them internally.
Cheers.
Neil.
--------------------------------------------------------------------
http://www.lug.org.uk http://www.linuxportal.co.uk
http://www.linuxjob.co.uk http://www.linuxshop.co.uk
--------------------------------------------------------------------
This archive was generated by hypermail 2.1.3 : Fri 08 Mar 2002 - 15:55:01 GMT