Re: Sharing a domain with Exchange

Viktor, Thanks so much! I will digest and rework! Thanks again!! Sent from my iPhone > On May 5, 2017, at 7:23 PM, Viktor Dukhovni > wrote: > > >> On May 5, 2017, at 5:21 PM, John Anderson >> wrote: >> >> My first post to a mailing list, I am sure this is a simple thing that I am >> overloo

Re: Different LMTP configuration for different clients

On 04/05/17 18:13, Angel L. Mateo wrote: > My problem is that I can't classify by recipient. I should do it by > client IP. Is this possible in a transport map? No, instead use smtpd_client_restrictions with check_client_access and a FILTER result pointing to the correct transport. See postco

Re: Sharing a domain with Exchange

> On May 5, 2017, at 5:21 PM, John Anderson wrote: > > My first post to a mailing list, I am sure this is a simple thing that I am > overlooking, but even a two week old case with RHEL and I am not hitting on > the answer. Please help if you can/want. > > Situation: > Single postfix server an

Sharing a domain with Exchange

Greetings, My first post to a mailing list, I am sure this is a simple thing that I am overlooking, but even a two week old case with RHEL and I am not hitting on the answer. Please help if you can/want. Situation: Single postfix server and an exchange 2013 server. The company is wanting to

Re: Very strange DNS Problem; MX not found

On 05.05.2017 at 14:48h Georg Sotsas wrote: The mails sent to .x...@guilford.com remain in the queue with this error: Host or domain name not found. Name service error for name=guilford.com type=MX: Host not found, try again Just workin

Re: Very strange DNS Problem; MX not found

Viktor Dukhovni: > > > On May 5, 2017, at 11:31 AM, Wietse Venema wrote: > > > > I would not exclude the possibility that the OP is using a greedy > > resolver that tries to look up A records when asked for MX, and > > then reports an MX lookup problem when it was actually the A query > > that f

Re: Very strange DNS Problem; MX not found

> On May 5, 2017, at 11:31 AM, Wietse Venema wrote: > > I would not exclude the possibility that the OP is using a greedy > resolver that tries to look up A records when asked for MX, and > then reports an MX lookup problem when it was actually the A query > that failed because of the large resp

Re: Very strange DNS Problem; MX not found

Viktor Dukhovni: > > > On May 5, 2017, at 8:48 AM, Georg Sotsas wrote: > > > > The mails sent to .x...@guilford.com remain in the queue with this > > error: > > Host or domain name not found. Name service error for name=guilford.com > > type=MX: Host not found, try again > > This sounds

Re: Message-ID: / In-Reply-To: ID continuity through mail servers

> On May 5, 2017, at 8:16 AM, Richard Sass wrote: > > For a simple example using Postfix and our application as the client sending > will the “Message-ID:” outbound from my application message be retained as > it passes through Postfix, unaltered arriving at the destination mailbox on > the same

Re: TLS security rules - perfect setup and issue with anonymous cipher

> On May 5, 2017, at 7:07 AM, Zalezny Niezalezny > wrote: > > I have a security question. My Postfix 2.10.1 Postfix 3.2, 3.1, 3.0 and 2.11 are all available. http://cdn.postfix.johnriley.me/mirrors/postfix-release/index.html while Postfix 2.10 is no longer supported. If you want to keep

Re: Very strange DNS Problem; MX not found

> On May 5, 2017, at 8:48 AM, Georg Sotsas wrote: > > The mails sent to .x...@guilford.com remain in the queue with this error: > Host or domain name not found. Name service error for name=guilford.com > type=MX: Host not found, try again This sounds like an error with *outbound* mail, pl

Re: Very strange DNS Problem; MX not found

Georg Sotsas: > Hello, > we are encountering a very strange problem on our Postfix (2.11.0-1ubuntu1) > Mail Relay. > > The mails sent to .x...@guilford.com remain in the queue with this > error: > Host or domain name not found. Name service error for name=guilford.com > type=MX: Host not found

Re: Message-ID: / In-Reply-To: ID continuity through mail servers

I suggest that you build on conventions that are valid across multiple mail software implementations, not just Postfix. Of particular interest are In-Reply-To: and References:. Search the web for "site:ietf.org references in-reply-to", and read the documents that come up, in particular RFC 2822 a

Advice on spam & virus checking (again)

I’m currently running postfix, dovecot and mailman on a Ubuntu 16.04 server, to which a number of domains resolve. There is a mailman list associated with one of the domains. The volumes are very low. After some adventures I got spamassassin running, but my attempts to run clamav, either through

Very strange DNS Problem; MX not found

Hello, we are encountering a very strange problem on our Postfix (2.11.0-1ubuntu1) Mail Relay. The mails sent to .x...@guilford.com remain in the queue with this error: Host or domain name not found. Name service error for name=guilford.com type=MX: Host not found, try again The DNS resolutio

Message-ID: / In-Reply-To: ID continuity through mail servers

We have a project to write an automated email client which is required to link reply messages sent back in response to its original message, what is the best method to provide this linkage? I am using Postfix (2.11) as my test bed. For a simple example using Postfix and our application as the clie

TLS security rules - perfect setup and issue with anonymous cipher

Hi, first of all I would like to say "thank You" for the answers on my previous questions. I read all of them, they were helpful but I missed to say "BIG THANKS!" I have a security question. My Postfix 2.10.1 Server TLS configuration looks like this at the moment. #TLS Server configuration smt