Your message dated Thu, 11 Oct 2018 07:32:21 +0200
with message-id <[email protected]>
and subject line Re: Bug#910590: bsd-mailx: error about missing command "jalias"
has caused the Debian Bug report #910590,
regarding bsd-mailx: error about missing command "jalias"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
910590: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910590
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bsd-mailx
Version: 8.1.2-0.20180807cvs-1
Severity: normal
$ echo test | mailx pot
Unknown command: "jalias"
$
The mail is sent, ma an error is signaled
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=C:en_GB:en:en_US:it:fr:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages bsd-mailx depends on:
ii base-files 10.1
ii exim4-daemon-light [mail-transport-agent] 4.91-8
ii libbsd0 0.9.1-1
ii libc6 2.27-6
ii liblockfile1 1.14-1.1
bsd-mailx recommends no packages.
bsd-mailx suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Francesco Potortì pisze:
>>> $ echo test | mailx pot
>>> Unknown command: "jalias"
>>> $
>>>
>>> The mail is sent, ma an error is signaled
>>
>> Please check your ~/.mailrc and /etc/mail.rc files. I guess one of them
>> contains the "jalias" command... If you remove it or replace with
>> "alias", then the error should be gone.
>
> Yes, thanks, that's was it...
>
Ok, so it's not a bug, I am closing the report.
Regards,
robert
--- End Message ---
