>X-Assp-Re-invalidFormatHeloRe: PB 10: for 177.0.210.234
>X-Assp-Message-Score: 10 (invalid HELO: '177.0.210.234')
>X-Assp-IP-Score: 10 (invalid HELO: '177.0.210.234')
>X-Assp-Re-invalidPTRRe: PB 15: for 4736251289
>X-Assp-Message-Score: 15 (PTR invalid
'4736251289.e.brasiltelecom.net.br')
On 18/12/15 07:11, Thomas Eckardt wrote:
> If the envelope sender is empty, assp detects a bounce mail.
>
>
Is there a way to stop this being used as a way in for SPAM ?
--
___
Thomas Eckardt wrote:
> Doug, please upgrade IO::Socket::SSL to the latest version (possibly also
> Net::SSLeay) and tryout the latest assp v2 dev build.
> Tell me if the issue (timeouts) is gone.
Thanks Thomas,
I'm on vacation starting Monday and will put those into place and let
you know.
Hi,
I upgraded to perl v5.22.1 via pacman (ArchLinux) and restartet ASSP. I tried
to send a mail containing the subject "test" and the body "test". At my gmail
account I received the mail without subject and the following body: (I replaced
the domain and names)
\C is deprecated in regex;
I found some time this AM to upgrade our work ASSP:
ASSP version 2.4.6(15351)
IO::Socket::SSL 2.022 / 2.020
Net::SSLeay 1.72 / 1.72
I've had 30 timeouts in the last hour
I'm planning on doing a TCP dump on my home mail server this upcoming Monday
(running Zimbra at work
You've set the hidden config variable '$DKIMconvHTML2base64' to the not
default value 1.
This causes a regex mistake to come up.
in sub DKIMgen_Run look for the line (assp.pl line 28304)
if($DKIMconvHTML2base64 && $this->{header}=~
/\015\012\Content-Type:\s*text\/(?:ht|x)ml/sio) {
and
>>> On Dec 18, 2015, at 8:22 AM, Thomas Eckardt thomas.ecka...@thockar.com
>>> wrote:
>>>I've had 30 timeouts in the last hour
bad news! Thank you for testing.
Postfix manual for TLS logging gives:
Server-side TLS activity logging
To get additional information about Postfix SMTP server
>I've had 30 timeouts in the last hour
bad news! Thank you for testing.
Your debug output has shown, that IO::Socket::SSL (Net::SSLeay) has
returned, that all data were written to the socket. The Net::SSLeay has to
encrypt (SSL) all data and has to write the SSL-data to the system socket.
>Would setting it to 2, 3 or even 4 be of help?
At least 3 would be required. So we can see, if there is a renegotiating
problem.
Thomas
Von:Doug Lytle
An: ASSP development mailing list
Datum: 18.12.2015 14:57
Betreff: