Re: Problem with DNS lookup when chrooted

I'm running Ubuntu 10.04 and I installed Postfix 2.8.4 from Christian Roessner's PPA. ricardus Stan Hoeppner wrote: > > On 8/10/2011 9:17 AM, ricardus1867 wrote: >> >>> Chroot and multiple instance support are, or should be, handled properly >> by the P

Re: Problem with DNS lookup when chrooted

nce effectively screwed up the usual directory structure... Guess there were some leftovers preventing the installation script from working properly. Because I didn't have those problems when I installed it the first time... ricardus Stan Hoeppner wrote: > > On 8/10/2011 12:10 AM, rica

Re: Problem with DNS lookup when chrooted

That did it. Thanks! ricardus Jeroen Geilman wrote: > > On 2011-08-10 07:10, ricardus1867 wrote: >> Hi! >> >> By trying to add a second postfix instance (something seems to have went >> terribly wrong), I managed to screw up my postfix. Badly. Nothing would >

Re: Alternatives to two instances

n when I get it fixed. Anyway, thanks for the input. Regards ricardus Noel Jones-2 wrote: > > On 8/9/2011 2:01 PM, ricardus1867 wrote: >> >> Hi! >> >> I'm running postfix on a VPS with two IP addresses. Each IP address is >> used >&g

Problem with DNS lookup when chrooted

Hi! By trying to add a second postfix instance (something seems to have went terribly wrong), I managed to screw up my postfix. Badly. Nothing would work anymore. So I tried the scorched earth approach (purge, then install). That worked more or less, except for the fact that /var/spool/postfix/e

Alternatives to two instances

Hi! I'm running postfix on a VPS with two IP addresses. Each IP address is used for a different service and I don't want those to be linked. Everything would be running smooth IF it wasn't for the SMTP banner. Which promptly gives away that seconddomain.com is using the same server as firstdomai

Re: reject_unauth_pipelining not working as I'd expect (bug?)

On 7/7/2011 11:20 PM, ricardus1867 wrote: > > While crawling trough my logs, I've noticed a couple of bots getting > > rejected because of Improper use of SMTP command pipelining because of > the > > reject_unauth_pipelining in smptd_recipient_restrictions. So I dec

reject_unauth_pipelining not working as I'd expect (bug?)

Hi! While crawling trough my logs, I've noticed a couple of bots getting rejected because of Improper use of SMTP command pipelining because of the reject_unauth_pipelining in smptd_recipient_restrictions. So I decided to give the old "sleep" trick a try. Only for unknown hosts, ofc... The http