Scott Haneda wrote, at 04/30/2009 10:31 PM:
On Apr 24, 2009, at 9:43 PM, Jorey Bump wrote:
Since one of the purposes of the submission port is to support road
warriors, I feel it should be as secure as possible and the entire
communication should be encrypted.
I am in a bad spot in this
Scott Haneda wrote, at 04/30/2009 10:11 PM:
What happens is, under heavy MTA load on port 25, I will run out of
connection slots on port 25.
Have you investigated the nature of this problem?
By moving users to 587, I do not care
about port 25 connection slots. MTA's will try again later if
On Fri, May 01, 2009 at 10:19:40AM -0400, Jorey Bump wrote:
My end goal here is to get this all working, and then change these ports
to, for example, 25 - 2525 and 587 - 587587 unless there is some other
convention. I am going to put a anti spam proxy in front of all this.
There is no
Victor Duchovni wrote, at 05/01/2009 10:26 AM:
On Fri, May 01, 2009 at 10:19:40AM -0400, Jorey Bump wrote:
FTR: No, I didn't! :)
My end goal here is to get this all working, and then change these ports
to, for example, 25 - 2525 and 587 - 587587 unless there is some other
convention. I am
Attila Nagy a écrit :
Hello,
I have to route e-mails coming from different IP addresses to the world
(no single smarthost, the target can be anything) with different source
IPs.
So a mail coming in on 1.1.1.1 should go out with the source address of
2.2.2.2 and another coming in on
On Fri, May 01, 2009 at 01:54:03PM -0400, Eric Cunningham wrote:
I think I've found a/the fix for re-enabling the original behavior of my
transport maps and MX relaying. I added .$mydomain to mydestination in
main.cf. This is in addition to $mydomain which was already in
mydestination.
postmap -q 67.218.188
mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf
554 mta_client_reactive_b
postmap -q 67.218.188.4
mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf
... no data
man 5 access seems to make no distinction between .map and SQL tables:
HOST
-- Original Message --
From: Ralf Hildebrandt ralf.hildebra...@charite.de
Reply-To: postfix-users@postfix.org
Date: Fri, 1 May 2009 20:56:15 +0200
* Len Conrad lcon...@go2france.com:
postmap -q 67.218.188
Len Conrad wrote:
postmap -q 67.218.188
mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf
554 mta_client_reactive_b
postmap -q 67.218.188.4
mysql:/usr/local/etc/postfix/mysql-mta_clients_reactive_b.cf
... no data
man 5 access seems to make no distinction between .map and SQL
* Len Conrad lcon...@go2france.com:
1. my email client discarded my wonderful Subject: line
Your client is Imail? Their servers are crap so why should the client
be better :)
2. The problem is that a query for 67.218.188.4 is not matched by an
entry of 67.218.188. This works in hash:.map
On May 1, 2009, at 7:19 AM, Jorey Bump wrote:
Scott Haneda wrote, at 04/30/2009 10:11 PM:
What happens is, under heavy MTA load on port 25, I will run out of
connection slots on port 25.
Have you investigated the nature of this problem?
Thoroughly. My current email server lacks control, it
Scott Haneda wrote, at 05/01/2009 08:37 PM:
On May 1, 2009, at 7:19 AM, Jorey Bump wrote:
The difference is that MTAs typically don't quit if they can't verify
the cert (check it against a root certificate store), so using a
self-signed cert is adequate.
# client TLS parameters, forward
12 matches
Mail list logo
