il in the instance that comes from Amavis
for being able to know which FILTER action should I use?.
I know there's a possibility of using smtpd sasl authenticated header but I
don't really trust in that way...
Any ideas? :)
Best regards,
--
Egoitz Aurrekoetxea
Hi Wietse,
Thank you so much for the advise...
I'm planning how to implement all this :)
Best regards,
El mar., 13 oct. 2020 a las 20:20, Wietse Venema ()
escribió:
> Egoitz Aurrekoetxea:
> > Good afternoon,
> >
> > Can a Postfix instance have a destination based
)?. But, later the mandatory filter action for Amavis, should
happen for everybody. I say this, because I know that only one FILTER
action can exist...
How do you usually do this?. Or you just pass DMARC for every users?.
Regards,
--
Egoitz Aurrekoetxea
one
message at the same time to a mailbox is that possible? without
suffering from a slow delivering queue?.
Best regards,
--
Egoitz Aurrekoetxea
On Thu, 12 Jan 2012, Stan Hoeppner wrote:
On 1/11/2012 11:15 PM, Al Zick wrote:
Hi,
For a while we ran Qmail. Qmail would accept all emails regardless,
creating a very serious backscatter problem. Of course, switching to
Postfix with it configured to only accept emails for our recipients
fix
On Tue, 8 Nov 2011, Stan Hoeppner wrote:
Apologies everyone. I got my threads confused. I thought I was
replying to the "reject or discard outgoing mail" thread. (palm to
forehead) This thread has nothing to do with spambots.
No problem ;)
--
Stan
On Wed, 9 Nov 2011, Martin Strand wrote:B>
For what it's worth, here's a similar policy daemon that I've been using for
a few years.
- it only checks the quota if MAIL FROM has a SIZE parameter (which is not
always the case)
- it executes 'postmap' on each request to find the proper maildir
On Tue, 8 Nov 2011, Egoitz Aurrekoetxea Aurre wrote:
On Tue, 8 Nov 2011, Stan Hoeppner wrote:
http://postfixquotareject.ramattack.net. It's a postfix policy daemon
which allow mail to be rejected at smtp dialogue when mailbox are
overquota... can work from the own mailbox machine or
On Tue, 8 Nov 2011, Stan Hoeppner wrote:
http://postfixquotareject.ramattack.net. It's a postfix policy daemon
which allow mail to be rejected at smtp dialogue when mailbox are
overquota... can work from the own mailbox machine or from the own
mailscanning machine farm asking to a daemon in ma
On Mon, 7 Nov 2011, Leslie León Sinclair wrote:
Thanks again, and sorry the thread, I´am stacked here. Almost near the
solution.
Best regards.
You could too take a look to Postfix Quota Reject.
http://postfixquotareject.ramattack.net. It's a postfix policy daemon
which allow mail t
El 23/01/2011, a las 22:02, mouss escribió:
> Le 19/01/2011 13:56, J4 a écrit :
>> Hi there,
>>
>>I set-up Postfix to enforce quotas using this in the main.cf:
>>
>> postconf -n | grep virtual
>> virtual_alias_maps =
>> proxy:mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf,
>> proxy:mysq
You could take a look too to postfix quota reject project,
http://postfixquotareject.ramattack.net/. It's a postfix policy code which
enforces quotas in maildir and cyrus mailboxes. It's another option and works
with either a normal mail server with postfix installed or with an isp
structure in
Uqlev advised me to use 2048 bit certs... after doing that... just the mail
client has limited to 128 bit session keys with thunderbird for example no
problem to get 256 bit session keys.
Thanks bye!!
El 15/10/2010, a las 11:16, Egoitz Aurrekoetxea Aurre escribió:
> Hi all,
>
Hi all,
How could I force in postfix to cypher with 256 bits instead of just the 128
minimum default??
Thanks a lot!!
Hi,
The only officially supported quota enforcing method is for mailbox mailboxes .
There are too other quota limit software like vda or postfixquotareject wich
can achieve you're goal. Vda was that you seem to have installed... another
method is postfixquotareject wich just works fine too but
Hi!,
Try Postfix quota reject it sais at the reject moment wich users are over quota
and the sender can easily know whose of the users should remove from the
recipient list for the mail to be able to be sent. It's comfortable, scalable
and IMHO works nice...
Bye!!
http://postfixquotareject.ra
El 14/11/2009, a las 14:55, Wietse Venema escribió:
Please do not top-post. See wikipedia for background information.
Egoitz Aurrekoetxea Aurre:
Hi,
Wietse, what do you want to say with this? any problem for running
some postfix release on freebsd?
Perhaps I have not received the previous
Hi,
Wietse, what do you want to say with this? any problem for running
some postfix release on freebsd?
Perhaps I have not received the previous mail...
El 14/11/2009, a las 14:17, Wietse Venema escribió:
Sahil Tandon:
+#if (__FreeBSD_version >= 702104 && __FreeBSD_version <= 80) \
+
And I could say too that if you decide doing more than just
reporting... I mean enforcing quotas rejecting mail for overquota
users or rejecting mails wich will rise the quota limit for the
mailbox and you're using cyrus or maildir++ mailboxes (courier, qmail
pop3d, dovecot...) try my proje
Hi,
I think outgoing scans are a little different. You have some
advantages and disadvantages respect incoming mail scanning.
Advantages are that you know you're users and more or less what they
do or you have it controlled with some scripts. So you can
identify easier when a user is
Hi Marty,
Dovecot uses maildir++ mailboxes??. If so you could use my project :
Postfix quota reject. It works rejecting mail for overquota mailboxes
that are maildir++ or cyrus sort of mailbox. I have programmed it
thinking on ISP mail hosting services; allows you the possibility of
rejec
Hi,
I have started working on a new outgoing mail moderator daemon. It
controls the outgoing mail for seeing if it seems to be legal or not
just looking you're normal behave, and some other items and will
determine if mail is spammy or not (without looking at the content of
the mail... so
hatever and till you don't know exactly what they're doing to
allow them to relay through you're server.
This are my advises :).
2.0.0 Bye
El 19/09/2009, a las 17:56, Egoitz Aurrekoetxea Aurre escribió:
No matter where they are... do a script that takes users from
wherev
This option :
"I was just thinking about another option. I might be able to make a
small program that analyzes the logfiles for each server, puts it in a
database with a timestamp, and then make it a POP/IMAP before SMTP.
That would be secure enough right?"
Is not valid for doing all you'
Hi,
Just create sasl account for allowing to relay to those authenticated
users. But be very careful on what you're users send though it because
if you're custommers start sending mail considered spam in two weeks
or less you're outgoingn servers are dead because no server will want
to t
I set 40 seconds for policy time limit and too for
smtpd_policy_service_max_ttl I telneted the smtpd later after
data
command I waited 2 minutes (for exceeding nice the 40 seconds) for
Perhaps surprisingly, Postfix starts a new policy daemon when a
policy daemon process terminates too s
When you run the policy service under the Postfix spawn daemon,
terminate when a read operation returns an end-of-file indication.
Wietse
Hi Wietse,
Have just read this... yep this is just what I do, I read from input
fd with <> wich in perl does the trick. I didn't remember I exite
and how could I know that the smtp server has disconnected from the
policy server? what does postfix send for knowing it?
When you run the policy service under the Postfix spawn daemon,
terminate when a read operation returns an end-of-file indication.
Wietse
Hi Wietse,
Have just
El 12/09/2009, a las 15:38, Wietse Venema escribió:
Egoitz Aurrekoetxea Aurre:
When you are running the policy service under the spawn daemon:
1) The time limit BEGINS after an SMTP server connects to the
policy server port, when a new policy daemon process is created.
Thus, an SMTP server
I have resent this message to just Wietse... but I wanted to send it
to whole mailing list. So I do.
When you are running the policy service under the spawn daemon:
1) The time limit BEGINS after an SMTP server connects to the
policy server port, when a new policy daemon process is crea
Hi,
I'm pretty sure about this but... I prefer asking for being totally
sure. Hey mates imagine a policy daemon has a (server time limit) time
limit of 3600 seconds... like hasn't arrived the max_idle time...
spawn doesn't close it and now it's near to it's time_limit
imagine that
Hi all!!
I'm proud to announce the new version of Postfix Quota Reject. This
new version enters several improvements over the old code and it's
oriented to ISPs for allowing to reject mail at smtp dialogue from the
own incoming mail scanning machines and avoiding bounces
(backscattering d
es <[EMAIL PROTECTED]>
> Egoitz Aurrekoetxea wrote:
>
>>
>> I have been talking about smtp client threads of postfix... but imagine
>> now (for understanding better...) amavis for example... you launch two
>> amavis processes as you specified in amavisd.conf. So
>
> For Wietse :
> I agree, assuming that he is talking about a small number of sending
> processes.
>
> If, on the other hand, he is talking about a small number of
> receiving processes,
Nope I was talking about smtp client proccess for send from postfix queue
to another smtp servers (Outs
>
> Yes, adjust the maxproc column in master.cf to adjust the total number of
> daemons a particular transport can spawn. If the maxproc column is "-",
> then default_process_limit is used.
Ok but this couldn't cause that if for example you have 20 messages to be
redirected for a transport (by t
Hi all!,
I wanted to ensure postfix can only use the number of transport daemons I
specify for it... for example if I have 10 smtp client daemons I wanted the
queue manager to know I only have 10 smtp daemons and should organize
deliveries knowing that can only use 10 (for avoiding unknown mail tr
Hi all!,
I wanted to ensure postfix can only use the number of transport daemons I
specify for it... for example if I have 10 smtp client daemons I wanted the
queue manager to know I only have 10 smtp daemons and should organize
deliveries knowing that can only use 10 (for avoiding unknown mail tr
Hi all!,
I wanted to ensure postfix can only use the number of transport daemons I
specify for it... for example if I have 10 smtp client daemons I wanted the
queue manager to know I only have 10 smtp daemons and should organize
deliveries knowing that can only use 10 (for avoiding unknown mail tr
38 matches
Mail list logo
