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 writ
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.
>
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: 212.
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 necess
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 b/makedefs
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 email
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
s
+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" wrote:
> Hi,
>
> On 11/19/2014 03:27 AM, Joe Acquisto-j4 wrote:
> [snip]
>
>> I wa
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 ha
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 o
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 g
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 cu
--On November 19, 2014 at 11:14:49 PM + Viktor Dukhovni
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 already designed in some
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 queri
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 missin
--On November 19, 2014 at 4:57:50 PM -0500 Wietse Venema
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 is aliased to. And eve
--On November 19, 2014 at 10:04:07 PM + Viktor Dukhovni
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 table lookup must handle the
--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 t
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 mi
Am 19.11.2014 um 22:57 schrieb Quanah Gibson-Mount:
--On November 19, 2014 at 9:39:26 PM + Viktor Dukhovni
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, Microso
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 yo
--On November 19, 2014 at 9:39:26 PM + Viktor Dukhovni
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 +
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 =
> (&(|(uid=%s)(zimbraAllowFromAddress=%s)(zimbraMailDeliveryAddress=%s)(zimbraMailAlias=%s)(zimbraMailCatchAllAddress=%s)
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 genera
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.
The
On Wed, Nov 19, 2014 at 10:16:02AM -0500, Wietse Venema wrote:
> Arrigo Marchiori:
> > Example 2: (error)
> > 220 myhost ESMTP Postfix
> > MAIL FROM:
> > 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 d
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): Ho
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
>
>
Arrigo Marchiori:
> Example 2: (error)
> 220 myhost ESMTP Postfix
> MAIL FROM:
> 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 / "<>"
Path = "<" [ A
* 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 r
On Wed, Nov 19, 2014, Arrigo Marchiori wrote:
> MAIL FROM:
> 501 5.1.7 Bad sender address syntax
> > MAIL FROM: [SP ]
> > The use of source routes is deprecated; while servers MUST be
> >From the above, I understand that the e-mail is poorly formatted, but
> also that Postfix should have
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 sessi
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=,
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=imaph
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=,
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
type=A: Host not
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
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 contro
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 (returni
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)
>> hostn
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 d
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 dev-
40 matches
Mail list logo
