I have set up Postfix for SPF for my domain simonandkate.net. Incoming
emails are being checked fine, but I am not 100% certain on setting up
the TXT record for outgoing emails.
I realise my Postfix config is working fine, but thought this list may
be able to quickly help me with the outgoi
On 5/9/2009, Curtis (postfixu...@isparks.com) wrote:
> I'm not talking about invalid recipients. We bounce email sent to
> invalid recipients at smtp time.
It helps avoid confusion to use the correct terms when discussing things
like this...
What you describe above is not BOUNCING, it is REJECTI
Hi Victor,
A high level description of my need may help:
"I would like to accept relaying messages coming from a set of IPs AND
which recipient address is described AT LEAST ONE TIME in the LDAP
directory, not as a mail/mailAlternateAddress address but as group(s)
member(s).
Example: from host
Rainer:
This my school project. I am setting up a new machine with just CentOS
5.3 installed and then I will first install PostgreSQL. Can you kindly
give me the name of the files I need to install and in what order.
Thank you, Rainer.
Jenn
Rainer Frey (Inxmail GmbH) wrote:
On Saturday 09
On Monday 11 May 2009 14:43:43 Just E. Mail wrote:
> Rainer:
>
> This my school project. I am setting up a new machine with just CentOS
> 5.3 installed and then I will first install PostgreSQL. Can you kindly
> give me the name of the files I need to install and in what order.
>
> Thank you, Rainer
Thank you Sahil and Aaron for the suggestions.
Since I will have multiple domains on this machine, would
it be valid to have a complete e-mail address in the recipient_bcc file so that
all the domains that have a user jane (such as j...@example2.com) don't get
archived?
# recipient_bcc map
j
Simon Wilson wrote:
I have set up Postfix for SPF for my domain simonandkate.net. Incoming
emails are being checked fine, but I am not 100% certain on setting up
the TXT record for outgoing emails.
I realise my Postfix config is working fine, but thought this list may
be able to quickly help
Greetings,
I have several Postfix implementations successfully handling outbound mail
relay directly to the Internet. These servers handle mail individually;
one physical server relays for all outbound mail for domainA.com, another
for domainB.com, etc. All servers have DNS/rDNS set up properly
Justin Peters:
> Greetings,
>
> I have several Postfix implementations successfully handling outbound mail
> relay directly to the Internet. These servers handle mail individually;
> one physical server relays for all outbound mail for domainA.com, another
> for domainB.com, etc. All servers ha
I guess I'm still missing something so here's my 'postfix -n' output and
logfile showing the rejection.
-Eric
for postfix to accept mail for a domain (from anywhere), the domain
needs to be found in one (and only one of):
- mydestination (this is for mail delivered to a unix a
Rainer:
Just to let you know that I have read several times all the
documentation you have mentioned. I have also installed the files you
suggested in your previous post. The reason I asked for a list of files
to install, to make sure that I was installing the correct files.
Jennifer
PS: I
On Mon May 11 2009 11:33:37 Eric Cunningham wrote:
> I guess I'm still missing something so here's my 'postfix -n' output
> and logfile showing the rejection.
> >>> for postfix to accept mail for a domain (from anywhere), the
> >>> domain needs to be found in one (and only one of):
> >>> - mydesti
On Monday, May 11, 2009 at 18:38 CEST,
"Just E. Mail" wrote:
> Rainer Frey (Inxmail GmbH) wrote:
>
> > Sorry, but instructions on installing PostgreSQL and what not are
> > hardly appropriate for this list. Ask your distribution vendor for
> > help, or better yet read the excellent documenta
On Monday, May 11, 2009 at 17:06 CEST,
Timothy Legg wrote:
> --- On Sun, 5/10/09, Sahil Tandon wrote:
>
> > You should be able to archive mail using any of those
> > methods. See:
> > http://www.postfix.org/postconf.5.html#recipient_bcc_maps
> > http://www.postfix.org/postconf.5.html#sen
You can install all the following packages by using "yum".
yum -y install postgresql-server postgresql-libs postgresql-devel
postgresql-contrib postfix
Andrew
--
Just E. Mail wrote:
Rainer:
Just to let you know that I have read several times all the
documentation you have mentioned. I hav
On Monday, May 11, 2009 at 18:59 CEST,
/dev/rob0 wrote:
[...]
> BTW, I always use complete paths for lookups. I think "ldap:vldap"
> defaults to "ldap:$config_directory/vldap", but it never hurts to
> be specific, so you know what you're getting.
ldap:vldap is the legacy configuration meth
...
virtual_alias_domains = $virtual_alias_maps
virtual_alias_maps = hash:/etc/postfix/virtual, ldap:vldap
These are all your address class definitions. We can't see into your
virtual_alias_maps to know what domains might be listed there. You can
show us "postmap -q sanguine.whoi.edu hash:/et
On Mon May 11 2009 12:08:02 Magnus Bäck wrote:
> On Monday, May 11, 2009 at 18:59 CEST,
> /dev/rob0 wrote:
>
> [...]
>
> > BTW, I always use complete paths for lookups. I think "ldap:vldap"
> > defaults to "ldap:$config_directory/vldap", but it never hurts to
> > be specific, so you know what
Eric Cunningham wrote:
May 11 12:24:19 obtest postfix/postfix-script[4849]: warning:
/var/spool/postfix/etc/resolv.conf and /etc/resolv.conf differ
Fix the above error. Probably not directly related to your
problem, but might cause unexpected behavior. The fix is
probably just:
# cp /et
On 11-May-2009, at 09:41, Mathias Meinelt wrote:
Simon Wilson wrote:
TXT v=spf1 a mx ip4:59.167.212.191 ~all
Is my TXT record OK? Do I need the IP4 entry?
[115 total lines deleted]
Mathias
Was it really necessary to quote all of the previous message? Yes,
top posting is evil and wro
Noel Jones wrote:
Apparently, sanguine.whoi.edu not listed in any of the postfix address classes.
Which address class do you expect this to be? Then you'll know where the
domain must be listed.
This is one document you need to understand:
http://www.postfix.org/ADDRESS_CLASS_README.html
Eric Cunningham:
> that to continue working, I'm now hearing that I must specifically list
> sanguine.whoi.edu "somewhere" in my postfix configs. That's not
> unreasonable, but let's now extend this example to another 250 hosts
> that are in a similar situation. I must now specifically find, l
Eric Cunningham wrote:
I want e...@sanguine.whoi.edu to continue
delivery to my imap account. In fact, that happened perfectly in my
previous postfix configuration.
... it worked previously due to a bug in permit_mx_backup.
That bug has been corrected.
Since upgrading postfix, in order f
I just installed CentOS Wiki guide for installing & configuring
Postfix restrictions & was wondering what you guys thought based on
what I have listed below. I just set this machine up and appears to be
working great but I trust you guys since you've been doing this for a
lot longer than I have:
h
Just E. Mail a écrit :
> Rainer:
>
> Just to let you know that I have read several times all the
> documentation you have mentioned. I have also installed the files you
> suggested in your previous post. The reason I asked for a list of files
> to install, to make sure that I was installing the co
Noel Jones wrote:
Eric Cunningham wrote:
I want e...@sanguine.whoi.edu to continue delivery to my imap
account. In fact, that happened perfectly in my previous postfix
configuration.
... it worked previously due to a bug in permit_mx_backup. That bug has
been corrected.
Ahh...finally, s
On Mon May 11 2009 14:45:14 Eric Cunningham wrote:
> This may be of use in my situation. Can you point me to the docs
> that explain how to configure wildcard subdomains?
postconf.5.html#parent_domain_matches_subdomains ... one way
pcre_table.5.html ... another way
regexp_table.5.html ... another
I've got a restriction class client_filter.class, which has several PCREs.
The problem is that some PTRs that should be shunted into that class are not.
When I test/paste actual maverick PTRs, eg this "access net" PTR:
postmap -q "79-70-88-236.as9105.com["
pcre:/usr/local/etc/postfix/client_f
Len Conrad wrote:
I've got a restriction class client_filter.class, which has several PCREs.
The problem is that some PTRs that should be shunted into that class are not.
When I test/paste actual maverick PTRs, eg this "access net" PTR:
postmap -q "79-70-88-236.as9105.com["
pcre:/usr/local
Len Conrad a écrit :
> I've got a restriction class client_filter.class, which has several PCREs.
>
> The problem is that some PTRs that should be shunted into that class are not.
>
>
> When I test/paste actual maverick PTRs, eg this "access net" PTR:
>
> postmap -q "79-70-88-236.as9105.com["
On Mon, May 11, 2009 at 02:29:45PM +0200, postfix wrote:
> A high level description of my need may help:
> "I would like to accept relaying messages coming from a set of IPs AND
> which recipient address is described AT LEAST ONE TIME in the LDAP
> directory, not as a mail/mailAlternateAddress ad
Quoting Mathias Meinelt :
Simon Wilson wrote:
TXT v=spf1 a mx ip4:59.167.212.191 ~all
Your setup of the SPF record is ok, however you should leave out
the
"a" and "mx" directive as they have no use here unless you want to
send mail over "mail.bluetie.com" as well.
This SPF Record should w
mouss wrote:
Len Conrad a écrit :
... they work, and works for each different PCRE in the .class.
The above is caught by:
/[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}(\.|\-)[0-9]{1,3}.*\[/
client_filter.class
remove the \[ part.
and BTW, here is a shorter version:
/(\d{1,3}[-\.]){3}\d
On Mon, 11 May 2009, Carlos Williams wrote:
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases
> append_dot_mydomain = no
> biff = no
> config_directory = /etc/postfix
> content_filter = smtp-amavis:[127.0.0.1]:10024
> home_mailbox = Maildir/
> inet_interfaces = all
> mailbox_si
On Mon, May 11, 2009 at 03:24:02PM -0400, Carlos Williams wrote:
> smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
In more recent versions of Postfix, this should be in ${data_directory}.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignore
35 matches
Mail list logo