On 2011-12-27 06:45, Glenn Sieb wrote:
Dear list,
While I have SASL set up on port 587, I recently found that foreign
IPs can connect, pretend to be, say, me, and send mail to my users.
SPF can catch this, but I think it's something that should/can be
caught by Postfix, no? So I conclude I have
Alex Vilceloiu:
> I want to be like "/home/$username/domainX/mailbox/.." where
> "$username" is a unix account.
Something like this:
virtual_mailbox_base = /home
virtual_mailbox_maps =
.. some Postfix-SQL map that replies with username/domainX/mailbox/ ..
virtual_uid_maps = some Postfix-SQL
Hello,
I have a mail server with postfix (mysql virtual
users/domains)+courier+amavis-spamassassin-clamd.
It is possible to change the virtual mailbox path, currentl I have
"virtual_mailbox_base = /mail"?
The mails are stored like "/mail/domain1/user1" "/mail/domain2/user1".
I want to be like "/
On Tuesday 27 December 2011 10:11:37 Alex Vilceloiu wrote:
> I have a mail server with postfix (mysql virtual
> users/domains)+courier+amavis-spamassassin-clamd. It is possible
Everything after the ")+" is mostly/probably irrelevant here.
> to change the virtual mailbox path, currentl I have
> "v
Hi Michael,
We use a solution with 2 loadbalancers in front of 3+ postfix servers
All MX records ( for around 100 domains ) are directed to the same address - the
address of the loadbalancers. Based on statistics for each server the
mail is redirected to one of the 3-6 postfix servers we have runn
Hi all,
Reindl: Thanks for your reply.
I guess this is for sending mails from postfix... my setup is regarding
"linux server->postfix" (so receiving mails, seen from postfix
point-of-view).
- how many retries total/per day ?
- what is the difference if I do it "DNS RR"/"MX equal value", do you kno
Hi all,
Thanks Peter, for you kind reply - some setup you have there... sounds very
nice indeed...:-) !
- If i have a lower budget, can this then be achieved without the
loadbalancers and still have same redundancy/flexibility (using e.g. "DNS
RR"/"MX with equal value") - if so what is for/against
On Tuesday 27 December 2011 07:07:22 Jeroen Geilman wrote:
> On 2011-12-27 06:45, Glenn Sieb wrote:
> > While I have SASL set up on port 587, I recently found that
> > foreign IPs can connect, pretend to be, say, me, and send mail
> > to my users. SPF can catch this, but I think it's something that
Am 27.12.2011 18:12, schrieb Michael Maymann:
> But if one postfix servers goes down, will all DNS replies then be only for
> alive-postfix
> or will there also be dead-postfix replies that needs to timeout, before it
> retries
> (and for how many times?) and potentially end up dropping the m
On 12/27/2011 11:26 AM, Michael Maymann wrote:
> Hi all,
>
> Reindl: Thanks for your reply.
> I guess this is for sending mails from postfix... my setup is
> regarding "linux server->postfix" (so receiving mails, seen from
> postfix point-of-view).
> - how many retries total/per day ?
Retries are
On Tue, Dec 27, 2011 at 06:12:12PM +0100, Michael Maymann wrote:
> Hi all,
>
> Thanks Peter, for you kind reply - some setup you have there... sounds very
> nice indeed...:-) !
> - If i have a lower budget, can this then be achieved without the
> loadbalancers and still have same redundancy/flexib
Reviving an old thread from 2011-09:
Mark Martinec:
> Trying to install postfix on an IPv6-only host
> FreeBSD 9.0B1, http://wiki.freebsd.org/IPv6Only
> ports: mail/postfix-current,
> but the installation chokes in the post-install phase.
> Running that failing command manually (in the ports w
Mark Martinec:
> Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> (with an inet6-only kernel), the installation fails as before:
>
> postfix-current$ make install
> ...
> Skipping /usr/local/share/doc/postfix/postfix-power.png...
> Skipping /usr/local/share/doc/postfix/scache.8.h
Hi Lorens,
thanks for your kind reply...:-) !
yes this is exactly the case... and my internal local-mailers consist on
standard RHEL5+6 servers and NetApp's.
Our ISP is restricting mail from only 1 of our sites, so we need to relay
all our internal mail globally through this site.
We can't preven
Wietse Venema:
> Mark Martinec:
> > Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> > (with an inet6-only kernel), the installation fails as before:
> >
> > postfix-current$ make install
> > ...
> > Skipping /usr/local/share/doc/postfix/postfix-power.png...
> > Skipping /usr/loc
> > postfix: fatal: could not find any active network interfaces
> > *** Error code 1
>
> How do you want to proceed: wait until I have time to reproduce
> your IPv6-only setup for which I have no specification, or spend
> all of next year doing blind testing?
No offense and not intending to rush
> I'm assuming that you have "inet_protocols=ipv6" in main.cf, instead
> of the backwards-compatibility "inet_protocols=ipv4" workaround,
> because that would not work on your machine.
No, that was a fresh install attempt, no directory /etc/postfix
or /usr/local/etc/postfix, no previous main.cf or
Mark Martinec:
> > I'm assuming that you have "inet_protocols=ipv6" in main.cf, instead
> > of the backwards-compatibility "inet_protocols=ipv4" workaround,
> > because that would not work on your machine.
>
> No, that was a fresh install attempt, no directory /etc/postfix
> or /usr/local/etc/post
On Tue, Dec 27, 2011 at 09:24:01PM +0100, Michael Maymann wrote:
> thanks for your kind reply...:-) !
> yes this is exactly the case... and my internal local-mailers consist on
> standard RHEL5+6 servers and NetApp's.
> Our ISP is restricting mail from only 1 of our sites, so we need to relay
> all
Wietse Venema:
> Wietse Venema:
> > Mark Martinec:
> > > Trying to install postfix-2.9-20111219 from ports on FreeBSD 9.0
> > > (with an inet6-only kernel), the installation fails as before:
> > >
> > > postfix-current$ make install
> > > ...
> > > Skipping /usr/local/share/doc/postfix/postfix-pow
On Tue, 2011-12-27 at 17:24:57 -0500, Wietse Venema wrote:
> ...
> After I made "inet_protocols=all" the default on your request, I
> received notice that Postfix no longer would build on freebsd.org
> "build" systems, and that it would be removed from ports. These
> build environments have IPv6
Wietse Venema:
> After I made "inet_protocols=all" the default on your request, I
> received notice that Postfix no longer would build on freebsd.org
> "build" systems, and that it would be removed from ports. These
> build environments have IPv6 in the kernel but they have no IPv6
> interfaces. B
22 matches
Mail list logo
