Hi, I have more info and I try to explain it better:
First of all I have smtputf8_enable = no (disabled).
I have several databases related with several mysql_virtual maps:
- Some with utf8 + utf8_general_ci collation
- Another ones with latin1 + latin1_spanish_ci.
I'm using mysql-postfix
> Wietse Venema via Postfix-users :
>
> Jaroslaw Rafa via Postfix-users:
>> Dnia 16.04.2023 o godz. 16:32:41 Gerald Galster via Postfix-users pisze:
>>>
>>> Mails classified as spam or external forwards seemingly take another route
>>> via mout-xforward.web.de. These servers are SBL-listed by
Jaroslaw Rafa via Postfix-users:
> Dnia 16.04.2023 o godz. 16:32:41 Gerald Galster via Postfix-users pisze:
> >
> > Mails classified as spam or external forwards seemingly take another route
> > via mout-xforward.web.de. These servers are SBL-listed by intention, most
> > likely because the spam
It appears that Jaroslaw Rafa via Postfix-users said:
>Dnia 16.04.2023 o godz. 16:32:41 Gerald Galster via Postfix-users pisze:
>>
>> Mails classified as spam or external forwards seemingly take another route
>> via mout-xforward.web.de. These servers are SBL-listed by intention, most
>> likely
Dnia 16.04.2023 o godz. 16:32:41 Gerald Galster via Postfix-users pisze:
>
> Mails classified as spam or external forwards seemingly take another route
> via mout-xforward.web.de. These servers are SBL-listed by intention, most
> likely because the spam probability is higher in this context. This
Dear Viktor,
I'm is an old grandfather, and I'm already not thinking straight in Linux and
I'm confused about these adjustments.
But I very need to get this stubborn and also old Videocam to work :-)
You have already helped me a lot in solving this problem, for which I thank you
very much!
If
On Sun, Apr 16, 2023 at 10:05:02PM +0300, Oleksandr wrote:
> > You now need to again post your configuration settings. Post the output
> > of:
> >
># postconf -nf smtpd_tls_cert_file smtpd_tls_key_file smtpd_tls_chain_files
># ls -l $(postconf -xh smtpd_tls_cert_file smtpd_tls_key_file
> You now need to again post your configuration settings. Post the output
> of:
>
# postconf -nf smtpd_tls_cert_file smtpd_tls_key_file smtpd_tls_chain_files
# ls -l $(postconf -xh smtpd_tls_cert_file smtpd_tls_key_file
smtpd_tls_chain_files)
# grep -E '^-(BEGIN|END) ' $(postconf
On Sun, Apr 16, 2023 at 09:24:09PM +0300, Oleksandr wrote:
> I think I've followed all your instructions, and now I've got another
> mistake:
That means that either my instructions had a typo, or your
implementation of correct instructions had a typo.
> Apr 16 21:20:29 mailserver
I think I've followed all your instructions, and now I've got another mistake:
Apr 16 21:20:29 mailserver postfix/smtps/smtpd[2496]: warning: No server certs
available. TLS won't be enabled
Apr 16 21:20:30 mailserver postfix/smtps/smtpd[2496]: connect from
unknown[192.168.8.144]
Apr 16 21:20:30
On Sun, Apr 16, 2023 at 07:49:00PM +0300, Oleksandr wrote:
> > Did you reconfigure Postfix to use the generated PEM file
> > as your certificate and private key file?
>
> I didn't know it had to be done... I just do what you recommend. How
> do I need to do this reconfiguration? Please tell
> Did you reconfigure Postfix to use the generated PEM file
> as your certificate and private key file?
I didn't know it had to be done...
I just do what you recommend.
How do I need to do this reconfiguration?
Please tell me about this in more detail.
And another question: do these commands
On Sun, Apr 16, 2023 at 06:03:09PM +0300, Oleksandr via Postfix-users wrote:
> Okay, Viktor! I executed these commands and got this result:
>
> $ dnsname=mailserver.mail.lan
> $ rm certkey.pem
> rm: Unable to delete 'certkey.pem': No such file or directory
> user@mailserver:~$ openssl req -new
Okay, Viktor! I executed these commands and got this result:
$ dnsname=mailserver.mail.lan
$ rm certkey.pem
rm: Unable to delete 'certkey.pem': No such file or directory
user@mailserver:~$ openssl req -new -nodes -newkey rsa:2048 -keyout /dev/stdout
\
-config <(printf
> John Levine via Postfix-users :
> [...]
> If you are a customer, what happened when you contacted them through
> their customer support channels and asekd for the support you are
> paying for?
Web.de is a german freemail provider like gmail.
They might provide support for paid accounts only.
> one of web.de's sender IPs is listed into zen.spamhaus.org as the following
> info.
>
> 554 5.7.1 Service unavailable; Client host [82.165.159.35] blocked using z
> en.spamhaus.org; https://www.spamhaus.org/sbl/query/SBL175032
Try to send your email via web.de (browser), which might use
It appears that tom--- via Postfix-users said:
>$ dig -x 82.165.159.35 +short
>mout-xforward.web.de.
>
>Can anyone from web.de help with this?
The only people who should be able to send mail through that server are web.de
customers.
If you are a customer, what happened when you contacted them
On 16/04/2023 05:57, tom--- via Postfix-users wrote:
> Intentionally at the request of web.de it seems. Did you read:
>>
>> https://www.spamhaus.org/sbl/query/SBL175032
>>
>> If your message was blocked, and was not spam, contact:
>>
>> https://postmaster.web.de/en/case?c=uar
>
> I sent
18 matches
Mail list logo
