Can anyone see what I’m doing wrong please? I’m obviously missing something to do with the transport. But, I’m going crosseyed looking at this now. So I’m probably missing something really simple. thanks Robert
mysql-virtual-aliases.db majordomo [email protected] master.cf majordomo unix - n n - 50 pipe flags=R user=_majordomo argv=/usr/local/majordomo-1.94.5/wrapper majordomo -o SENDER=${sender} -m USER=${user} EXTENSION=${extension} mail.log output Result Jul 5 15:49:18 zeus postfix/pickup[54295]: 4DDE437F062A: uid=501 from=<robert> Jul 5 15:49:18 zeus postfix/cleanup[54347]: 4DDE437F062A: message-id=<[email protected]> Jul 5 15:49:18 zeus postfix/qmgr[54296]: 4DDE437F062A: from=<[email protected]>, size=368, nrcpt=1 (queue active) Jul 5 15:49:18 zeus postfix/qmgr[54296]: warning: connect to transport private/"/usr/local/majordomo-1.94.5/wrapper majordomo": No such file or directory Jul 5 15:49:18 zeus postfix/error[54349]: 4DDE437F062A: to=<[email protected]>, orig_to=<majordomo>, relay=none, delay=0.1, delays=0.08/0.01/0/0.01, dsn=4.3.0, status=deferred (mail transport unavailable) mailq -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- F224A37F04ED 368 Tue Jul 5 15:43:40 [email protected] (mail transport unavailable) [email protected] > On 5 Jul 2016, at 12:20, [email protected] wrote: > > Thanks Wietse, > I’ll start looking in those areas. I can see that allowing commands would be > a problem. > > Robert > > >> On 5 Jul 2016, at 12:16, Wietse Venema <[email protected]> wrote: >> >> [email protected]: >>> This is the problem line that can't be put in anything but the >>> standard /etc/aliases file. Or the majordomo.aliases file. >>> >>> majordomo: "|/path/to/majordomo/wrapper majordomo" >> >> With Postfix, command execution requires that you use the local(8) >> delivery agent (alias_maps or .forward file) or the pipe(8) daemon. >> >> Allowing commands elsewhere would introduce a vulnerability that >> was exploited by the Internet worm from 1998. >> >> Wietse >
