Change in pcre file requires reload?

In main.cf I have a configuration line: sender_canonical_maps = pcre:/etc/postfix/pt_lu.pcre When I change something inside pt_lu.pre, do I then need to reload postfix? Thanks, Yves

Re: Change in pcre file requires reload?

* Yves Kreis : > In main.cf I have a configuration line: > sender_canonical_maps = pcre:/etc/postfix/pt_lu.pcre > > When I change something inside pt_lu.pre, do I then need to reload > postfix? No, Postfix will eventually pick up the change -- Ralf Hildebrandt (ralf.hildebra...@charite.de)

Re: Change in pcre file requires reload?

On 09.01.2009, at 10:31, Edward Krack wrote: postmap /etc/postfix/pt_lu.pcre postfix reload http://www.postfix.org/PCRE_README.html On Fri, Jan 9, 2009 at 2:57 AM, Yves Kreis wrote: In main.cf I have a configuration line: sender_canonical_maps = pcre:/etc/postfix/pt_lu.pcre When I change

Fwd: Cannot connect to smtp server

> >> From the laptop, what happens when you >> telnet smtp.gmail.com 25 > > telnet smtp.gmail.com 25 > Trying 66.249.93.109... > Trying 66.249.93.111... > telnet: Unable to connect to remote host: Connection refused > > But gmail does not only use port 25. It uses port 465 (with ssl) and > 587 (w

Need help with postfix migration

HI, Two days ago my company mail server died. I was able to set up a temporary server until I could get the data off the old drive. Tonite I moved mailman and /var/spool/ over and reconstructed the mail boxes. Everything looked great until I tried to send mail. Everyone can get mail, but

Re: PATCH: bug from May 19, 1997

Victor Duchovni: > Translation, this only matters for parameters that change the behaviour > of the master daemon. Removing such a parameter from main.cf did not > result in changed master(8) behaviour without a full restart. > > Most users don't modify master(8) parameters other than inet_interfa

Re: Need help with postfix migration

On Fri, 9 Jan 2009 03:33:59 -0800 carconni wrote: > HI, > > Two days ago my company mail server died. I was able to set up a > temporary server until I could get the data off the old drive. > Tonite I moved mailman and /var/spool/ over and reconstructed the > mail boxes. > > Everything looked

Re: Need help with postfix migration

Chris Babcock wrote: On Fri, 9 Jan 2009 03:33:59 -0800 carconni wrote: HI, Two days ago my company mail server died. I was able to set up a temporary server until I could get the data off the old drive. Tonite I moved mailman and /var/spool/ over and reconstructed the mail boxes. Every

Re: Change in pcre file requires reload?

Yves Kreis wrote: postmap for pcre files? Are you sure? The readme doesn't mention postmap or reload... No, these files do not need to be postmapped. -- Corey Chandler / KB1JWQ Living Legend / Systems Exorcist Today's Excuse: The new frame relay network hasn't bedded down the software loop

Re: "forcing" authenticated users to use port 587?

Sahil Tandon wrote, at 01/08/2009 11:37 PM: > Jeff Weinberger wrote: > >> Also you noted: >> In the final step of my scenario, that's the behavior I want to achieve. Will that simple step work? >>> Yes. You can completely disable submission on port 25 and prevent >>> relaying to d

Re: getting dns error

Sahil Tandon wrote, at 01/08/2009 10:06 PM: > James D. Parra wrote: > >> I am getting the following error when sending to the below mail server. I >> added the name of our internal relay server to our public dns and a ptr >> record, but I am still getting the error below. >> >> >> host mxi4p.cra

Re: Problem of mail suffix replacement

2008/12/17 Gauthier DOUCHET > Hi all, > > I have a problem with a system based on Postfix+LDAP with virtual domains. > > I'm using LDAP to store domains and user. The LDAP tree is like that: > ou=hosting > +virtualdomain=company1.common.com > ++ou=mail > +++uid=user1 (with attribute mail wich is

Re: Fwd: Cannot connect to smtp server

Vikas Rawal wrote: > >> From the laptop, what happens when you >> telnet smtp.gmail.com 25 > > telnet smtp.gmail.com 25 > Trying 66.249.93.109... > Trying 66.249.93.111... > telnet: Unable to connect to remote host: Connection refused >

Re: Problem of mail suffix replacement

On Wed, Dec 17, 2008 at 09:21:18AM +0100, Gauthier DOUCHET wrote: > For example, when us...@company1.common.com sends a mail to some mail > adresses, when these people receive the mail, instead to have the mail From > filled with us...@company1.common.com, they have us...@www.common.com (this > is

RE: getting dns error

> -Original Message- > From: James D. Parra > Sent: Thursday, January 08, 2009 6:51 PM > To: Postfix users (E-mail) > Subject: getting dns error > > > Hello, > > I am getting the following error when sending to the below > mail server. I added the name of our internal relay server

Re: Change in pcre file requires reload?

Ralf Hildebrandt wrote: * Yves Kreis : In main.cf I have a configuration line: sender_canonical_maps = pcre:/etc/postfix/pt_lu.pcre When I change something inside pt_lu.pre, do I then need to reload postfix? No, Postfix will eventually pick up the change While postfix will eventually pic

safe wildcard aliasing with mysql [Was: Reject_unlisted_recipient and "wide" aliasing]

Roman Medina-Heigl Hernandez a écrit : > [snip] > Any ideas to improve this? I think this could be solved with more mysql > magic... > let's use these "simplistic" tables (no id/keys... for simplicity): - a User table, with the following columns * user: the user-part of an email address * doma

Re: "forcing" authenticated users to use port 587?

jeff_homeip a écrit : > > Thanks for pointing it out - I've read it several times already. > > "ORIGINATING" is not mentioned at all in MILTER_README. > > And while I'm sure the postconf(5) brief explanation is meaningful to you, it > means > nothing to me. > > As I noted, I am completely un

Re: getting dns error

James D. Parra a écrit : > >> -Original Message- >> From: James D. Parra >> Sent: Thursday, January 08, 2009 6:51 PM >> To: Postfix users (E-mail) >> Subject: getting dns error >> >> >> Hello, >> >> I am getting the following error when sending to the below >> mail server. I added the

Preventing domain mails from outside

I am trying to stop a flood of incoming spam that appears in user inboxes as coming from legitimate users. The intent is to reject any emails claiming to be from inside our own network which do not actually originate from our own server IPs or authenticated sessions. In order to do this I follo

Re: Preventing domain mails from outside

Norm Mackey: > Received: by www.thisisireallymydomain.com (Postfix) > id 3C916254775; Tue, 30 Dec 2008 03:50:01 -0800 (PST) That mail did not arrive via SMTP. Look in your maillog file around that time. If this mail comes from your HTTP account, the look in the HTTP logs for details. If the HT

Re: Preventing domain mails from outside

Norm Mackey wrote: > The intent is to reject any emails claiming to be from inside our > own network which do not actually originate from our own server > IPs or authenticated sessions. > > In order to do this I followed the instructions I found at > http://tech.groups.yahoo.com/group/postfix-u

Re: Preventing domain mails from outside

Sahil Tandon wrote: > > > Received: by www.thisisireallymydomain.com (Postfix) > > > id 3C916254775; Tue, 30 Dec 2008 03:50:01 -0800 (PST) > > > Delivered-To: n...@thisisireallymydomain.com > > > Received: from alkhorayef.com (unknown [91.189.132.54]) Some additional advice: consider using the z

Re: Preventing domain mails from outside

On Fri, Jan 09, 2009 at 10:55:22PM -0500, Sahil Tandon wrote: > > How do I filter on the actual domain that it is coming from instead of > > the forged > > "From:" sent in the message headers? > > You need to filter based on the headers More accurately, the OP will need to abandon the idea of fi