On 03/13/2012 09:00 PM, Wietse Venema wrote:
I don't know what the consequences would be: can a v2 client talk
to a v3 server? What about a v3 client and a v2 server?
Mine answer would be:
+---+---+---+
| | v2 client | v3 client |
On 2012-03-12 12:18 PM, Viktor Dukhovni postfix-us...@dukhovni.org wrote:
On Mon, Mar 12, 2012 at 12:10:30PM -0400, Charles Marcus wrote:
relay=outbounds6.obsmtp.com[64.18.5.12]:25, delay=1,
delays=0.65/0.01/0.27/0.07, dsn=5.0.0, status=bounced (host
outbounds6.obsmtp.com[64.18.5.12] said: 518
On 3/14/2012 6:38 AM, Charles Marcus wrote:
On 2012-03-12 12:18 PM, Viktor Dukhovni postfix-us...@dukhovni.org wrote:
On Mon, Mar 12, 2012 at 12:10:30PM -0400, Charles Marcus wrote:
relay=outbounds6.obsmtp.com[64.18.5.12]:25, delay=1,
delays=0.65/0.01/0.27/0.07, dsn=5.0.0, status=bounced (host
On 2012-03-14 9:07 AM, Stan Hoeppner s...@hardwarefreak.com wrote:
On 3/14/2012 6:38 AM, Charles Marcus wrote:
It turns out it is simply that when you are using postini, and use them
for outbound relay/filtering as well, they expect the 'From' address to
be from our domain... this is just
Am 14.03.2012 14:42, schrieb Charles Marcus:
The real question is: Why are you bothering to use Postini for outbound
delivery, given these problems, instead of continuing to send direct to MX?
Biggest reason is, if I don't relay outbound mail through postini, we lose
the
On 2012-03-14 10:16 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 14.03.2012 14:42, schrieb Charles Marcus:
The real question is: Why are you bothering to use Postini for outbound
delivery, given these problems, instead of continuing to send direct to MX?
Biggest reason is, if I don't
Example to send forwarded mail direct to MX.
/etc/postfix/main.cf:
relayhost =
sender_dependent_relayhost_maps = pcre:/etc/postfix/relayhost_maps
/etc/postfix/relayhost_maps:
# Local domain(s) below.
/[@.]example\.com$/ postini
Another possibility may be
On 2012-03-14 10:55 AM, Wietse Venema wie...@porcupine.org wrote:
Example to send forwarded mail direct to MX.
/etc/postfix/main.cf:
relayhost =
sender_dependent_relayhost_maps = pcre:/etc/postfix/relayhost_maps
/etc/postfix/relayhost_maps:
# Local domain(s) below.
Hi Folks,
I'm currently running a pretty basic high-availability configuration for
our mail server (postfix) - it simply runs in a Xen virtual machine,
with mirrored disks across two machines (DRBD), and failover of the VM
if something goes wrong (pacemaker).
I'm thinking about migrating
--
Erwan Loaec
Ingénieur Systèmes Réseaux
CGIN - Compagnie Générale d'Imagerie Numérique
55 route Jean BRIAUD
33693 MERIGNAC CEDEX - FRANCE
Tél : +33 (5) 57 89 03 06
Fax : +33 (5) 57 89 03 01
Sorry for the last mail... It was a mistake between the chair and
keyboard...
On Thu, Mar 8, 2012 at 4:06 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
How much traffic can postscreen handle? Each mail server in our
cluster handles 800,000 to 1,000,000 messages per day. We typically
This is mainly limited by the whitelist database latency: the
time
On 13/03/2012 23:50, Wietse Venema wrote:
#submission inet n - n - - smtpd
# -o syslog_name=postfix/submission
# -o smtpd_tls_security_level=encrypt
I forget the exact details now, but one mail client, I think it might be
an Android or iPhone mail client(?)
On 2012-03-14 2:39 PM, Ed W li...@wildgooses.com wrote:
I see no reason to *require* encryption on the submission port (RFC
aside).
Unless you prefer that sniffers not be able to see your passwords
crossing the wire in plaintext?
I think may is a more appropriate default?
Disagree
Dan Lists:
On Thu, Mar 8, 2012 at 4:06 PM, Wietse Venema wie...@porcupine.org wrote:
Dan Lists:
How much traffic can postscreen handle? ? Each mail server in our
cluster handles 800,000 to 1,000,000 messages per day. ?We typically
This is mainly limited by the whitelist database
Ed W:
On 13/03/2012 23:50, Wietse Venema wrote:
#submission inet n - n - - smtpd
# -o syslog_name=postfix/submission
# -o smtpd_tls_security_level=encrypt
I forget the exact details now, but one mail client, I think it might be
an Android or iPhone mail
Wietse Venema:
Ed W:
On 13/03/2012 23:50, Wietse Venema wrote:
#submission inet n - n - - smtpd
# -o syslog_name=postfix/submission
# -o smtpd_tls_security_level=encrypt
I forget the exact details now, but one mail client, I think it might be
an
* Charles Marcus cmar...@media-brokers.com:
On 2012-03-14 2:39 PM, Ed W li...@wildgooses.com wrote:
I see no reason to *require* encryption on the submission port (RFC
aside).
Unless you prefer that sniffers not be able to see your passwords
crossing the wire in plaintext?
I think may is
* Wietse Venema postfix-users@postfix.org:
Wietse Venema:
Ed W:
On 13/03/2012 23:50, Wietse Venema wrote:
#submission inet n - n - - smtpd
# -o syslog_name=postfix/submission
# -o smtpd_tls_security_level=encrypt
I forget the exact details
Patrick Ben Koetter:
That's not a problem for me. I don't use the submission service
and rely on input from the real world for this.
Meaning, may, combined with a setting that allows plaintext
passwords only over encrypted connections. Not sure if that makes
trouble shooting easier
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
That's not a problem for me. I don't use the submission service
and rely on input from the real world for this.
Meaning, may, combined with a setting that allows plaintext
passwords only over encrypted connections.
On 3/14/2012 4:50 PM, Patrick Ben Koetter wrote:
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
That's not a problem for me. I don't use the submission service
and rely on input from the real world for this.
Meaning, may, combined with a setting that allows plaintext
* Noel Jones postfix-users@postfix.org:
On 3/14/2012 4:50 PM, Patrick Ben Koetter wrote:
* Wietse Venema postfix-users@postfix.org:
Patrick Ben Koetter:
That's not a problem for me. I don't use the submission service
and rely on input from the real world for this.
Meaning, may,
What is the best Perl interface for milters? I found several:
Sendmail::Milter is way old, and demands -Dusethreads -- my perl is
built with -Duseithreads.
Sendmail::Pmilter is recent, but lacks a maintainer. No traffic on
its mailing list since 2009.
Then there's
- Цитат от Ben Rosengart (ben.roseng...@morganstanley.com), на 15.03.2012 в
00:34 -
What is the best Perl interface for milters? I found several:
Sendmail::Milter is way old, and demands -Dusethreads -- my perl is
built with -Duseithreads.
Sendmail::Pmilter is recent, but
On Thu, Mar 15, 2012 at 12:53:56AM +0200, karave...@mail.bg wrote:
- ?? Ben Rosengart (ben.roseng...@morganstanley.com),
15.03.2012 ?? 00:34 -
What is the best Perl interface for milters?
Why use milter interface? There are other ways to extend postfix that I
On 03/14/2012 04:03 PM, Patrick Ben Koetter wrote:
* Charles Marcuscmar...@media-brokers.com:
On 2012-03-14 2:39 PM, Ed Wli...@wildgooses.com wrote:
I see no reason to *require* encryption on the submission port (RFC
aside).
Unless you prefer that sniffers not be able to see your passwords
- Цитат от Ben Rosengart (ben.roseng...@morganstanley.com), на 15.03.2012 в
01:14 -
On Thu, Mar 15, 2012 at 12:53:56AM +0200, karave...@mail.bg wrote:
- ?? Ben Rosengart (ben.roseng...@morganstanley.com),
15.03.2012 ?? 00:34 -
What is the best Perl
On 13/3/2012 7:58 μμ, Nikolaos Milas wrote:
As far as I know, most people creating RHEL Postfix RPMs are using S.
J. Mudd's src.rpm but I don't know if someone has extended the
included spec files to support custom LDAP paths.
I have been able to use S. J. Mudd's src.rpm to build RPM packages
On Thu, 2012-03-15 at 01:45:43 +0200, Nikolaos Milas wrote:
...
%if %{with_ldap}
CCARGS=${CCARGS} -DHAS_LDAP -I/usr/local/openldap/include
AUXLIBS=${AUXLIBS} -L/usr/local/openldap/lib -lldap -llber
%endif
...
However, I see that at the end of the build process, the
On 15/3/2012 1:54 πμ, Sahil Tandon wrote:
/usr/local/openldap/lib != /usr/local/openldap/lib64
I know; I am wondering whether this is the problem.
I think that the build process uses 64 bit libs correctly when needed
and produces automatically both 32 bit and 64 bit RPMs if the required
On Wed, Mar 14, 2012 at 2:09 PM, Wietse Venema wie...@porcupine.org wrote:
I assume you are referring to the temporary whitelist. I do not see
any way to configure what is uses to store the temporary whitelist.
Is it configurable? Is there any way to share the temp whitelist
between
Hi,
In ee2234180768aa5bb7cd9a8954d69dd5.mai...@mail.bg
Re: Perl milters? on Thu, 15 Mar 2012 01:30:40 +0200,
karave...@mail.bg wrote:
Another
consideration was that I do not know how to test milters without running
full
Dan Lists:
On Wed, Mar 14, 2012 at 2:09 PM, Wietse Venema wie...@porcupine.org wrote:
I assume you are referring to the temporary whitelist. ?I do not see
any way to configure what is uses to store the temporary whitelist.
Is it configurable? ? Is there any way to share the temp whitelist
On 3/14/2012 5:09 PM, Patrick Ben Koetter wrote:
* Noel Jones postfix-users@postfix.org:
AFAIK OpenSSL works OK for testing SMTP as long as you avoid
sending/pressing the upper-case R character, which triggers TLS
renegotiation (and an SMTP error). Issuing the SMTP commands in
lower-case is
On Wed, Mar 14, 2012 at 10:49 AM, Miles Fidelman
mfidel...@meetinghouse.net wrote:
Hi Folks,
Hi.
I'm currently running a pretty basic high-availability configuration for our
mail server (postfix) - it simply runs in a Xen virtual machine, with
mirrored disks across two machines (DRBD), and
36 matches
Mail list logo
