| Main Archive Page > Month Archives > postfix-users archives |
Re: Strange transport problem
From: Anne Wilson <cannewilson_at_nospam>Date: Sat Nov 19 2011 - 16:03:15 GMT
To: postfix-users@postfix.org
On Saturday 19 November 2011 14:57:44 Anne Wilson wrote:
> On Saturday 19 November 2011 04:21:21 Anne Wilson wrote:
> > On Saturday 19 November 2011 08:51:16 Stefan wrote:
> > > On Fri, Nov 18, 2011 at 3:37 PM, Anne Wilson
> > >
> > > <cannewilson@googlemail.com> wrote:
> > > > My home LAN has a strange problem. We use postfix on my IMAP
>
> I doubt it is really strange, but at this point there is still not
> enough information.
>
> > > > server to separate local mail from external mail. The
> > > > transport hash is based on:
> > > >
> > > > lydgate.net local:
> > > > .lydgate.net local:
> See postconf.5.html#parent_domain_matches_subdomains :: the pattern
> with the preceding dot is not going to be sought from this map.
It's clear that I am misunderstanding something. However, removing those
lines makes no difference, which is why I put them back. However, I see no
reason for them any more, so I've removed them again.
> Furthermore, with this domain in mydestination, the transport_maps
> listing is redundant.
Yet it clearly is working in the I can send a message to anne@lydgate.lan and
it goes directly into my mail spool - the result I wanted. If the transport
map isn't doing that, what is?
>
> > > > lydgate.lan local:
> > > > .lydgate.lan local:
> > > > * smtp:[mailhost.zen.co.uk]
>
> This entry is functionally equivalent to "relayhost".
>
That sounds reasonable, since I don't run my own smtp but use my ISP's.
> > > > .* smtp:[mailhost.zen.co.uk]
>
> This pattern would never be sought under any circumstances.
>
Ah yes - I remember now that I removed that some time past. I obviously used
an older backup that returned it. I'll take it out.
> > > > I also host a small mailing list on Zen's servers, using the
> > > > email address creativestitching@lydgate.org.
> > > >
> > > > I receive the mail for the list, and also the owner messages,
> > > > but I cannot write to the list, except by using webmail. The
> > > > problem appears to be that postfix thinks it is LAN traffic,
> > > > and can't find a user called creativestitching.
>
> http://www.postfix.org/STANDARD_CONFIGURATION_README.html#some_local
>
> > > > I assume that I have somehow triggered a catch-all, due to a
> > > > misunderstanding, so can someone please explain
> > > >
> > > > a) Why is creativestitching mail thought to be local?
>
> Is lydgate.org in mydestination? It's not in the mydestination you
> showed us below. We'd have to see *actual* logs, not a summary.
>
OK - can we try some definitions to see where I have misunderstood?
What I want to achieve - any mail addressed to xxx@lydgate.lan is put onto my
IMAP server's mail spool for the person concerned. Any mail other than
addressed to xxx@lydgate.lan should go to mailhost.zen.co.uk.
My laptops and desktops all are named something.lydgate.lan. They are set to
send all mail to 192.168.0.xx - the IMAP server, the one I am trying to re-
configure.
My external mail goes to my account on zen, someone@lydgate.org. Lydgate.net
is owned by me, but currently unused, so irrelevant to this problem.
In view of this, what should $myorigin and $mydestination be?
> > > > b) How can I correct it?
>
> Ditto, unknown.
>
> > > > c) Is there documentation that would explain this in more
> > > > detail?
>
> http://www.postfix.org/BASIC_CONFIGURATION_README.html
>
I try, I try, but man pages often only make sense *after* you have thoroughly
understood the basics. The man who helped me set up the original died last
year, so I no longer can ask questions of him.
> > > We don't know your network topology; are "home LAN" and "my IMAP
> > > server" on the same network?
> >
> > Sorry - obvious to me, but not to you :-) Yes, they are on the
> > same network. Other background information that may be relevant is
> > that originally the LAN was called lydgate.net. This is a second
> > domain that I have owned for some time, but not originally when I
> > set up the LAN. At that time I didn't know that .net was a
> > possible tld. When I changed from CentOS 5 to CentOS 6, being a
> > clean install, I decided that I ought to change the name to
> > lydgate.lan. I did have some problems at first, and tweaked
> > main.cf to get things working again. I assume that I have
> > introduced a problem that wasn't obvious until I needed to post to
> > creativestitching.
> >
> > > Someone will likely spot something if you provide, minimally, the
> > > output of postconf -n and relevant log output.
> >
> > It's so long since I had problems with postfix that I had forgotten
> > that. Output:
> >
> > alias_database = hash:/etc/aliases
> > alias_maps = hash:/etc/aliases
> > command_directory = /usr/sbin
> > config_directory = /etc/postfix
> > daemon_directory = /usr/libexec/postfix
> > data_directory = /var/lib/postfix
> > debug_peer_level = 2
> > home_mailbox = Maildir/
> > html_directory = no
> > inet_interfaces = localhost
> > inet_protocols = all
> > mail_owner = postfix
> > mail_spool_directory = /var/spool/mail
> > mailq_path = /usr/bin/mailq.postfix
> > manpage_directory = /usr/share/man
> > masquerade_domains = $mydomain
> > mydestination = $myhostname, localhost.$mydomain, $mydomain,
> > lydgate.lan
> > mydomain = lydgate.net
>
> .net != .org of course. This shows lydgate.net in mydestination, but
> not lydgate.org.
>
This really confused me. I originally set that to lydgate.org - and nothing
worked at all. When I changed it to lydgate.net, as it had originally been, I
got what seemed to be a working system - until this particular case came up.
> > myhostname = tosh.lydgate.net
> > mynetworks = 192.168.0.0/28, 127.0.0.0/8
> > myorigin = $mydomain
> > newaliases_path = /usr/bin/newaliases.postfix
> > queue_directory = /var/spool/postfix
> > readme_directory = /usr/share/doc/postfix-2.7.3/README_FILES
> > relayhost = [192.168.0.40]
> > sample_directory = /usr/share/doc/postfix-2.7.3/samples
> > sendmail_path = /usr/sbin/sendmail.postfix
> > setgid_group = postdrop
> > unknown_local_recipient_reject_code = 550
>
> And here we see that my dissertation on transport_maps above was not
> relevant, because you have not set that. A typo in main.cf, or did you
> just assume that /etc/postfix/transport had a special meaning?
I assumed that /etc/postfix/transport was used by default. What needs to be in
main.cf then? And if it's not being used, why is the local mail setting
working correctly?
> With no
> transport_maps set, your aforementioned hash is ignored, and relayhost
> is used. postconf.5.html#transport_maps
>
> > > http://www.postfix.org/DEBUG_README.html#mail
Again, I read without feeling any wiser. I appreciate your efforts, but I'll
never learn unless people like you explain in detail. I do read man pages,
but as I said, I find them useful *after* I have really got to grips with the
basics, and clearly something that I've misunderstood for several years is
causing my problem now.
Anne