Simon, > I posted this once before, but it doesn't happen often enough for me > to remember to login and do something about it. > > The advice I was given then was that the mydomain variable had not > been set. but he has on line 14 of /etc/amavis/conf.d/50-user, so now > I'm confused. > > Furthermore, if I grep for the pattern grep -inr > change-mydomain-variable /etc/amavis/ I get no results. > > Any ideas? > It's not fatal, just annoying.
Which version? In your previous posting you showed: > (28776-15) p.path BANNED:1 ... > (28776-15) local delivery: <[email protected]> -> banned-quarantine, > ... > (28776-15) smtp resp to RCPT (pip) > (<postmaster@!change-mydomain-variable!.example.com>): > 501 5.1.3 Bad recipient address syntax > (28776-15) Negative SMTP resp. to DATA: 554 5.5.1 Error: no valid recipients > (28776-15) (!)SEND via SMTP: <[email protected]> -> > <postmaster@!change-mydomain-variable!.example.com>, > [email protected] > 501 5.1.3 Failed, id=28776-15, from MTA([127.0.0.1]:10025): > 501 5.1.3 Bad recipient address syntax > (28776-15) (!)FAILED to notify admin: 501 5.1.3 Failed, id=28776-15, > from MTA([127.0.0.1]:10025): 501 5.1.3 Bad recipient address syntax So in that case it was a banned admin notification, which is sent to an address given by a lookup on @banned_admin_maps, which defaults to: @banned_admin_maps = (\$banned_admin, \%virus_admin, \$virus_admin); So it must be one of these settings that is copying a value of $mydomain *before* it has been set to a sensible value. The '!change-mydomain-variable!.example.com' is a default (and initial value) of a variable $mydomain. So, make sure the value of $mydomain is assigned *before* this variable is used in further expressions. Mark
