On Fri, Feb 06, 2026 at 10:54:57AM -0500, Dennis Putnam via Postfix-users wrote:
> However, I'm getting something I don't understand which may be a > mailman related issue. Unlikely, based on the below. > When mail is received from [email protected] The below mail is NOT **from** "[email protected]", its envelope **recipient** is "[email protected]", while the envelope sender is "[email protected]". It arrived via SMTP on the loopback interface, perhaps you need to look earlier in your logs to see where a message with ID: <[email protected]> really came from. > it appears to be going back to gmail rather than being intercepted and > processed by mailman. It isn't "going back" it is passed to some sort of LMTP service on port 8024 ont the local machine (either a content filter or a mailstore frontend). Are you reading the logs you're posting? Do you understand what they're telling you, or are they just line noise as far as you're concerned? > 2026-02-06T10:33:49.471389-05:00 dap002 postfix/smtpd[185613]: 7304C500071: > client=localhost[127.0.0.1] > 2026-02-06T10:33:49.514414-05:00 dap002 postfix/cleanup[185615]: 7304C500071: > message-id=<[email protected]> > 2026-02-06T10:33:49.553836-05:00 dap002 postfix/qmgr[185296]: 7304C500071: > from=<[email protected]>, size=10502, nrcpt=1 (queue active) > 2026-02-06T10:33:49.632822-05:00 dap002 postfix/lmtp[185616]: 7304C500071: > to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.17, > delays=0.09/0.02/0/0.06, dsn=2.0.0, status=sent (250 Ok) > 2026-02-06T10:33:49.635083-05:00 dap002 postfix/qmgr[185296]: 7304C500071: > removed Read these carefully, don't jump to conclusions, and ask about anything that isn't clear. > I realize there are separate processes there but that is what comes out > every time mail is received from gmail. That email isn't received from gmail. It is addressed to gmail, but is delivered to something else via LMTP. Perhaps a content filter and hence later to Gmail, or not... > I'm not sure what causes mail to be intercepted by mailman but it must > be a configuration issue. These are all generated automatically by the > mailman install. If mailmain is the LMTP server on port 8024, your transport settings are broken, mail TO gmail should not be routed to that transport. > main.cf: > > transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp What is in that transport table? > local_recipient_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp Why is the mailman transport table your (entire) local recipient table? Both of these are unwise, especially if you don't know what's in that table. > relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains Again, why? > > postfix_lmtp: > > # Aliases which are visible only in the @gmail.com domain. > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 > [email protected] lmtp:[127.0.0.1]:8024 Why on earth would you put these entries there? > postfix_domains: > > gmail.com gmail.com Whatever for? The solution to logs that read like line noise to you isn't a configuration that also reads like line-noise to everyone else. You need to read the Postfix book by Patrick and Ralf, and start with a default configuration that you evolve step by step, testing after each modest change before moving further, until it meets your requirements. Trying random tweaks won't get you there. -- Viktor. 🇺🇦 Слава Україні! _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
