FreeBSD-8.2 STABLE
Postfix (2.10-20120422)
OpenSSL 1.0.1a 19 Apr 2012
I just updated to the latest devel version of Postfix and openssl-1.0.1a.
Following the instructions (I think correctly) on this list, I created the
following file:
cat tls_policy
hotmail.com may protocols=!SSLv2:!TLSv1.1
Jerry:
> FreeBSD-8.2 STABLE
> Postfix (2.10-20120422)
> OpenSSL 1.0.1a 19 Apr 2012
>
> I just updated to the latest devel version of Postfix and openssl-1.0.1a.
Just to be sure, what is the output from:
$ ldd /usr/libexec/postfix/smtp
I did the Postfix testing between FreeBSD 8.2 with OpenSSL 1
On Tue, 24 Apr 2012 09:08:16 -0400 (EDT)
Wietse Venema articulated:
>Jerry:
>> FreeBSD-8.2 STABLE
>> Postfix (2.10-20120422)
>> OpenSSL 1.0.1a 19 Apr 2012
>>
>> I just updated to the latest devel version of Postfix and
>> openssl-1.0.1a.
>
>Just to be sure, what is the output from:
>
>$ ldd /usr/
- Original Message -
From: "Marko Weber"
To: "Olivier Pavilla"
Cc: "Postfix Users"
Sent: Monday, April 23, 2012 11:45 AM
Subject: Re: [SPAM] Someone is harassing my smtp.
Am 23.04.2012 06:50, schrieb Olivier Pavilla:
Hi everyone.
For several months my smtp is harassing by some
Jerry:
> $ ldd /usr/local/libexec/postfix/smtp
> /usr/local/libexec/postfix/smtp:
...
> libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800b2f000)
> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800c93000)
That looks like the right OpenSSL version.
Can you connect from the same
hi guys!
i have a content filter script that receives _only_ the body part of the
message, not the headers. i would like to use it like this:
http://www.postfix.org/FILTER_README.html
is there a simple way to pass only the body to the script?
thanks in advance,
evelio vila
On 4/24/2012 9:33 AM, Evelio VILA wrote:
> hi guys!
>
> i have a content filter script that receives _only_ the body part of the
> message, not the headers. i would like to use it like this:
>
> http://www.postfix.org/FILTER_README.html
>
> is there a simple way to pass only the body to the scri
Is it possible to put the use of a smtpd_milter into a restriction class? From
what I've read so far I'm suspect the answer is no. In which case I'll have to
put the functionality into the milter itself, MIMEDefang in my case. I'd
prefer to keep the restriction classes "centralized" if you w
On Tue, 24 Apr 2012 10:21:32 -0400 (EDT)
Wietse Venema articulated:
>Jerry:
>> $ ldd /usr/local/libexec/postfix/smtp
>> /usr/local/libexec/postfix/smtp:
>...
>> libssl.so.8 => /usr/local/lib/libssl.so.8 (0x800b2f000)
>> libcrypto.so.8 => /usr/local/lib/libcrypto.so.8 (0x800c93000)
Jerry:
> FreeBSD-8.2 STABLE
> Postfix (2.10-20120422)
> OpenSSL 1.0.1a 19 Apr 2012
>
> I just updated to the latest devel version of Postfix and openssl-1.0.1a.
>
> Following the instructions (I think correctly) on this list, I created the
> following file:
>
> cat tls_policy
> hotmail.com
On 4/24/2012 10:20 AM, Chad M Stewart wrote:
>
> Is it possible to put the use of a smtpd_milter into a restriction class?
No, the milter connection happens before postfix knows anything
about the client.
-- Noel Jones
On Tue, 24 Apr 2012 11:34:11 -0400 (EDT)
Wietse Venema articulated:
>Jerry:
>> FreeBSD-8.2 STABLE
>> Postfix (2.10-20120422)
>> OpenSSL 1.0.1a 19 Apr 2012
>>
>> I just updated to the latest devel version of Postfix and
>> openssl-1.0.1a.
>>
>> Following the instructions (I think correctly) on th
Good afternoon,
I've just been troubleshooting an issue with the php mail() function and
Postfix.
Keeping it short and to the point it appears that DKIM can be broken
because something (assuming Cleanup) changes the line endings in the
body section of the mail after it has been signed.
What I no
Jerry:
> /etc/postfix/tls_policy:
> example.com may protocols=!SSLv2:!TLSv1.1:!TLSv1.2
>
>
> I did screw it up, I left out the "v"in the "TLSv1.2" protocol name.
> However, even changing that did not make any difference.
This confirms that Postfix never found the entry in your
Sam Jones:
> Now, if I manually strip the line endings \r\n and replace them a plain
> newline \n, it works perfectly suggesting something strips the line
> endings if the are \r\n after it has been signed.
This happens when you use an old Postfix version AND have MIXED
line endings (some lines en
On Tue, Apr 24, 2012 at 12:58:29PM -0400, Wietse Venema wrote:
>
> B) Upgrade to a Postfix 2.9 or later that strips regardless.
> as described in the manpage entry below.
I'm surprised that such a basic aspect of mail processing is changing
at such a late date. What caused you to introduce this
Ben Rosengart:
> On Tue, Apr 24, 2012 at 12:58:29PM -0400, Wietse Venema wrote:
> >
> > B) Upgrade to a Postfix 2.9 or later that strips regardless.
> > as described in the manpage entry below.
>
> I'm surprised that such a basic aspect of mail processing is changing
> at such a late date. What
On Tue, 24 Apr 2012 12:51:16 -0400 (EDT)
Wietse Venema articulated:
>Jerry:
>> /etc/postfix/tls_policy:
>> example.com may protocols=!SSLv2:!TLSv1.1:!TLSv1.2
>>
>>
>> I did screw it up, I left out the "v"in the "TLSv1.2" protocol name.
>> However, even changing that did not make
On Tue, 2012-04-24 at 12:58 -0400, Wietse Venema wrote:
> Sam Jones:
> > Now, if I manually strip the line endings \r\n and replace them a plain
> > newline \n, it works perfectly suggesting something strips the line
> > endings if the are \r\n after it has been signed.
>
> This happens when you u
- Original Message -
From: "Sam Jones"
To:
Sent: Tuesday, April 24, 2012 6:23 PM
Subject: Does Cleanup (or something) change message body line endings?
Good afternoon,
I've just been troubleshooting an issue with the php mail() function and
Postfix.
Keeping it short and to the po
[An on-line version of this announcement will be available at
http://www.postfix.org/announcements/postfix-2.9.2.html]
Postfix stable release 2.9.2, and legacy releases 2.8.10, 2.7.9,
2.6.15 are available. They contains workarounds that are already
part of Postfix 2.10.
These releases add support
* Wietse Venema :
> Based on input from Victor I'll put out a 2.10 development release
> that makes the minimum changes to support the new OpenSSL protocols.
> This may then be back-ported to earlier Postfix releases if needed.
>
> Meanwhile, Victor will start work on future-proofing Postfix, such
Ralf Hildebrandt:
> @charite were suddenly encountering several domains that don't seem to
> implement STARTTLS properly.
>
> mailq exhibits the following behaviour:
>
> 3VRgn515L4zKg2v 443924 Tue Apr 10 10:01:13 sen...@charite.de
> (lost connection with mail2.trioncology.org[81.252.237.162]
On Tue, Apr 24, 2012 at 05:01:29PM -0400, Wietse Venema wrote:
> [An on-line version of this announcement will be available at
> http://www.postfix.org/announcements/postfix-2.9.2.html]
>
> Postfix stable release 2.9.2, and legacy releases 2.8.10, 2.7.9,
> 2.6.15 are available. They contains worka
The Doctor:
> gcc -Wmissing-prototypes -Wformat -DUSE_SASL_AUTH -DUSE_CYRUS_SASL -DUSE_TLS
> -I/usr/include -I/usr/contrib/include/ -I/usr/contrib/include/sasl -DHAS_PCRE
> -g -O -I. -I../../include -DBSDI4 -c tls_client.c
Are you really building Postfix on BSD/OS 4.x? I should start
trimming th
On Tue, Apr 24, 2012 at 08:21:05PM -0400, Wietse Venema wrote:
> The Doctor:
> > gcc -Wmissing-prototypes -Wformat -DUSE_SASL_AUTH -DUSE_CYRUS_SASL
> > -DUSE_TLS -I/usr/include -I/usr/contrib/include/
> > -I/usr/contrib/include/sasl -DHAS_PCRE -g -O -I. -I../../include -DBSDI4 -c
> > tls_client.
Hi,
I have a few postfix-2.8.7 systems on fedora15 that connect with
another postfix-2.8.7 system. I'm receiving the following messages
periodically in the logs:
Apr 24 16:24:43 mailrelay postfix/smtpd[8814]: timeout after DATA
(9832 bytes) from mail02.example.com[68.XXX.YYY.45]
Apr 24 16:24:43 m
The Doctor:
> On Tue, Apr 24, 2012 at 08:21:05PM -0400, Wietse Venema wrote:
> > The Doctor:
> > > gcc -Wmissing-prototypes -Wformat -DUSE_SASL_AUTH -DUSE_CYRUS_SASL
> > > -DUSE_TLS -I/usr/include -I/usr/contrib/include/
> > > -I/usr/contrib/include/sasl -DHAS_PCRE -g -O -I. -I../../include -DBSD
Alex:
[ Charset ISO-8859-1 unsupported, converting... ]
> Hi,
>
> I have a few postfix-2.8.7 systems on fedora15 that connect with
> another postfix-2.8.7 system. I'm receiving the following messages
> periodically in the logs:
>
> Apr 24 16:24:43 mailrelay postfix/smtpd[8814]: timeout after DATA
On Tue, Apr 24, 2012 at 08:59:53PM -0400, Wietse Venema wrote:
> The Doctor:
> > On Tue, Apr 24, 2012 at 08:21:05PM -0400, Wietse Venema wrote:
> > > The Doctor:
> > > > gcc -Wmissing-prototypes -Wformat -DUSE_SASL_AUTH -DUSE_CYRUS_SASL
> > > > -DUSE_TLS -I/usr/include -I/usr/contrib/include/
> >
Hi,
>> I have a few postfix-2.8.7 systems on fedora15 that connect with
>> another postfix-2.8.7 system. I'm receiving the following messages
>> periodically in the logs:
>>
>> Apr 24 16:24:43 mailrelay postfix/smtpd[8814]: timeout after DATA
>> (9832 bytes) from mail02.example.com[68.XXX.YYY.45]
31 matches
Mail list logo