On 13.01.25 11:58, Turritopsis Dohrnii Teo En Ming via Postfix-users wrote:
Subject: URGENT help needed with Postfix which stopped working on 11 Jan 2025
Saturday at about 3.00 AM
SYSTEM INFORMATION
OS type and version AlmaLinux 9.5
Webmin version 2.202
Virtualmin version
Subject: URGENT help needed with Postfix which stopped working on 11 Jan 2025
Saturday at about 3.00 AM
SYSTEM INFORMATION
OS type and version AlmaLinux 9.5
Webmin version 2.202
Virtualmin version 7.30.4
Webserver version 2.4.62
Related packagesPostfix
Dear
On February 24, 2020 8:47:49 AM UTC, Viktor Dukhovni
wrote:
>>
>> On Feb 24, 2020, at 2:27 AM, Michael wrote:
>>
>> Feb 22 08:50:07 mail postfix/smtpd[12952]: connect from
>bendel.debian.org[82.195.75.100]
>> Feb 22 08:50:07 mail postfix/smtpd[12952]: setting up TLS connection
>from bendel.
i forgot:
On Monday, February 24, 2020 9:47:49 AM CET, Viktor Dukhovni wrote:
Were TLS sessions failing from all senders or just particular systems?
it seemes to me, that all tls sessions failed, since no mail was delivered
at all after the switch.
greetings...
hey,
On Monday, February 24, 2020 9:47:49 AM CET, Viktor Dukhovni wrote:
This looks like a client (or firewall, etc. in between) that does not
correctly support TLS 1.3. What's new on your system is not Postfix 3.4,
but a sufficiently recent version of OpenSSL that has TLS 1.3 support.
i came
>
> On Feb 24, 2020, at 2:27 AM, Michael wrote:
>
> Feb 22 08:50:07 mail postfix/smtpd[12952]: connect from
> bendel.debian.org[82.195.75.100]
> Feb 22 08:50:07 mail postfix/smtpd[12952]: setting up TLS connection from
> bendel.debian.org[82.195.75.100]
> Feb 22 08:50:07 mail postfix/smtpd[129
hey,
first, let me thank you for your answer. i really appreciate this!
On Monday, February 24, 2020 12:20:27 AM CET, Viktor Dukhovni wrote:
smtpd_tls_security_level = may
smtpd_tls_lloglevel = 1
That's fine, but not consistent with the verbose logging below, did you
temporarily set a higher
On Sun, Feb 23, 2020 at 10:45:14PM +0100, Michael wrote:
> After upgrading from debian stretch (providing postfix 3.1.14) to
> buster (providing postfix 3.4.8), I just found out that no incoming
> mail was received any longer. Digging a little deeper showed me that
> turning of tls resolved this
hey,
after upgrading from debian stretch (providing postfix 3.1.14) to buster
(providing postfix 3.4.8), i just found out that no incoming mail was
received any longer. digging a little deeper showed me that turning of tls
resolved this issue. but then again, there was no tls...
i would appr
Quoting Postfix User :
I assume you have read: http://www.postfix.org/DEBUG_README.html#mail
Specifically, if the problem is SASL related, consider including the output
from the saslfinger tool. This can be found at
http://postfix.state-of-mind.de/patrick.koetter/saslfinger/.
Yup, and now
On Thu, 27 Aug 2015 07:39:48 +0200, Martin Skjöldebrand stated:
> After a lot of head scratching and despair, I *think* I got the
> problem down to sasl authentication didn't authenticate. I can now
> send from one account (this) but not my main address with the same
> settings (w/ change of
After a lot of head scratching and despair, I *think* I got the
problem down to sasl authentication didn't authenticate. I can now
send from one account (this) but not my main address with the same
settings (w/ change of user/pw naturally). Looking further into this.
/Martin S
Have you verified that access to port 25 from localhost works as expected?
Yes it does
Does openssl s_client -connect mail.skjoldebrand.eu:465 work from
remote? From localhost to localhost?
Yup both works.
Do you have a firewall?
It hasn't blocked port 25 before (its on the hosting si
Hi,
On 2015-08-23 12:36, Martin Skjöldebrand wrote:
Quoting Christian Kivalo :
Logs are not say much at all, possibly because I'm locking at the
wrong logs. Any thoughts on what might have happened here?
/var/log/{syslog,messages,mail.log}? One of those should be it.
I can't see that any o
Hi,
However, after a major infrastructure crash at the hosting company the
server is now up again. Still the same problem though. If anyone sent
any suggestions in the last 12 hours or so, I'm still eagerly waiting
for ideas.
Your server seems to not respond, at least no response to a ping,
Time to run your own servers then :)
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Martin Skjöldebrand
Sent: Sunday, August 23, 2015 11:33 PM
To: postfix-users@postfix.org
Subject: Re: "stopped working"
On Sun,
On Sun, 2015-08-23 at 14:16 +0200, Benny Pedersen wrote:
On August 23, 2015 11:04:32 AM Martin Skjöldebrand
> [mskjoldebrand@localhost ~]$ telnet mail.skjoldebrand.eu 465
you must be kidding here ?
No just not thinking.
However, after a major infrastructure crash at the hosting company the
On August 23, 2015 11:04:32 AM Martin Skjöldebrand
[mskjoldebrand@localhost ~]$ telnet mail.skjoldebrand.eu 465
you must be kidding here ?
telnet does not know how to make ssl connection
try man openssl and look for s_client
Quoting Christian Kivalo :
Logs are not say much at all, possibly because I'm locking at the
wrong logs. Any thoughts on what might have happened here?
/var/log/{syslog,messages,mail.log}? One of those should be it.
I can't see that any of them even register a connection attempt from my MUA
Hi,
Am 23. August 2015 11:03:45 MESZ, schrieb "Martin Skjöldebrand"
:
>Hi,
>
>Love those subjects.
>I was about to setup DKIM on my mail server when I noticed I "all of a
>
>sudden" can't send mail from MUAs any longer. Before trying to set up
>DKIM I got Mailman working and could still use
465 expects SSL encrypted communication from the start.
p@rick
* Martin Skjöldebrand :
> Hi,
>
> Love those subjects.
> I was about to setup DKIM on my mail server when I noticed I "all of
> a sudden" can't send mail from MUAs any longer. Before trying to set
> up DKIM I got Mailman working an
Hi,
Love those subjects.
I was about to setup DKIM on my mail server when I noticed I "all of a
sudden" can't send mail from MUAs any longer. Before trying to set up
DKIM I got Mailman working and could still use MUAs without problems.
I reverted to a previously known "working" postfix main
btb:
> i guess i consider lost logs to be a bug - i'll submit a bug report to
> ubuntu for this. in your opinion, would this be something the postfix
> package maintainer should address, or the syslog-ng packager maintainer
> [or is it just the admin's fault]?
Postfix, with chroot turned on, r
On Fri, Jan 16, 2015 at 10:42:54AM -0500, btb wrote:
> I guess I consider lost logs to be a bug - I'll submit a bug report to
> ubuntu for this. In your opinion, would this be something the postfix
> package maintainer should address, or the syslog-ng packager maintainer [or
> is it just the admi
On 2015.01.16 09.43, wie...@porcupine.org (Wietse Venema) wrote:
btb:
postconf -Mf
smtp inet n - - - 1 postscreen
Yep, it's chrooted. You need to configure syslog to add a log
socket to the jail, or turn off chroot.
during this period, postfix activity
Am 16.01.2015 um 15:33 schrieb Wietse Venema:
Wietse Venema:
FreeBSD:
# mkdir -p /var/spool/postfix/var/run
# syslogd -l /var/spool/postfix/var/run/log
Linux, OpenBSD:
# mkdir -p /var/spool/postfix/dev
# syslogd -a /var/spool/postfix/dev/log
Except that on some systems
btb:
> >>> postconf -Mf
> >> smtp inet n - - - 1 postscreen
> >
> > Yep, it's chrooted. You need to configure syslog to add a log
> > socket to the jail, or turn off chroot.
>
> during this period, postfix activity from all other postfix processes is
> gettin
On 2015.01.15 22.21, Viktor Dukhovni wrote:
On Thu, Jan 15, 2015 at 09:57:53PM -0500, b...@bitrate.net wrote:
i happened to notice that on one of our two mxes, no postscreen activity was
logged between 06:25:09 and 11:54:42:
Jan 15 06:25:09 mta2 postfix/postscreen[22371]: DISCONNECT
[103.242
Wietse Venema:
> Viktor Dukhovni:
> > > >postconf -Mf
> > > smtp inet n - - - 1 postscreen
> >
> > Yep, it's chrooted. You need to configure syslog to add a log
> > socket to the jail, or turn off chroot.
>
> FreeBSD:
>
> # mkdir -p /var/spool/postfix/va
Viktor Dukhovni:
> > >postconf -Mf
> > smtp inet n - - - 1 postscreen
>
> Yep, it's chrooted. You need to configure syslog to add a log
> socket to the jail, or turn off chroot.
FreeBSD:
# mkdir -p /var/spool/postfix/var/run
# syslogd -l /var/spool/p
On Thu, Jan 15, 2015 at 09:57:53PM -0500, b...@bitrate.net wrote:
> i happened to notice that on one of our two mxes, no postscreen activity was
> logged between 06:25:09 and 11:54:42:
>
> Jan 15 06:25:09 mta2 postfix/postscreen[22371]: DISCONNECT
> [103.242.116.92]:37543
> Jan 15 11:54:42 mta2
On 12/30/2011 10:53 AM, Mark wrote:
> My apologies for the cross-posting but I believe it is relevant.
>
> I have been running postfix for 8+ months without problems.
> Recently ( a week or two) I had a user complain that he could no
> longer send. It appears that postfix is no longer accept
My apologies for the cross-posting but I believe it is relevant.
I have been running postfix for 8+ months without problems.
Recently ( a week or two) I had a user complain that he could no longer
send. It appears that postfix is no longer accepting SSL/TLS
connections. STARTTLS is work
On 2010-04-15 Bruno Ribeiro da Silva wrote:
> Hi, I'm having some trouble with my production server, that mailman
> stopped working apparently without any modification. I think
> everything at my postfix configuration is ok, but what I'm seeing is
> that virtual_alias
On 4/15/2010 3:22 PM, Bruno Ribeiro da Silva wrote:
Hi, I'm having some trouble with my production server, that mailman
stopped working apparently without any modification. I think
everything at my postfix configuration is ok, but what I'm seeing is
that virtual_alias_maps isn&#x
Hi, I'm having some trouble with my production server, that mailman
stopped working apparently without any modification. I think
everything at my postfix configuration is ok, but what I'm seeing is
that virtual_alias_maps isn't working as expected.
My setup consists in one
on mine to: 0777. I figured it was easier
than finding that something else had stopped working.
--
Jerry
postfix.u...@yahoo.com
TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail
TO (UN)SUBSCRIBE see http://www.postfix.org/lists.html
Leibowitz's Rule:
When hammering a nail
Jerry wrote:
> On Fri, 30 Oct 2009 16:26:10 +0100
> Erwan David replied:
>
>> Jerry a écrit :
>>> System: FreeBSD-7.2
>>>
>>> I just updated to clamav-0.95.3 on my system. I then realized that
>>> clamav-milter and Postfix were no longer connecting.
>>>
>>>
>>> # Enable clamav-milter
>>> milter_
On Fri, 30 Oct 2009 16:26:10 +0100
Erwan David replied:
>Jerry a écrit :
>> System: FreeBSD-7.2
>>
>> I just updated to clamav-0.95.3 on my system. I then realized that
>> clamav-milter and Postfix were no longer connecting.
>>
>>
>> # Enable clamav-milter
>> milter_default_action = accept
>>
Jerry a écrit :
> System: FreeBSD-7.2
>
> I just updated to clamav-0.95.3 on my system. I then realized that
> clamav-milter and Postfix were no longer connecting.
>
>
> # Enable clamav-milter
> milter_default_action = accept
> smtpd_milters = unix:/var/run/clamav/clmilter.sock
>
>
> srwxr-xr-
System: FreeBSD-7.2
I just updated to clamav-0.95.3 on my system. I then realized that
clamav-milter and Postfix were no longer connecting.
# Enable clamav-milter
milter_default_action = accept
smtpd_milters = unix:/var/run/clamav/clmilter.sock
srwxr-xr-x 1 clamav wheel 0B Oct 30 10:22
41 matches
Mail list logo
