> If it's backscatter, it should be coming from <>, not a "valid company
> address". Please show your logs during delivery of the alleged backscatter.
>
I don't have anymore the logs from Postfix and I'm not sure if it
really is a backscatter problem, all I have right now is the
following:
-
> -Original Message-
> From: owner-postfix-us...@postfix.org
> [mailto:owner-postfix-us...@postfix.org] On Behalf Of jan gestre
> Sent: Wednesday, 27 May 2009 5:00 PM
> To: postfix-users@postfix.org
> Subject: Re: BackScatter Problem
>
> > If it's backscatter, it should be coming from
Hi,
> From: mouss
> what you could do is run a script that
> - checks the message size. if it's too large, store it somewhere for review
> - else, run sendmail
>
> in any case, don't bounce without some sort of verification (some
> anti-spam checks or a manual review).
>
> If you are willing
Thank you a lot.
I didn't know that solution.
Le mardi 26 mai 2009 à 07:34 -0500, Noel Jones a écrit :
> Nicolas Michel wrote:
> > Thanks for your help. But that tips is not really what I'm searching
> > for. The class restriction is a global restriction : some users have
> > full permission (
jan gestre wrote:
I don't have anymore the logs from Postfix and I'm not sure if it
really is a backscatter problem, all I have right now is the
following:
The message snippet is of no use. Can you post the full headers? That
and a corresponding log entry should clear things up.
From what
I noticed that postfix doesn't recognize NetBSD 5:
This is as far as makedefs goes..
makedefs: NetBSD.4*) SYSTYPE=NETBSD4
as a test, I did this:
makedefs: NetBSD.5*) SYSTYPE=NETBSD4
and it compiled just fine.
-JD
J.D. Bronson:
> I noticed that postfix doesn't recognize NetBSD 5:
>
> This is as far as makedefs goes..
> makedefs: NetBSD.4*) SYSTYPE=NETBSD4
>
> as a test, I did this:
> makedefs: NetBSD.5*) SYSTYPE=NETBSD4
>
> and it compiled just fine.
Postfix will recognize NetBSD 5 after it has bee
I try to limit auth mech in postfix 2.6.1 on FreeBSD 6.4. For this
I've added to main.conf:
smtp_sasl_mechanism_filter = plain, login
But simple test by telnet shows following:
Connected to x.x.x.x.
Escape character is '^]'.
220 xxx.xxx.com.ua ESMTP Postfix
ehlo 1
250-xxx.xxx.com.ua
250-PIPELINI
* Zero Zeibov :
> I try to limit auth mech in postfix 2.6.1 on FreeBSD 6.4. For this
> I've added to main.conf:
>
> smtp_sasl_mechanism_filter = plain, login
smtpd_sasl_mechanism_filter = plain, login
--
Ralf Hildebrandt
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-15
Here's filtered output from postconf
# postconf | grep sasl_mechanism
lmtp_sasl_mechanism_filter =
smtp_sasl_mechanism_filter = plain, login
I didn't find option smtpd_sasl_mechanism_filter on postfix manual
2009/5/27 Ralf Hildebrandt :
> * Zero Zeibov :
>> I try to limit auth mech in postfix 2.
Wietse Venema wrote:
Postfix will recognize NetBSD 5 after it has been verified to fully
support the existing Postfix features.
One known bug is that file descriptor passing requires different
code on NetBSD than on the other 64-bit systems. This breaks Milters,
the SMTP connection cache, and
On Wed, 27 May 2009, kj wrote:
> jan gestre wrote:
>> I don't have anymore the logs from Postfix and I'm not sure if it
>> really is a backscatter problem, all I have right now is the
>> following:
>
> The message snippet is of no use. Can you post the full headers? That
> and a corresponding
On Tue, 26 May 2009, LuKreme wrote:
> On 26-May-2009, at 17:39, Lists wrote:
>> As part of my mail system I am using postgrey.
>>
>> When stuff is stopped at the gate (so to speek) i.e. it doesn't even
>> get into the the system is there a log kept of this?
>
> postgrey logs to the maillog. line
Zero Zeibov:
> I try to limit auth mech in postfix 2.6.1 on FreeBSD 6.4. For this
> I've added to main.conf:
>
> smtp_sasl_mechanism_filter = plain, login
Read carefully.
AS DOCUMENTED, this applies to the Postfix SMTP CLIENT.
Wietse
> But simple test by telnet shows following:
>
> Co
On Wed, May 27, 2009 at 02:11:26PM +0300, Zero Zeibov wrote:
> I didn't find option smtpd_sasl_mechanism_filter on postfix manual
It does not exist. Server-side SASL mechanism lists are set in
the server's SASL configuration file.
--
Viktor.
Disclaimer: off-list followups get on-list r
On Wed, May 27, 2009 at 12:35:28AM -0700, Trigve Siver wrote:
>
> Hi,
>
> > From: mouss
>
> > what you could do is run a script that
> > - checks the message size. if it's too large, store it somewhere for review
> > - else, run sendmail
> >
> > in any case, don't bounce without some sort of
Wietse:
> Curtis:
> > > This is safe only when the maildrop queue is "stopped", that is,
> > >
> > > 1) No submissions with the Postfix sendmail command while these
> > >files are in the maildrop directory, otherwise mail will be
> > >lost.
I'm still trying to understand why mail would b
On Wed, May 27, 2009 at 11:05:50AM -0600, Curtis wrote:
> I'm still trying to understand why mail would be lost. Since it would be
> impossible for the Postfix sendmail command to overwrite one of these files
> due to a filename conflict (we write the files using filenames that would
> never be u
Hi list !
I run a python script which is a mail2news gateway for usenet postings.
This script allows people without a proper usenet client to post to
newsgroups by email client .
The procedure is to write the interested newsgroups where to post to in
the user part of the email address plus a date f
Curtis:
> Wietse:
> > Curtis:
> > > > This is safe only when the maildrop queue is "stopped", that is,
> > > >
> > > > 1) No submissions with the Postfix sendmail command while these
> > > >files are in the maildrop directory, otherwise mail will be
> > > >lost.
>
>
> I'm still trying to
Victor Duchovni:
> the same time. If "postsuper" (which runs durin "reload") is to be
> allowed to race against your code, your mode 0700 file names have to
> match the usual Postfix hex file names:
>
>
>
> this is an undocumented interface, so you have to be willing to review
> any Postfi
I've already been down this road. Forget about playing with queue file names,
permissions and all the other "back door" methods of accessing the queues, and
use the utilities supplied.
Calling an external app to make things happen isn't quite as elegant as being
able to drop files where you want t
On Wed, May 27, 2009 at 02:25:24PM -0400, Wietse Venema wrote:
> Victor Duchovni:
> > the same time. If "postsuper" (which runs durin "reload") is to be
> > allowed to race against your code, your mode 0700 file names have to
> > match the usual Postfix hex file names:
> >
> >
> >
> > this
Victor Duchovni:
> On Wed, May 27, 2009 at 02:25:24PM -0400, Wietse Venema wrote:
>
> > Victor Duchovni:
> > > the same time. If "postsuper" (which runs durin "reload") is to be
> > > allowed to race against your code, your mode 0700 file names have to
> > > match the usual Postfix hex file names:
> >
> > Sorry, the RELEASE_NOTES don't discuss undocumented behavior.
> >
>
> By "review", I meant "read the code"... Postfix is open-source
> software, if they are willing to take on the burden of supporting local
> "customization" (their injection system can be viewed as a
> customization),
> an
Wietse:
> Without stopping Postfix, importing files safely could be done with
> a new "postdrop" command-line option. This would be a privileged
> option, since real queue files contain records that users are not
> allowed to provide.
That would be terrific... and would seemingly resolve all conc
> > The problem is, that I can send mail to the listener on
> > 192.168.xxx.xxx on port 25, but that it is passed to the
> > postfixfilter. My question is, how can I completely turn off
> > contentfiltering for all mail received on 192.168.xxx.xxx and why
> > does the "-o content_filter=" optio
On Wed, May 27, 2009 at 01:47:27PM -0600, Curtis wrote:
> For those wondering why we can't just commit to only using the provided
> utilities to manipulate queue files, it's because we are giving individual
> users the ability to view messages that were placed in the hold queue and
> release them
Wietse Venema:
> The Postfix queue is designed to be a short-term message store
> where files can be located quickly based on their name alone.
>
> I don't think it is a good idea to re-purpose this design for
> routine long-term storage of messages waiting for approval, or to
> break the design b
The Postfix queue is designed to be a short-term message store
where files can be located quickly based on their name alone.
I don't think it is a good idea to re-purpose this design for
routine long-term storage of messages waiting for approval, or to
break the design by making file locations dep
* Zero Zeibov :
> I try to limit auth mech in postfix 2.6.1 on FreeBSD 6.4. For this
> I've added to main.conf:
>
> smtp_sasl_mechanism_filter = plain, login
This does not apply to the SMTP server smtpd, but only to the SMTP client
smtp.
> But simple test by telnet shows following:
>
> Connecte
On 27-May-2009, at 05:29, Sahil Tandon wrote:
On Tue, 26 May 2009, LuKreme wrote:
On 26-May-2009, at 17:39, Lists wrote:
As part of my mail system I am using postgrey.
When stuff is stopped at the gate (so to speek) i.e. it doesn't even
get into the the system is there a log kept of this?
p
On Wed, 27 May 2009, LuKreme wrote:
> On 27-May-2009, at 05:29, Sahil Tandon wrote:
>> On Tue, 26 May 2009, LuKreme wrote:
>>
>>> On 26-May-2009, at 17:39, Lists wrote:
As part of my mail system I am using postgrey.
When stuff is stopped at the gate (so to speek) i.e. it doesn't eve
According to 'postconf -d', myhostname is set to genex.localdomain where genex
is an arbitrary name I chose for a hostname when I installed Debian Lenny.
When I look in /etc/postfix/main.cf,
myhostname = genex.example1.com
Is this a normal discrepancy?
Is it even neccessary to have a hostname
* Tim Legg :
>
> According to 'postconf -d',
Which displays the default, not what you set...
--
Ralf Hildebrandt
Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155
http://www.computerbeschimpfung.de
Wenn etwas Abstoßendes modern wird, ist es sofort anziehend.
Tim Legg wrote:
According to 'postconf -d', myhostname is set to genex.localdomain where genex
is an arbitrary name I chose for a hostname when I installed Debian Lenny.
When I look in /etc/postfix/main.cf,
myhostname = genex.example1.com
postconf -d shows compiled-in defaults, not your setti
Tim Legg:
>
> According to 'postconf -d', myhostname is set to genex.localdomain where g
>-enex is an arbitrary name I chose for a hostname when I installed Debian Len
>-ny.
As documented, "postconf -d" does not show what is in main.cf.
> When I look in /etc/postfix/main.cf,
> myhostname = genex
gabriele a écrit :
> Hi list !
> I run a python script which is a mail2news gateway for usenet postings.
> This script allows people without a proper usenet client to post to
> newsgroups by email client .
> The procedure is to write the interested newsgroups where to post to in
> the user part of
Terry:
> >
> > For those wondering why we can't just commit to only using the
> provided
> > utilities to manipulate queue files, it's because we are giving
> individual
> > users the ability to view messages that were placed in the hold queue
> and
> > release them up to 30 days after the messages
LuKreme wrote:
On 26-May-2009, at 17:39, Lists wrote:
As part of my mail system I am using postgrey.
When stuff is stopped at the gate (so to speek) i.e. it doesn't even
get into the the system is there a log kept of this?
postgrey logs to the maillog. lines look like this:
May 26 16:27:18
Viktor:
> If the files are guaranteed to only have a single recipient at the
> point
> in your processing stream at which they are "held", you don't have to
> do
> anything nearly so complex. Just retain the file's original name and
> inode, by renaming it into a suitable directory tree in the same
Curtis:
> In the mean time, it seems like using doing "postsuper -r" to re-activate
> old queue files would be a good alternative. Hopefully that resolves the
> expiration cycle issue that is caused when you inject a queue file directly
> into the maildrop queue?
If that's "postsuper -r" from hol
Hello all,
This is my first post.
I'm using postfix 2.3.3 on some Centos 5.x boxes strictly to send mail
for alerting purposes. I've got relaying setup to go to our main smtp
server which is running FreeBSD 6.x and postfix. What I'm trying to do
is for the outgoing messages to show the ho
Ausmus, Matt:
> Hello all,
>
> This is my first post.
>
> I'm using postfix 2.3.3 on some Centos 5.x boxes strictly to send mail
> for alerting purposes. I've got relaying setup to go to our main smtp
> server which is running FreeBSD 6.x and postfix. What I'm trying to do
> is for the outgoing m
44 matches
Mail list logo
