Bernd Petrovitsch writes:
> On 27/05/2020 01:08, Mark Sapiro wrote:
> > Basically unknown. For the most part, log files are us-ascii, but some
> > entries contain user entered data such as names or (malformed) email
>
> If the user enters his name in a HTML form with e.g. German umlauts,
>
Mark Sapiro writes:
> On 6/1/20 3:15 PM, Lucio Crusca wrote:
> > Ok, let's assume it is a deliverable address. Running the following
> > one-liner yields nothing:
My guess is that the real mailbox was replaced with a hash of that
mailbox. SHA-2-512 or SHA-3-512 would fit with the
On 6/1/20 3:15 PM, Lucio Crusca wrote:
>
> Ok, let's assume it is a deliverable address. Running the following
> one-liner yields nothing:
>
> # for i in /var/log/mail.log* ; do EXE=cat ; if [[ "$i" == *.gz ]] ;
> then EXE=zcat ; fi ; echo "$EXE $i ---" ; $EXE $i | grep
>
Il 01/06/20 21:15, Mark Sapiro ha scritto:
The trace headers in the message you attached all indicate it was sent
and delivered to ada3167eb87301cb4835917425f07...@libero.it.
You're right, I overlooked those headers and took for granted the recipient
address I found from the MTA logs was the
On 6/1/20 3:10 AM, Lucio wrote:
>
> A few hours ago I received a FBL complaint notification about a monthly
> subscription reminder marked as spam and actually coming from my server.
> The subscription reminder was attached to the FBL complaint, so I could
> see the mailman list subscribed email
On 6/1/20 6:11 AM, Jeffrey Westgate wrote:
> I am running v2.1.20, looking to upgrade to 2.1.32 (or 33), but the upgrade
> path seems to me to want the same options used in the previous install. I
> didn't do the previous install, so the one command I'm looking for is --
>
> the one command
If you still have access to the source directory used to build the previous
install, the compile command is in the file config.log... in my case
./configure --with-cgi-gid=apache
Quoting Jeffrey Westgate (jeffrey.westg...@arkansas.gov):
> I am running v2.1.20, looking to upgrade to 2.1.32 (or
I am running v2.1.20, looking to upgrade to 2.1.32 (or 33), but the upgrade
path seems to me to want the same options used in the previous install. I
didn't do the previous install, so the one command I'm looking for is --
the one command that will tell me what options were used in the
Until a few hours ago I was running mailman 2.1.29 on Debian Stretch, as
packaged by Debian, e.g. mailman_1:2.1.29-1_amd64.deb, so I was missing
the latest update published by Debian on April, 24 as
mailman_1:2.1.29-1+deb10u1_amd64.deb. That means my mailman was
vulnerable to this specific
Hi!
On 27/05/2020 01:08, Mark Sapiro wrote:
> On 5/26/20 4:30 PM, Brett Delmage wrote:
[...]
>> What is the character set coding for the log files, please?
>> I'm using MM 2.1.29
>
> Basically unknown. For the most part, log files are us-ascii, but some
> entries contain user entered data such
Mark Sapiro writes:
> On 5/26/20 4:30 PM, Brett Delmage wrote:
> > Hi!
> >
> > What is the character set coding for the log files, please?
> > I'm using MM 2.1.29
>
> Basically unknown. For the most part, log files are us-ascii,
I would consider declaring ISO-8859-1, ISO-8859-15, or
11 matches
Mail list logo
