Hi
On 06/02/2014 05:11 PM, st...@thornet.co.uk wrote:
Hi
We use sqlgrey as a policy daemon for greylisting. It runs on both our
mail servers with a shared database on one of them. If the database is
unavailable for some reason on the main server the backup rejects mail
with "451 4.3.5 Server co
On Jun 3, 2014 12:06 AM, wrote:
>
> >
> > you *do not* lose anything
> >
> > 451 is a *temporary* error
> > 5xx would be a complete reject
> >
>
> Yes, but many mails rejected in an incident this morning haven't been
resent. I guess we're dealing with broken clients.
>
What sort of "broken" clien
> What sort of "broken" clients are these that don't
use real email servers,
> and how do you know they are broken?
They could very well be waiting for
> some time to pass before
retrying again (and there is some kind of a
> system
> for
these intervals. It's not as if the standard protocol is
On Tue, 03 Jun 2014 11:17:07 +0200
Микаел Бак wrote:
> Maybe you should consider having a master db on one of the mail
> servers and a slave db on the other one and have the data be
> replicated to the slave automatically.
Since both servers need to write to the database as well the slave is
stil
Am 03.06.2014 11:39, schrieb st...@thornet.co.uk:
>> What sort of "broken" clients are these that don't use real email servers,
>> and how do you know they are broken? They could very well be waiting for
>> some time to pass before retrying again (and there is some kind of a
>> system
>> for thes
Hi,
On 06/03/2014 11:42 AM, D'Arcy J.M. Cain wrote:
On Tue, 03 Jun 2014 11:17:07 +0200
Микаел Бак wrote:
Maybe you should consider having a master db on one of the mail
servers and a slave db on the other one and have the data be
replicated to the slave automatically.
Since both servers need
Hi I have the same configuration and situation as the following:
http://serverfault.com/questions/132750/postfix-whitelist-before-recipient-restrictions
In short:
"
So i need a method of whitelisting ANY email that comes to domain.com, however
i need it to take place before any of the recipien
On 03/06/2014 15:33, mancyb...@gmail.com wrote:
Hi I have the same configuration and situation as the following:
http://serverfault.com/questions/132750/postfix-whitelist-before-recipient-restrictions
In short:
"
So i need a method of whitelisting ANY email that comes to domain.com, however
i
mancyb...@gmail.com:
> So i need a method of whitelisting ANY email that comes to domain.com,
> however i need it to take place before any of the recipient
> restrictions, they want no RBL or postgrey blocking at all.
Birta Levente:
> If you want to whitelist recipient domain you need to check rec
On Tue, Jun 03, 2014 at 08:55:46AM -0400, Wietse Venema wrote:
> mancyb...@gmail.com:
> > So i need a method of whitelisting ANY email that comes to domain.com,
> > however i need it to take place before any of the recipient
> > restrictions, they want no RBL or postgrey blocking at all.
>
> Birta
Hello,
we have a postfix server which has the user config stored in a openldap
directory.
Recently we also implemented ldap groups which are expanded by postfix. This
works fine, unless the group expands to some email alias destinations.
All alias expanded from the group seem to not be resolve
On Tue, Jun 03, 2014 at 02:28:22PM +, Andr? Schild wrote:
> Recently we also implemented ldap groups which are expanded by postfix.
> This works fine, unless the group expands to some email alias destinations.
Virtual(5) alias expansion is performed recursively in cleanup(8)
for all recipient
Wietse:
Begin quote from Postfix sendmail manpage
-C config_file
-C config_dir
The path name of the Postfix main.cf file, or of its parent
directory. This information is ignored with Postfix versions
before 2.3.
With a
> > Recently we also implemented ldap groups which are expanded by postfix.
> > This works fine, unless the group expands to some email alias destinations.
>
> Virtual(5) alias expansion is performed recursively in cleanup(8) for all
> recipient addresses. Recursive local aliases(5) expansion hap
On Tue, 3 Jun 2014 08:55:46 -0400 (EDT)
wie...@porcupine.org (Wietse Venema) wrote:
> mancyb...@gmail.com:
> > So i need a method of whitelisting ANY email that comes to domain.com,
> > however i need it to take place before any of the recipient
> > restrictions, they want no RBL or postgrey block
On Tue, Jun 03, 2014 at 10:31:34AM -0500, Rick Zeman wrote:
> I'm using the Apple-compiled Postfix 2.9.4 that comes with Mac
> Mavericks server. One thing that made setup much harder than it
> needed to be for me is that Apple puts their postfix config files in a
> different location than the "st
On Tue, Jun 03, 2014 at 03:31:28PM +, Andr? Schild wrote:
> > I recommend "proxy:ldap:..." rather than "ldap:...".
>
> This will just improve resource usage, but not change behaviour, correct?
Yes.
> > > server_host = ldap://openldap1.server
> > > version = 3
> > > search_base = ou=groups,o
On Tue, Jun 3, 2014 at 11:18 AM, Viktor Dukhovni
wrote:
> On Tue, Jun 03, 2014 at 10:31:34AM -0500, Rick Zeman wrote:
>
>> I'm using the Apple-compiled Postfix 2.9.4 that comes with Mac
>> Mavericks server. One thing that made setup much harder than it
>> needed to be for me is that Apple puts th
Rick Zeman:
> I'm using the Apple-compiled Postfix 2.9.4 that comes with Mac
> Mavericks server. One thing that made setup much harder than it
> needed to be for me is that Apple puts their postfix config files in a
> different location than the "standard" /etc/postfix, but yet the
> postfix helpe
On Tue, Jun 3, 2014 at 12:04 PM, Wietse Venema wrote:
> Rick Zeman:
>> I'm using the Apple-compiled Postfix 2.9.4 that comes with Mac
>> Mavericks server. One thing that made setup much harder than it
>> needed to be for me is that Apple puts their postfix config files in a
>> different location
Rick Zeman:
> > I suspect that you have programs from different Postfix builds
> > on the same machine.
> >
> > Postfix would never work when some Postfix programs have a different
> > built-in config_directory than other Postfix programs.
>
> Hi Wietse,
>
> That could well be (is there a way to
Hello Viktor,
> > > > server_host = ldap://openldap1.server version = 3 search_base =
> > > > ou=groups,o=mailhosting query_filter =
> > > > (&(mail=%s)(objectclass=groupOfUniqueNames))
> > > > leaf_result_attribute = mail
> > > > special_result_attribute = uniquemember
> > >
> > > What's in "lda
Hi Steve,
>
We use sqlgrey as a policy daemon for greylisting. It runs on both our
mail servers with a shared database on one of them. If the database is
unavailable for some reason on the main server the backup rejects mail
with "451 4.3.5 Server configuration problem" Is it possible to change
On Tue, Jun 03, 2014 at 06:47:26PM +, Andr? Schild wrote:
> dn: mail=langenth...@client.ch,jvd=client.ch,o=mailhosting
> objectClass: JammMailAccount
> objectClass: top
> accountActive: FALSE
> delete: FALSE
> homeDirectory: /home/vmail/domains
> lastChange: 1363865462
> mail: langenth...@clie
Hey guys, I'm seeing in my logs 2 things causing me some concern, I
don't need to go in to all my settings, just looking to see if
anything stands out from the message and common causes:
Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
cleers.dustypex.com does not resolve to addres
Am 03.06.2014 21:34, schrieb Paul C:
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
> cleers.dustypex.com does not resolve to address xx.xx.xx.xx: Temporary
> failure in name resolution
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: connect from
> unknown[xx.xx.xx.xx]
> Jun
Paul C:
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
> cleers.dustypex.com does not resolve to address xx.xx.xx.xx: Temporary
> failure in name resolution
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: connect from
> unknown[xx.xx.xx.xx]
The client IP address has no PTR re
Hi,
I'm trying to find out which is the correct way to configure alias
domains on postfix.
For example, I have 3 different domains (example.com, example.info,
example.net), and when I send an e-mail to a user on any of the three
domains it's always sent to "u...@example.com".
In other words, I ne
On 6/3/2014 3:50 PM, Peter Bittner wrote:
> Hi,
>
> I'm trying to find out which is the correct way to configure alias
> domains on postfix.
>
> For example, I have 3 different domains (example.com, example.info,
> example.net), and when I send an e-mail to a user on any of the three
> domains it
Thanks for the responses, and right on point, RDNS from my host has
been failing here and there the last 2 days, they tell me they are
fixing it, the ptr records exist but seem to be timing out at times,
so good to see that's one of the problems as it should be fixed soon.
cleers.dustypex.com. is
Your domain seems to be on URIBL blacklist (black)
"Contains an URL listed in the URIBL blacklist [URIs: d u s t y p e x.com]"
jfyi
Razvan
-Original Message-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Tuesday, June
That's not my domain, its the one trying to send mail through my
postfix server, it connects to my ip and tries to send on it, postfix
is logging the warning message for hostname not matching, that's how I
saw it.
On Tue, Jun 3, 2014 at 7:13 PM, Inteq Solution - Dep. Tehnic
wrote:
> Your domain s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
opensuse 13.1
postfix 2.9.6-7.4.1
I recently upgraded a server from 12.3 to 13.1. Postfix worked
correctly in v12.3.
Postfix fails to start with this message:
Code:
- -- Unit postfix.service has failed.
- --
- -- The result is dependency.
Jun 03 1
James Moe:
> opensuse 13.1
> postfix 2.9.6-7.4.1
>
> I recently upgraded a server from 12.3 to 13.1. Postfix worked
> correctly in v12.3.
>
> Postfix fails to start with this message:
>
> Code:
> -- Unit postfix.service has failed.
> --
> -- The result is dependency.
> Jun 03 10:59:24 sma-server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2014 05:33 PM, Wietse Venema wrote:
>
> $ postconf | egrep '_(directory|path) ='
>
> Maybe that causes the coin to drop.
>
No, that did not show "/t2" anywhere as a dependency.
"postconf | egrep 't2'" produced no results, either.
- --
On Tue, Jun 03, 2014 at 05:07:22PM -0700, James Moe wrote:
> Postfix fails to start with this message:
>
> Code:
> - -- Unit postfix.service has failed.
> - --
> - -- The result is dependency.
> Jun 03 10:59:24 sma-server3 systemd[1]: t2.mount mount process exited,
> code=exited status=32
> Jun
I want mail to example.org to be delivered to the local virtual
mailboxes. I want mail to in.example.org to be relayed to
mail.power.com.
The configuration below is relaying all mail to mail.power.com.
Can someone please suggest what I need to do to fix?
thanks
# See /usr/share/postf
On Wed, Jun 04, 2014 at 11:39:56AM +1000, Andrew Stuart wrote:
> I want mail to example.org to be delivered to the local virtual mailboxes. I
> want mail to in.example.org to be relayed to mail.power.com.
>
> The configuration below is relaying all mail to mail.power.com.
Try "postconf -n" instea
postconf -n output
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
home_mailbox = Maildir/
inet_interfaces = all
local_recipient_maps = $virtual_mailbox_maps
local_transport = virtual
mailbox_size_limit = 0
messa
On Wed, Jun 04, 2014 at 11:52:59AM +1000, Andrew Stuart wrote:
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> home_mailbox = Maildir/
Only applicable with local(8) delivery, but you have
local_transport = virtual, so unless you have explicit
transport entries selecting "l
transport file contains:
* smtp:mail.power.com
On 04/06/2014, at 11:59 AM, Viktor Dukhovni wrote:
On Wed, Jun 04, 2014 at 11:52:59AM +1000, Andrew Stuart wrote:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
home_mailbox = Maildir/
Only applicable with local(
On Wed, Jun 04, 2014 at 12:16:08PM +1000, Andrew Stuart wrote:
> transport file contains:
>
> * smtp:mail.power.com
And you're surprised why everything is going via smtp to mail.power.com?
--
Viktor.
On Tue, 03 Jun 2014 17:07:22 -0700
James Moe wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> opensuse 13.1
> postfix 2.9.6-7.4.1
>
> I recently upgraded a server from 12.3 to 13.1. Postfix worked
> correctly in v12.3.
>
> Postfix fails to start with this message:
>
> Code:
> -
Not since you pointed it out.
Thanks Viktor works fine now.
On 04/06/2014, at 12:17 PM, Viktor Dukhovni wrote:
On Wed, Jun 04, 2014 at 12:16:08PM +1000, Andrew Stuart wrote:
transport file contains:
* smtp:mail.power.com
And you're surprised why everything is going via smtp to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/03/2014 05:07 PM, James Moe wrote:
> opensuse 13.1 postfix 2.9.6-7.4.1
>
> I recently upgraded a server from 12.3 to 13.1. Postfix worked
> correctly in v12.3.
>
The mount errors are spurious for loading Postfix, as some have noted.
I fina
45 matches
Mail list logo
