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 > > <cannewil...@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. Furthermore, with this domain in mydestination, the transport_maps listing is redundant. > > > lydgate.lan local: > > > .lydgate.lan local: > > > * smtp:[mailhost.zen.co.uk] This entry is functionally equivalent to "relayhost". > > > .* smtp:[mailhost.zen.co.uk] This pattern would never be sought under any circumstances. > > > I also host a small mailing list on Zen's servers, using the > > > email address creativestitch...@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. > > > 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 > > 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. > 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? 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 -- Offlist mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header
