Wietse Venema schrieb am 23.08.20 um 14:14:05 Uhr:
> > > >> with postfix version 2.11.11?
> > > >
> > > > You are running some Frankenstein Postfix, perhaps with features
> > > > backported by RHEL. Such backports are NOT part of the official
> > > > Postfix release, and are NOT SUPPORTED.
Peter schrieb am 23.08.20 um 16:10:19 Uhr:
> On 23/08/20 2:16 am, Wietse Venema wrote:
> >>
> >> with postfix version 2.11.11?
> >
> > You are running some Frankenstein Postfix, perhaps with features
> > backported by RHEL. Such backports are NOT part of the official
> > Postfix release, and a
Jaroslaw Rafa schrieb am 22.08.20 um 17:38:18 Uhr:
> Dnia 22.08.2020 o godz. 16:54:58 ratatouille pisze:
> >
> > What I don't understand at the moment is that when I send a mail
> > that contains german umlauts in the subjectline to the server in question,
>
Wietse Venema schrieb am 22.08.20 um 10:16:36 Uhr:
> > Any chance to circumvent a
> >
> > status=bounced (SMTPUTF8 is required, but was not offered by host
> > smtp.bitclusive.de[92.60.38.182])
> >
> > with postfix version 2.11.11?
>
> Postfix 2.11 has no SMTPUTF8 support.
>
> % grep -ri s
ratatouille schrieb am 22.08.20 um 14:58:46 Uhr:
> Souji Thenria schrieb am 22.08.20 um 14:46:20 Uhr:
> > have you already looked into this?
> > http://www.postfix.org/SMTPUTF8_README.html
>
> Yes and I found it is not possible to set smtputf8_enable = yes with this
Souji Thenria schrieb am 22.08.20 um 14:46:20 Uhr:
> On Sat, 22 Aug 2020 14:34:36 +0200
> ratatouille wrote:
> > Any chance to circumvent a
> >
> > status=bounced (SMTPUTF8 is required, but was not offered by host
> > smtp.bitclusive.de[92.60.38.182])
> &g
Hello!
Any chance to circumvent a
status=bounced (SMTPUTF8 is required, but was not offered by host
smtp.bitclusive.de[92.60.38.182])
with postfix version 2.11.11?
I'm setting up an onlinestore and find this in the log when a user puts an
order.
Andreas
Leonardo Rodrigues schrieb am 21.07.20 um 08:44:21
Uhr:
> Em 20/07/2020 22:44, Viktor Dukhovni escreveu:
> > If CentOS 8 requires a default floor of TLS 1.2, and have not patched
> > Postfix to relax that system-default constraint, then you're stuck
> > with TLS >= 1.2 until a suitable work-arou
Viktor Dukhovni schrieb am 19.07.20 um 17:05:02
Uhr:
> > Jul 19 22:41:37 dualbit1 postfix/smtpd[834008]: Anonymous TLS connection
> > established from p57b62c8e.dip0.t-ipconnect.de[87.182.44.142]: TLSv1.2 with
> > cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
>
> Your server supports TL
Hello!
"@lbutlr" schrieb am 19.07.20 um 06:33:10 Uhr:
> On 18 Jul 2020, at 07:25, ratatouille wrote:
> > mail_version = 3.3.1
>
> This is quite old. The current version of 3.3.x is 3.3.12.
>
> > Jul 18 14:55:12 dualbit1 postfix/smtpd[493943]:
Hello!
A problem with an android device connecting to postfix on a CentOS8 server.
mail_version = 3.3.1
I have this in the log:
Jul 18 14:55:12 dualbit1 postfix/smtpd[493943]: initializing the server-side
TLS engine
Jul 18 14:55:12 dualbit1 postfix/smtpd[493943]: connect from
p57b62c8e.dip0.t
Hello!
Matus UHLAR - fantomas schrieb am 15.07.20 um 13:28:02 Uhr:
> >The local user exists as andr...@dualbit.de. What is the problem?
>
> andr...@dualbit1.dualbit.de it different than andr...@dualbit.de
>
> either the doveco must accept dualbit1.dualbit.de same as dualbit.de or you
> need
Hello!
mail_version = 3.3.1
I am blind at the moment. I configured postfix and dovecot to deliver
via lmtp to a users local mailbox and get
Jul 15 13:14:40 dualbit1 postfix/lmtp[8901]: 173C931068B4:
to=, orig_to=,
relay=dualbit1.dualbit.de[private/dovecot-lmtp], delay=0.23,
delays=0.12/0.01/0
Hello!
Viktor Dukhovni schrieb am 05.03.20 um 18:52:55
Uhr:
> On Fri, Mar 06, 2020 at 12:26:06AM +0100, ratatouille wrote:
>
> > I have just too TLSv1 connections this month:
> > ...
> > 11 TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)
> > 9 TLSv1.2 wi
Viktor Dukhovni schrieb am 05.03.20 um 16:44:14
Uhr:
> On Thu, Mar 05, 2020 at 09:08:43PM +0100, ratatouille wrote:
>
> > Don't know why TLSv1 is still offered on our servers running
>
> Probably because you're not changing the configuration in the right
> p
Hello!
Don't know why TLSv1 is still offered on our servers running
mail_version = 2.11.3
smtpd_tls_protocols = !SSLv2, !SSLv3, !TLSv1
but a scan by ssllabs.com or with testssl.sh shows TLSv1 is still supported.
I am not sure what's wrong. What do I miss?
Other parameters I set:
smtpd_tls_CApa
Wietse Venema schrieb am 22.01.20 um 14:50:48 Uhr:
> ratatouille:
> > srw-rw-rw- 1 postfix postfix 0 22. Jan 20:24 lmtp
>
> that is not /var/spool/postfix/private/dovecot-lmtp
The problem was something, I assume webmin, modified
dovecot.conf from protocols = imap lmtp sie
Wietse Venema schrieb am 22.01.20 um 14:50:48 Uhr:
> ratatouille:
> > srw-rw-rw- 1 postfix postfix 0 22. Jan 20:24 lmtp
>
> that is not /var/spool/postfix/private/dovecot-lmtp
/var/spool/postfix/private/dovecot-lmtp is not created and I don't know
why. Just subscribed
Wietse Venema schrieb am 22.01.20 um 14:44:42 Uhr:
> > dovecot is running but it does not create doceot-lmtp. It creates lmtp
> > socket.
> >
> > service lmtp {
> > unix_listener /var/spool/postfix/private/dovecot-lmtp {
> > group = postfix
> > mode = 0600
> > user = postfix
> >
ratatouille schrieb am 22.01.20 um 20:41:25 Uhr:
> dovecot is running but it does not create doceot-lmtp. It creates lmtp socket.
>
> service lmtp {
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0600
> user = postfix
>
Daniel Armengod schrieb am 22.01.20 um 19:39:33 Uhr:
> Andreas,
>
> The creation of the listening socket is responsibility of the Dovecot
> server.
>
> Have you verified that Dovecot is up and running?
>
> The relevant setting (dovecot 10-master.conf) appears to be correct in
> the snippet y
Wietse Venema schrieb am 22.01.20 um 12:45:07 Uhr:
> ratatouille:
> > Hello all!
> >
> > Since some modifications on my testserver I have the following problem:
> > connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or
> > directory
> >
&g
Hello all!
Since some modifications on my testserver I have the following problem:
connect to smtp.amimanera.de[private/dovecot-lmtp]: No such file or directory
# fgrep -r dovecot-lmtp /etc
/etc/postfix/main.cf:mailbox_transport = lmtp:unix:private/dovecot-lmtp
/etc/dovecot/conf.d/10-master.conf:
Hello!
Mark ADAMS schrieb am 23.12.19 um 19:40:01 Uhr:
> I forgot a couple of things:
> Distro: Linux shuttle 5.4.2-desktop-1.mga7 #1 SMP Thu Dec 5 17:40:00 UTC 2019
> x86_64 x86_64 x86_64 GNU/Linux
> Postfix: postfix-3.4.5-1.mga7
> Dovecot: 2.3.7.2 (3c910f64b)
>
> I'm looking at dovecot, but
Hello!
postscreen_pipelining_enable = no
I see this in the log:
Dec 13 14:18:43 atlas postfix/postscreen[12510]: CONNECT from
[71.6.146.186]:46796 to [185.84.80.145]:25
Dec 13 14:18:43 atlas postfix/postscreen[12510]: PREGREET 137 after 0 from
[71.6.146.186]:46796:
\22\3\1\0\132\1\0\0\128\3\3
Hello all!
Received: from mail.namase.de (s1.bomberg.city [62.173.139.77])
I would like to reject incoming email if dns- and rdns-entries differ.
Does this make sense and how could I achieve this?
Kind regards
Andreas
Henrik K schrieb am 02.10.19 um 15:46:18 Uhr:
> On Wed, Oct 02, 2019 at 02:20:48PM +0200, Matus UHLAR - fantomas wrote:
> >
> > I got rid of it, since of too many false positives related to outlook, gmail
> > etc.
>
> Why would you greylist something that's easily skipped using DNSWL etc?
Tha
Ansgar Wiechers schrieb am 02.10.19 um 11:56:56 Uhr:
> On 2019-10-02 ratatouille wrote:
> > Do I really have to whitelist all the IPs of
> > outbound.protection.outlook.com in postgrey?
>
> No. You could simply stop graylisting and instead use spam protection
> m
Hello!
Do I really have to whitelist all the IPs of outbound.protection.outlook.com in
postgrey?
Oct 2 10:57:28 bitclusive1 postfix/smtpd[20061]: NOQUEUE: reject: RCPT from
mail-eopbgr680083.outbound.protection.outlook.com[40.107.68.83]: 450 4.2.0
: Recipient address rejected: Greylisted for
Wietse Venema schrieb am 28.07.19 um 15:36:02 Uhr:
> ratatouille:
> > Hi!
> >
> > May I allude the dead link http://www.porcupine.org/postfix/dos.html
> > on
> > http://www.porcupine.org/postfix/doc/overview.html and others.
> >
> > Have a
Hi!
May I allude the dead link http://www.porcupine.org/postfix/dos.html
on
http://www.porcupine.org/postfix/doc/overview.html and others.
Have a good afternoon!
Andreas
Hello!
Wietse Venema schrieb am 12.05.19 um 15:24:01 Uhr:
> ratatouille:
> > A restart of rsyslog and postfix changes nothing.
>
> You did not restart systemd, which sits in the middle between Postfix
> and rsyslogd, and which has a reputation for breaking Postfix a
Hello!
mail_version = 2.10.1
I have a serious problem with logging of postfix via rsyslog on one of my
servers
on CentOS 7.
All I see in the log is
May 12 12:41:39 nimmini1 postfix/qmgr[19227]: E16FE20EA7:
from=, size=2141, nrcpt=1 (queue active)
May 12 12:41:40 nimmini1 postfix/qmgr[19227]:
33 matches
Mail list logo
