On Tue, Apr 07, 2026 at 11:45:38AM -0400, Greg Wooledge wrote: > On Tue, Apr 07, 2026 at 11:00:21 -0400, Haines Brown wrote: > > >From MAILER-DAEMON Tue Apr 07 10:47:07 2026 > > Return-path: <> > > Envelope-to: [email protected] > > Delivery-date: Tue, 07 Apr 2026 10:47:07 -0400 > > Received: from Debian-exim by Iskra.histomat.net with local (Exim 4.96) > > id 1wA7hr-0003St-1r > > for [email protected]; > > Tue, 07 Apr 2026 10:47:07 -0400 > > This is a message generated locally on your own system. It was not > received over the network.
> So, here's my guesswork -- and you should verify all of this yourself. > > 1) You've got "iskra.histomat.net" configured as a local delivery > domain, but NOT "histomat.net". > > 2) You've got "postmaster" aliased to "[email protected]". > > 3) The remote system that received messages for @histomat.net addresses > is configured to reject messages with a null sender. > > 4) Your local system is stuck in a loop, because every time it tries > to send an error message to postmaster, the error message fails, > which triggers another error message, unendingly. > > If you verify that all of these points are correct, then changing any of > them should break the cycle. The most viable changes would be either > to re-alias postmaster to a local account instead of a remote address, > or to configure the remote mail server to stop rejecting null senders. > (Or, I suppose, to re-alias postmaster to a different remote account, > which accepts null senders.) As I just wrote in another message, it seems that my configuring exim to use histomat.net for its address rather than prepend to it a hostname may be the source of the problem. If I configure exim on both machines not to hide outgoing mail address that might solve the problem -- Haines Brown
