On Tue, Apr 22, 2014 at 11:28:42AM +1100, Winston Smith wrote:
> Just feeding in tarballs into one's own repo makes incremental
> building of one's own distribution somewhat impossible because
> the only diff one every gets is from release to release.
Postfix snapshot releases and patch releases
On 4/21/14, 8:41 PM, "/dev/rob0" wrote:
>On Mon, Apr 21, 2014 at 04:26:50PM -0400, Wietse Venema wrote:
>> I'm getting tired of questions about relayhost load balancing
>> or source IP address diffusion.
>
>I understand the feeling. However, in many cases, the people who
>want this are hurting
On Mon, Apr 21, 2014 at 04:26:50PM -0400, Wietse Venema wrote:
> I'm getting tired of questions about relayhost load balancing
> or source IP address diffusion.
I understand the feeling. However, in many cases, the people who
want this are hurting themselves or hurting others:
A. Self hurt:
1.
> For bizarre Sendmail compatibility reasons, Milters don't see the
> first header in the message. Changing that would cost me at least
> a day to ensure that it breaks nothing with "add header", "delete
> header", etc. requests.
>
> Wietse
Thanks for your prompt answer.
I'm going to test
Alexandre Ellert:
> One of the reason would be that a milter application can't see a
> header added by a policy server in the same smtpd(8) process.
> Can you tell me if that's true ?
For bizarre Sendmail compatibility reasons, Milters don't see the
first header in the message. Changing that would
Am 22.04.2014 00:42, schrieb John Griessen:
> On 04/21/2014 04:50 PM, Viktor Dukhovni wrote:
>
>>
>> This is an SMTP *client* setting, for sending mai. You almost
>> never client certs. You probably meant to set:
>>
>> # smtpd_tls_... not smtp_tls_...
>> #
>
> I changed that and whe
On 04/21/2014 04:50 PM, Viktor Dukhovni wrote:
This is an SMTP *client* setting, for sending mai. You almost
never client certs. You probably meant to set:
# smtpd_tls_... not smtp_tls_...
#
I changed that and when I test with telnet, I can get to
220 2.0.0 Ready to start TLS
T
Hello,
I have a policy server which do SPF verification at
smtpd_recipient_restrictions stage and prepend a header.
For exemple :
spf=pass (sender SPF authorized) smtp.mailfrom=gmail.com
(client-ip=209.85.128.179; helo=mail-ve0-f179.google.com;
envelope-from=[hidden]@gmail.com; receiver=[hidden]@n
On Mon, Apr 21, 2014 at 04:35:41PM -0500, John Griessen wrote:
> For now, I just want to enable TLS with clear text passwords on
> IMAP email accounts.
Postfix is not your IMAP server, that would be something like
Dovecot.
> reading http://www.postfix.org/TLS_README.html
If you really meant IMA
I got a server certificate from cacert.org, so want to have
postfix use TLS for authorizing smtp sending from my usual IP,
and later add mobile independent of IP address sending with client certificates.
For now, I just want to enable TLS with clear text passwords on IMAP email
accounts.
Follow
Wietse Venema:
> A possible solution for load balancing is to introduce a new map
> type that makes random selection.
>
> randmap:/file/name
>
> The file contains a list of reponses, one response per line,
> ignoring leading whistespace, trailing whitespace, and empty
> lines. Each m
On Mon, Apr 21, 2014 at 02:18:41PM -0400, Wietse Venema wrote:
> The following example will deliver local mail locally and load-balance
> non-local mail over smtp0: and smtp1:.
>
> /etc/postfix/main.cf:
> transport_maps = hash:/etc/postfix/transport, randmap:!smtp0:!smtp1:
One caveat is that
A possible solution for load balancing is to introduce a new map
type that makes random selection.
randmap:/file/name
The file contains a list of reponses, one response per line,
ignoring leading whistespace, trailing whitespace, and empty
lines. Each map query returns a randomly-sel
McDonald, Dan:
> On 4/21/14, 11:26 AM, "Robert Schetterer" wrote:
> >Am 21.04.2014 18:17, schrieb McDonald, Dan:
> >> Is there a simple was to create a transport map that will allow mail to
> >> be delivered round-robin to two servers? I can?t publish an externally
> >> visible MX record for the
On 4/21/14, 11:26 AM, "Robert Schetterer" wrote:
>Am 21.04.2014 18:17, schrieb McDonald, Dan:
>> Is there a simple was to create a transport map that will allow mail to
>> be delivered round-robin to two servers? I can¹t publish an externally
>> visible MX record for the two locations, and the
Am 21.04.2014 18:17, schrieb McDonald, Dan:
> Is there a simple was to create a transport map that will allow mail to
> be delivered round-robin to two servers? I can’t publish an externally
> visible MX record for the two locations, and the connections are using
> port-mapped nat on the same addr
Is there a simple was to create a transport map that will allow mail to be
delivered round-robin to two servers? I can’t publish an externally visible MX
record for the two locations, and the connections are using port-mapped nat on
the same address (e.g. 2025/tcp is one host, and 2026/tcp is a
LuKreme:
> > "Some commonly asked questions about third-party products:
> >
> > Why isn't Postfix included?
> > The license is not free, and thus can not be considered."
> >
> > Not free?
>
> That statement is a lie based on a religious position and has
> nothing at all to do with any facts. Wha
El 21/04/2014 00:54 a.m., Viktor Dukhovni escribió:
On Sun, Apr 20, 2014 at 11:11:03PM -0400, Lulu Li wrote:
I have an application that uses PHPMailer, which in turn uses
/usr/sbin/sendmail installed by Postfix.
Make sure that the application does not allow users to send email
to arbitrary re
19 matches
Mail list logo
