Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #274979
| From | George at Clug <Clug@goproject.info> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: where is mail.log |
| Date | 2024-11-29 03:50 +0100 |
| Message-ID | <JNZeV-clDz-5@gated-at.bofh.it> (permalink) |
| References | <JNWK5-cklQ-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi,
I hope this helps.
As other have said, there has been a move to let systemctl manage log files, and we now access the logs via journalctl.
That said, I did find this command returned some info:
# grep "postfix\|open" /var/log/syslog
Nov 29 02:20:35 mail postfix/postfix-script[1522]: starting the Postfix mail system
Nov 29 02:20:35 mail postfix/master[1524]: daemon started -- version 3.5.25, configuration /etc/postfix
But to manage postfix, I have been using these commands:
# journalctl -u postfix
or
# journalctl -u postfix@-.service
or if I have also implemented DKIM and DMARC, then
# journalctl -u postfix@-.service -u opendkim -u opendmarc
If in a terminal I want to monitor in real time I use the -f option:
# journalctl -f -u postfix@-.service -u opendkim -u opendmarc
I have seen the use of -t which allows the specification of multiple identifiers.
journalctl -t postfix
journalctl -t postfix -t postfix/anvil -t postfix/bounce -t postfix/cleanup -t postfix_container -t postfix/error -t postfix/local -t postfix/master -t postfix/pickup -t postfix/postalias -t postfix/postfix-script -t postfix/proxymap -t postfix/qmgr -t postfix/scache -t postfix/sendmail -t postfix/smtp -t postfix/smtpd -t postfix/tlsmgr -t postfix/trivial-rewrite
https://man7.org/linux/man-pages/man1/journalctl.1.html
To show all fields emitted by a unit and about the unit, option
-u/--unit= should be used.
-t, --identifier=SYSLOG_IDENTIFIER
Show messages for the specified syslog identifier
SYSLOG_IDENTIFIER.
This parameter can be specified multiple times.
Today I discovered this useful line ( read up on the options from "man journalctl" :
journalctl --no-pager --quiet --identifier='postfix/smtp' --since='2022-10-30 00:00:00' --until='2024-12-06 23:59:59' --output='short'
journalctl --no-pager --quiet --identifier='postfix/smtp' --since='2022-10-30 00:00:00' --until='2024-12-06 23:59:59' --output='short'
PAGER CONTROL OPTIONS top
The following options control page support:
--no-pager
Do not pipe output into a pager.
-q, --quiet
Suppresses all informational messages (i.e. "-- Journal
begins at ...", "-- Reboot --"), any warning messages
regarding inaccessible system journals when run as a normal
user.
-t, --identifier=SYSLOG_IDENTIFIER
Show messages for the specified syslog identifier
SYSLOG_IDENTIFIER.
FILTERING OPTIONS top
The following options control how to filter journal records: -S, --since=, -U, --until= Start showing entries on or newer than the specified date, or on or older than the specified date, respectively.
-o, --output=
Controls the formatting of the journal entries that are
shown. Takes one of the following options:
short
is the default and generates an output that is mostly
identical to the formatting of classic syslog files,
showing one line per journal entry.
Added in version 206.
short-full
is very similar, but shows timestamps in the format the
--since= and --until= options accept. Unlike the
timestamp information shown in short output mode this
mode includes weekday, year and timezone information in
the output, and is locale-independent.
Added in version 232.
George.
On Friday, 29-11-2024 at 11:07 Bitfox wrote:
> My OS is debian 12 without GUI.
>
> After I installed postifx by apt, I can't find the path to mail.log.
>
> the log file in /var/log doesn't exist.
>
> do you know where is my mail.log now?
>
> Thanks.
>
>
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
where is mail.log Bitfox <hi@bitfox.ddns.net> - 2024-11-29 01:10 +0100
Re: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-11-29 01:20 +0100
Re: where is mail.log "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-11-29 21:20 +0100
Re: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-11-29 21:30 +0100
Re: where is mail.log gene heskett <gheskett@shentel.net> - 2024-11-29 22:30 +0100
Re: where is mail.log Nicolas George <george@nsup.org> - 2024-11-30 14:40 +0100
Re: where is mail.log "Roy J. Tellason, Sr." <roy@rtellason.com> - 2024-11-30 23:30 +0100
Re: where is mail.log Max Nikulin <manikulin@gmail.com> - 2024-12-03 04:10 +0100
Re: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-12-03 04:20 +0100
Re: where is mail.log "Jonathan Dowland" <jmtd@debian.org> - 2024-12-03 10:30 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-11-29 21:50 +0100
Re: where is mail.log pocket@homemail.com - 2024-11-29 22:40 +0100
Re: where is mail.log <tomas@tuxteam.de> - 2024-11-30 07:40 +0100
Re: where is mail.log Bitfox <bitfox@secubox.org> - 2024-11-30 13:40 +0100
Re: where is mail.log Scott Andrews <pocket@homemail.com> - 2024-11-30 14:00 +0100
Re: where is mail.log Richard Owlett <rowlett@access.net> - 2024-11-30 15:10 +0100
Re: where is mail.log <tomas@tuxteam.de> - 2024-11-30 14:30 +0100
Re: differences between sysvinit and systemd; was: where is mail.log Michael Kjörling <c9bc136c6063@ewoof.net> - 2024-11-30 14:30 +0100
Re: differences between sysvinit and systemd; was: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-11-30 15:10 +0100
Re: differences between sysvinit and systemd Michael Kjörling <c9bc136c6063@ewoof.net> - 2024-11-30 16:50 +0100
Re: where is mail.log Nicolas George <george@nsup.org> - 2024-11-30 14:50 +0100
Re: where is mail.log pocket@homemail.com - 2024-11-30 13:40 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-11-30 18:00 +0100
Re: where is mail.log Scott Andrews <pocket@homemail.com> - 2024-11-30 18:40 +0100
Re: where is mail.log <tomas@tuxteam.de> - 2024-11-30 19:00 +0100
Re: where is mail.log pocket@homemail.com - 2024-11-30 19:20 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-11-30 19:30 +0100
Re: where is mail.log <tomas@tuxteam.de> - 2024-11-30 19:30 +0100
Re: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-11-30 19:40 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-11-30 20:00 +0100
Re: where is mail.log <tomas@tuxteam.de> - 2024-11-30 20:20 +0100
Re: where is mail.log and the changing Linux ecosystem George at Clug <Clug@goproject.info> - 2024-12-01 01:10 +0100
Re: where is mail.log and the changing Linux ecosystem Greg Wooledge <greg@wooledge.org> - 2024-12-01 01:20 +0100
Re: where is mail.log and the changing Linux ecosystem George at Clug <Clug@goproject.info> - 2024-12-01 01:30 +0100
Re: where is mail.log and the changing Linux ecosystem <tomas@tuxteam.de> - 2024-12-01 07:20 +0100
Re: where is mail.log Jeffrey Walton <noloader@gmail.com> - 2024-12-02 17:30 +0100
Re: where is mail.log Scott Andrews <pocket@homemail.com> - 2024-11-30 20:00 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-11-30 19:10 +0100
Re: where is mail.log Anssi Saari <anssi.saari@debian-user.mail.kapsi.fi> - 2024-12-02 13:10 +0100
Re: where is mail.log Dan Ritter <dsr@randomstring.org> - 2024-11-29 01:40 +0100
Re: where is mail.log Greg Wooledge <greg@wooledge.org> - 2024-11-29 03:10 +0100
Re: where is mail.log Bitfox <hi@bitfox.ddns.net> - 2024-11-29 05:10 +0100
Re: where is mail.log Bitfox <hi@bitfox.ddns.net> - 2024-11-29 11:40 +0100
Re: where is mail.log George at Clug <Clug@goproject.info> - 2024-11-30 13:30 +0100
Re: where is mail.log George at Clug <Clug@goproject.info> - 2024-11-29 03:50 +0100
Re: where is mail.log Michael <ml@hemathor.de> - 2024-12-02 12:50 +0100
Re: where is mail.log Nicolas George <george@nsup.org> - 2024-12-02 13:10 +0100
Re: where is mail.log Andy Smith <andy@strugglers.net> - 2024-12-02 16:10 +0100
Re: where is mail.log Michael <ml@hemathor.de> - 2024-12-03 11:20 +0100
csiph-web