Hello,
I have a few simple questions to be sure using the right commands to do
what I want :
Situation
-
I have mails in the queue (I can see them with mailq).
A) I want to delete them
- postqueue -f
- postsuper -d ALL
- mailq | awk '{if (NF == 7) print $1'} | postsuper -d -
Are thes
Salut,
On 27 juin 2011, at 11:09, Nicolas Michel wrote:
> I have mails in the queue (I can see them with mailq).
>
> A) I want to delete them
> - postqueue -f
nope, it will just flush the queue (force a new delivery attempt)
> - postsuper -d ALL
> - mailq | awk '{if (NF == 7) print $1'} | post
On 06/27/2011 11:24 AM, Patrick Proniewski wrote:
Salut,
On 27 juin 2011, at 11:09, Nicolas Michel wrote:
I have mails in the queue (I can see them with mailq).
A) I want to delete them
- postqueue -f
nope, it will just flush the queue (force a new delivery attempt)
- postsuper -d ALL
- m
Nicolas Michel:
> OK. So if I understand well, "postsuper -r ALL" puts mails into the
> starting point of the postfix delivery process (as like the mail were
> just arrived on the server) but "postqueue -f" only try to deliver them?
> (without reprocessing all the headers of each mail?)
>
> If
I am running a postfix server on Freebsd 8.1
I have multiple domains and need to set up each domain with its own TLS
certificate.
I emailed this list and the best solution seems to be to run multiple
instances.
I read through the documentation and I want to clarify things before I
start making
Mark Moellering:
> I am running a postfix server on Freebsd 8.1
> I have multiple domains and need to set up each domain with its own TLS
> certificate.
> I emailed this list and the best solution seems to be to run multiple
> instances.
> I read through the documentation and I want to clarify th
On 27-Jun-11 12:50 PM, Wietse Venema wrote:
Mark Moellering:
I am running a postfix server on Freebsd 8.1
I have multiple domains and need to set up each domain with its own TLS
certificate.
I emailed this list and the best solution seems to be to run multiple
instances.
I read through the docum
On 6/27/2011 12:01 PM, Mark Moellering wrote:
Ahh I see... What about the sql files? Can each instance point
to the same directory or do I need different directories per
instance? Since everything is already set to handle multiple
domains, I can use the same sql for each...
Multiple instances
Mark Moellering:
> Does each instance need its own uid and gid?
Wietse:
> The documentation does not say that different instances must have
> different mail_owner and setgid_group settings, so don't do that.
Mark Moellering:
> It says that "The default instance is responsible for local mail
> sub
Good mornig!
We want to block any mail locally seded from apache account.
Many years ago we set in main.cf:
authorized_submit_users = !apache,static:all
but after upgrading postfix from 2.7.4 to 2.8.3
this option suddenly stop working.
:
Th
> I have multiple domains and need to set up each domain with its own TLS
> certificate.
Can you explain this a little bit more? You could add several
w1.x1.y1.z1:smtp ... smtpd
w1.x1.y1.z1:submission ... smtpd
w2.x2.y2.z2:smtp ... smtpd
w2.x2.y2.z2:submission ... smtpd
Example from my server:
On 6/27/2011 2:14 PM, Bartłomiej Solarz-Niesłuchowski wrote:
Good mornig!
We want to block any mail locally seded from apache account.
Many years ago we set in main.cf:
authorized_submit_users = !apache,static:all
but after upgrading postfix from 2.7.4 to 2.8.3
this option suddenly stop workin
I was having trouble getting that to work but with your example I might
try it again...
On 27-Jun-11 3:25 PM, Christian Roessner wrote:
I have multiple domains and need to set up each domain with its own TLS
certificate.
Can you explain this a little bit more? You could add several
w1.x1.y1.
I saw a configuration for blocking web mail from Apache from accessing
Postfix. I think it was something like: !www or something like that. I
forgot to write it down and now I cannot locate it. Does anyone know
what the recipe is. Thanks!
Am 27.06.2011 23:44, schrieb Jerry:
> I saw a configuration for blocking web mail from Apache from accessing
> Postfix. I think it was something like: !www or something like that. I
> forgot to write it down and now I cannot locate it. Does anyone know
> what the recipe is. Thanks!
i guess nobod
Jerry:
> I saw a configuration for blocking web mail from Apache from accessing
> Postfix. I think it was something like: !www or something like that. I
> forgot to write it down and now I cannot locate it. Does anyone know
> what the recipe is. Thanks!
This was discussed here three postings befor
On Behalf Of Reindl Harald
>
> Am 27.06.2011 23:44, schrieb Jerry:
> > I saw a configuration for blocking web mail from Apache from accessing
> > Postfix. I think it was something like: !www or something like that. I
> > forgot to write it down and now I cannot locate it. Does anyone know
> > what
On Mon, 27 Jun 2011 23:47:50 +0200
Reindl Harald articulated:
> Am 27.06.2011 23:44, schrieb Jerry:
> > I saw a configuration for blocking web mail from Apache from
> > accessing Postfix. I think it was something like: !www or something
> > like that. I forgot to write it down and now I cannot loc
On Mon, 27 Jun 2011 18:06:19 -0400 (EDT)
Wietse Venema articulated:
> Jerry:
> > I saw a configuration for blocking web mail from Apache from
> > accessing Postfix. I think it was something like: !www or something
> > like that. I forgot to write it down and now I cannot locate it.
> > Does anyone
On Mon, 2011-06-27 at 18:25:18 -0400, Jerry wrote:
> OK, I found it:
>
> authorized_submit_users = !apache,static:all
>
> Since I am running Apache on FreeBSD with user/group ownership of "www"
> I assume I would use this instead:
>
> authorized_submit_users = !www, static:all
Yes, and inciden
Jerry:
[ Charset UTF-8 unsupported, converting... ]
> On Mon, 27 Jun 2011 18:06:19 -0400 (EDT)
> Wietse Venema articulated:
>
> > Jerry:
> > > I saw a configuration for blocking web mail from Apache from
> > > accessing Postfix. I think it was something like: !www or something
> > > like that. I f
On Mon, 27 Jun 2011 18:38:58 -0400
Sahil Tandon articulated:
> On Mon, 2011-06-27 at 18:25:18 -0400, Jerry wrote:
>
> > OK, I found it:
> >
> > authorized_submit_users = !apache,static:all
> >
> > Since I am running Apache on FreeBSD with user/group ownership of
> > "www" I assume I would use t
greetings
does anyone have a good current header check they would be willing to share,
specifically Im looking for correct fundamentals like date and time?
-j
Le 27/06/2011 01:35, Noel Jones a écrit :
> On 6/26/2011 3:12 PM, Ralf Hildebrandt wrote:
>> * Georg Sauthoff:
>>
Since procmail(1), and other utilities need to be able to forward mail
while retaining the original envelope sender address, restricting the
envelope sender address in se
Le 28/06/2011 00:25, Jerry a écrit :
> On Mon, 27 Jun 2011 18:06:19 -0400 (EDT)
> Wietse Venema articulated:
>
>> Jerry:
>>> I saw a configuration for blocking web mail from Apache from
>>> accessing Postfix. I think it was something like: !www or something
>>> like that. I forgot to write it down
Le 28/06/2011 01:54, jeffrey j donovan a écrit :
> greetings
> does anyone have a good current header check they would be willing to share,
> specifically Im looking for correct fundamentals like date and time?
>
just forget about that.
if you're after date&time, use spamassassin, which takes a
Le 27/06/2011 21:14, Bartłomiej Solarz-Niesłuchowski a écrit :
> Good mornig!
>
> We want to block any mail locally seded from apache account.
>
> Many years ago we set in main.cf:
> authorized_submit_users = !apache,static:all
> but after upgrading postfix from 2.7.4 to 2.8.3
> this option sudd
On 6/27/2011 6:54 PM, jeffrey j donovan wrote:
greetings
does anyone have a good current header check they would be willing to share,
specifically Im looking for correct fundamentals like date and time?
-j
Years ago this used to be useful, but not anymore. The false
positive rate is fairly
On Jun 27, 2011, at 9:16 PM, Noel Jones wrote:
> On 6/27/2011 6:54 PM, jeffrey j donovan wrote:
>> greetings
>> does anyone have a good current header check they would be willing to share,
>> specifically Im looking for correct fundamentals like date and time?
>>
>> -j
>
> Years ago this used
29 matches
Mail list logo
