tls_policy_maps as mysql table

2014-11-19 Thread Patrik Båt
Hello! How do I return the data? for now I've tried: hostname/next-hop option (returning just one field with a space in-between) hostname/next-hop,option (returning 2 fields) Tried with a regular hash file and that works, returning the some data end me up with this warning: Nov 19 13:18:08

Re: tls_policy_maps as mysql table

2014-11-19 Thread Patrik Båt
On 2014-11-19 13:54, Patrik Båt wrote: Hello! How do I return the data? for now I've tried: hostname/next-hop option (returning just one field with a space in-between) hostname/next-hop,option (returning 2 fields) Tried with a regular hash file and that works, returning the some data end

Re: tls_policy_maps as mysql table

2014-11-19 Thread Patrik Båt
Btw, Vi vill ha deliverystatus som visar encrypted or not va ? On 2014-11-19 14:06, Patrik Båt wrote: On 2014-11-19 13:54, Patrik Båt wrote: Hello! How do I return the data? for now I've tried: hostname/next-hop option (returning just one field with a space in-between)

Re: tls_policy_maps as mysql table

2014-11-19 Thread Patrik Båt
On 2014-11-19 14:35, Patrik Båt wrote: Btw, Vi vill ha deliverystatus som visar encrypted or not va ? On 2014-11-19 14:06, Patrik Båt wrote: On 2014-11-19 13:54, Patrik Båt wrote: Hello! How do I return the data? for now I've tried: hostname/next-hop option (returning just one field with

Re: restrict or alter to address based on from address

2014-11-19 Thread Mikael Bak
Hi, On 11/19/2014 03:27 AM, Joe Acquisto-j4 wrote: [snip] I was daydreaming about ways to get messages from the old system to the new one, as might be required. For a bit it seemed feasible to cobble up something to allow messages to be sent via SMTP from the old system to the new, in a

Re: tls_policy_maps as mysql table

2014-11-19 Thread Wietse Venema
Patrik B?t: Hello! How do I return the data? Same format as a hash: based table lookup result. That is: postmap -q query-string hash:/path/to/file should return the same result as: postmap -q query-string mysql:path/to/file Wietse

virtual_transport = lmtp:imaphost:24 - host not found

2014-11-19 Thread Sascha Hüdepohl
Hi, i'm having trouble with: virtual_transport = lmtp:imaphost:24 I get an error like: Nov 19 15:30:24 kite postfix/lmtp[612]: 1C11B49: to=o...@hier.de, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=imaphost

Re: virtual_transport = lmtp:imaphost:24 - host not found

2014-11-19 Thread li...@rhsoft.net
Am 19.11.2014 um 15:45 schrieb Sascha Hüdepohl: virtual_transport = lmtp:imaphost:24 I get an error like: Nov 19 15:30:24 kite postfix/lmtp[612]: 1C11B49: to=o...@hier.de, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error

Reverse path in MAIL FROM: consisting of multiple addresses (source routes?)

2014-11-19 Thread Arrigo Marchiori
Hello list, I am using Postfix 2.10.3 as home e-mail gateway: messages are delivered by fetchmail and passed to Postfix via SMTP on the same host. Today I received an e-mail that had two addresses in the From: field. Postfix consistently rejected it. I went to see the transcript of the SMTP

Re: Reverse path in MAIL FROM: consisting of multiple addresses (source routes?)

2014-11-19 Thread Claus Assmann
On Wed, Nov 19, 2014, Arrigo Marchiori wrote: MAIL FROM:two@localhost,users@localhost 501 5.1.7 Bad sender address syntax MAIL FROM:reverse-path [SP mail-parameters ] CRLF The use of source routes is deprecated; while servers MUST be From the above, I understand that the e-mail is

Re: virtual_transport = lmtp:imaphost:24 - host not found

2014-11-19 Thread Sascha Hüdepohl
* li...@rhsoft.net (li...@rhsoft.net) schrieb: in case of transports postfix don't care about your /etc/hosts and makes DNS requests, Feeling dumb now. Because i turned verbose on for lmtp and saw postfix/lmtp[521]: dns_query: imaphost (A): Host not found in the logs. I didn't realize it

Re: Reverse path in MAIL FROM: consisting of multiple addresses (source routes?)

2014-11-19 Thread Wietse Venema
Arrigo Marchiori: Example 2: (error) 220 myhost ESMTP Postfix MAIL FROM:two@localhost,users@localhost 501 5.1.7 Bad sender address syntax This IS NOT source routing. That looks like @domain,@domain:user@domain, and your MAIL FROM command does not. RFC 5321: Reverse-path = Path /

Re: tls_policy_maps as mysql table

2014-11-19 Thread Patrik Båt
On 2014-11-19 15:12, Wietse Venema wrote: Patrik B?t: Hello! How do I return the data? Same format as a hash: based table lookup result. That is: postmap -q query-string hash:/path/to/file should return the same result as: postmap -q query-string mysql:path/to/file Wietse Yes

Re: virtual_transport = lmtp:imaphost:24 - host not found

2014-11-19 Thread li...@rhsoft.net
Am 19.11.2014 um 16:11 schrieb Sascha Hüdepohl: * li...@rhsoft.net (li...@rhsoft.net) schrieb: in case of transports postfix don't care about your /etc/hosts and makes DNS requests, Feeling dumb now. Because i turned verbose on for lmtp and saw postfix/lmtp[521]: dns_query: imaphost (A):

Re: Reverse path in MAIL FROM: consisting of multiple addresses (source routes?)

2014-11-19 Thread Arrigo Marchiori
On Wed, Nov 19, 2014 at 10:16:02AM -0500, Wietse Venema wrote: Arrigo Marchiori: Example 2: (error) 220 myhost ESMTP Postfix MAIL FROM:two@localhost,users@localhost 501 5.1.7 Bad sender address syntax This IS NOT source routing. That looks like @domain,@domain:user@domain, and your

BCC action in header/body_checks

2014-11-19 Thread Wietse Venema
Postfix snapshot 20141119 adds support for BCC actions in header/body_checks and milter_header_checks. There is no limit on the number of BCC actions that may be specified, other than the implicit limit due to finite storage. BCC support will not be implemented in Postfix delivery agents

sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
When implementing sender login maps, we've run into an issue where people cannot send out email using a from address of the alias domain. We store all of the data in LDAP, but I'm not coming up with a good resolution on a lookup query that will handle this. Thoughts appreciated. The general

Re: sender login maps and alias domains

2014-11-19 Thread Viktor Dukhovni
On Wed, Nov 19, 2014 at 01:31:59PM -0800, Quanah Gibson-Mount wrote: server_host = ldap://zre-ldap003.eng.zimbra.com:389 server_port = 389 search_base = query_filter =

Re: sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
--On November 19, 2014 at 9:39:26 PM + Viktor Dukhovni postfix-us...@dukhovni.org wrote: For each user list all their mail addresses as additional values of a suitable multi-valued attribute that holds the users various valid email addresses. For example, Microsoft Exchange stores:

Re: sender login maps and alias domains

2014-11-19 Thread Wietse Venema
Quanah Gibson-Mount: When implementing sender login maps, we've run into an issue where people cannot send out email using a from address of the alias domain. We store Postfix alias expansion happens after the sender authorization check. At the risk of asking an obvious question: have you

Re: sender login maps and alias domains

2014-11-19 Thread li...@rhsoft.net
Am 19.11.2014 um 22:57 schrieb Quanah Gibson-Mount: --On November 19, 2014 at 9:39:26 PM + Viktor Dukhovni postfix-us...@dukhovni.org wrote: For each user list all their mail addresses as additional values of a suitable multi-valued attribute that holds the users various valid email

Re: sender login maps and alias domains

2014-11-19 Thread Viktor Dukhovni
On Wed, Nov 19, 2014 at 01:57:48PM -0800, Quanah Gibson-Mount wrote: For each user list all their mail addresses as additional values of a suitable multi-valued attribute that holds the users various valid email addresses. For example, Microsoft Exchange stores: For sites with 10 million +

Re: sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
--On November 19, 2014 at 11:02:05 PM +0100 li...@rhsoft.net wrote: in case of such sites you have *databases* used directly for MTA queries or generate config files from databases LDAP is a database. It already contains all of the necessary data to get the work done. What's missing is

Re: sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
--On November 19, 2014 at 10:04:07 PM + Viktor Dukhovni postfix-us...@dukhovni.org wrote: Avoiding wildcards gives you the opportunity to not burden every user with legacy domain names just because some users need them. Who said anything about legacy domain names? Sorry, the login

Re: sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
--On November 19, 2014 at 4:57:50 PM -0500 Wietse Venema wie...@porcupine.org wrote: Alias expansions are one-to-many, and alias expansions are recursive. Suppose that foo is aliased to bar and baz. When a client sends mail from foo, the Postfix SMTP server does not know what addresses foo

Re: sender login maps and alias domains

2014-11-19 Thread Viktor Dukhovni
On Wed, Nov 19, 2014 at 03:06:07PM -0800, Quanah Gibson-Mount wrote: in case of such sites you have *databases* used directly for MTA queries or generate config files from databases LDAP is a database. It already contains all of the necessary data to get the work done. What's missing is

Re: sender login maps and alias domains

2014-11-19 Thread Viktor Dukhovni
On Wed, Nov 19, 2014 at 03:07:19PM -0800, Quanah Gibson-Mount wrote: Sorry, the login table lookup must handle the original address as the lookup key via a single query. And clearly postfix is already designed in some cases to do multiple queries based on the results of previous queries.

Re: sender login maps and alias domains

2014-11-19 Thread Quanah Gibson-Mount
--On November 19, 2014 at 11:14:49 PM + Viktor Dukhovni postfix-us...@dukhovni.org wrote: On Wed, Nov 19, 2014 at 03:07:19PM -0800, Quanah Gibson-Mount wrote: Sorry, the login table lookup must handle the original address as the lookup key via a single query. And clearly postfix is

google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Robert Moskowitz
Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and sent many an email to the cubieboard list. Just today I finally upgraded my mailserver, but still get the bounce. My

Re: google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Mark Martinec
Robert Moskowitz wrote: Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and sent many an email to the cubieboard list. Just today I finally upgraded my mailserver, but still

Re: sender login maps and alias domains

2014-11-19 Thread Wietse Venema
Viktor Dukhovni: On Wed, Nov 19, 2014 at 03:07:19PM -0800, Quanah Gibson-Mount wrote: Sorry, the login table lookup must handle the original address as the lookup key via a single query. And clearly postfix is already designed in some cases to do multiple queries based on the results

Re: google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Wietse Venema
Robert Moskowitz: Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and sent many an email to the cubieboard list. I had one email bounce last week. Looks like they handle

Re: restrict or alter to address based on from address

2014-11-19 Thread Isaac Grover
+1 for imapsync, as we use it extensively when migrating a new customer onto our servers and they have a slew of email stored with their old provider that can't be left behind. On Nov 19, 2014 7:49 AM, Mikael Bak mikael@yandex.ru wrote: Hi, On 11/19/2014 03:27 AM, Joe Acquisto-j4 wrote:

Re: google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Robert Moskowitz
This is kind of what I was thinking was the case... On 11/19/2014 07:28 PM, Mark Martinec wrote: Robert Moskowitz wrote: Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and

Re: google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Robert Moskowitz
On 11/19/2014 07:46 PM, Wietse Venema wrote: Robert Moskowitz: Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and sent many an email to the cubieboard list. I had one

2.12-20141119 NetBSD6+ shared lib and dynamicmaps support. Also support for NetBSD7

2014-11-19 Thread Viktor Dukhovni
The NetBSD7 sys_defs.h change and new case pattern in makedefs are taken from NetBSD pkgsrc. I added the shared lib support which was tested on NetBSD6, and should work identically with NetBSD7, but by way of full disclosure, I've not had a chance to try that yet. diff --git a/makedefs

Re: sender login maps and alias domains

2014-11-19 Thread li...@rhsoft.net
Am 20.11.2014 um 00:06 schrieb Quanah Gibson-Mount: --On November 19, 2014 at 11:02:05 PM +0100 li...@rhsoft.net wrote: in case of such sites you have *databases* used directly for MTA queries or generate config files from databases LDAP is a database. It already contains all of the

Email-get-bounces.

2014-11-19 Thread Mohammed Ejaz
hello, Please experiencing two issues with customer. any explanation would be highly appreciated. 1. I have several entries as below for our one of the customer whose relaying his email through our mail servers Nov 20 07:41:05 mersal postfix/smtpd[30971]: warning:

Re: google bouncing emails - ipv6 ptr problem?

2014-11-19 Thread Robert Schetterer
Am 20.11.2014 um 01:46 schrieb Wietse Venema: Robert Moskowitz: Perhaps this should go to the bind list, but all of my checking shows my ipv6 ptr record is working. This started, I think, last week. I was running an old mailserver and sent many an email to the cubieboard list. I had

warnings about symlinks in /etc/postfix/

2014-11-19 Thread A. Schulze
Hello, I use to have symlinks in /etc/postfix to include files from other sources while building the local configuration. Since longer time I notice warnings from postfix-script every time I install a new postfix version. # postfix check postfix/postfix-script: warning: group or other