ber
# postscreen_cache_cleanup_interval = 0
# on ALL instances if you DON'T use backup.
Thank you very much for every hints.
Regards
Marco
Wietse Venema porcupine.org> writes:
> Please show the problem without logs from other servers.
I'm sorry for word wrap and mix. This is an example:
https://docs.google.com/open?id=0B-09bt7bbY_0MHU4bGduZTFWeGc
Thanks again
Marco
ueue_id and counting the different "orig_to" fields, where they are
present. So it is possible, but the operation is quite complex.
Many thanks
Cheers
Marco
is as the relayhost and
apply the headers_check in this VM that will be used only for Internet
outgoing traffic.
Is there any other solution that will not need a new VM?
Tnx
Marco
Il 29. 10. 15 14:38, Wietse Venema ha scritto:
> Marco:
>> Hello all.
>>
>> I'm using postfix since at least 20 years and I could always find a
>> satisfactory solution to my problems.
>>
>> However I have an now an issue with the filtering
Il 29. 10. 15 17:33, Wietse Venema ha scritto:
> Marco:
>> A Milter could be also an option in the future, with the target of
>> "sanitizing" the mails by replacing the original header with a new one,
>> ensuring no internal information leakage (i.e. including t
Il 29. 10. 15 18:09, Wietse Venema ha scritto:
> Wietse:
>> smtp_header_checks has a replace option.
> Marco:
>> The issue I have is that smtp_header_checks is unable to distinguish
>> between mail sent to intranet destinations (the VMsrunning the services)
>> a
s question, it really
depends from where your servers are located.
Marco
Il 20. 02. 16 15:01, Sebastian Nielsen ha scritto:
> I readed that on wikipedia, and readed the sources, and one thing I can say,
> is that the source is heavily misinterpreted. They refer to physical mail,
> an
o reflect the MX records. Is
there any way of changing the host name sent in the 250 ehlo answer
without having to modify the definition of "myhostname", I would prefer
to keep identical to the internal DNS name?
Tnx for the answer and have a nice day
Marco
e internal name of the bastion host, pointing to an external address,
and change the MX record accordlying.
Tnx and have a nice day
Marco
Il 29. 02. 16 19:27, Wietse Venema ha scritto:
> Marco:
>> Hello.
>>
>> I have a small security concern with my external SMTP server:
>
rity_level = $smtpd_tls_security_level
postscreen_upstream_proxy_protocol =
postscreen_upstream_proxy_timeout = 5s
postscreen_use_tls = $smtpd_use_tls
postscreen_watchdog_timeout = 10s
postscreen_whitelist_interfaces = static:all
mail_version = 3.1.0
Thank you very much
Best Regards
Marco
Il 23/05/2016 10:42, Marco ha scritto:
2016-05-20T15:49:07.384799+02:00 mx postfix/dnsblog[1304]: addr
157.56.110.148 listed by domain wl.mailspike.net as 127.0.0.17
Ah, I understood.
wl.mailspike.net as 127.0.0.17 doesn't match the rule:
wl.mailspike.net=127.0.0.[18..20]*-1
but dn
with some filtering for the obvious cases
as you propose.
Have a nice day
Marco
Il 16. 07. 16 07:25, Michael Fox ha scritto:
> I'd like to be able to reject mail that contains encrypted content. This is
> to satisfy US FCC rules against encrypted content on amateur radio
> frequen
path not allowed
I searched in the mans and documentation but i didn't find a solution;
is it possible to deny routed senders like user@domain1@domain2?
Is it right that user@domain1@domain2 is not syntactically correct and
the correct syntax is "@ONEdomain,@TWOdoamin:JOE@THREEdomain" ?
Thanks
Marco
always permitted for all logins, even if it doesn't match the
smtpd_sender_login_maps table.
reject_authenticated_sender_login_mismatch works as expected for all
other envelopes.
Could you help me to know why?
Thank you very much
Marco
2bounce_notice_recipient = a...@example.com
alias
installation, and then
collect the policyd_spf answers to verify the efficieny of SPF for my
sites (currently I see a lot of DONNO even for Google)
Tnx
Marco
Hello.
Tnx, however I'm not using the python version but the compiled one, and
there is nowhere a policyd-spd.conf file nor a man page.
Marco
Il 10. 05. 17 16:49, Dominic Raferd ha scritto:
On 10 May 2017 at 15:27, marco <mailto:marco.brign...@marcobaldo.ch>> wrote:
*
*default_destination_recipient_limit = 25
*
Of course this slows down the delivery, however it is not a big problem
unless all the recipients are handled by a restricted number of MX (and
this is not usual)
I'm now running less intensive mail servers, so maybe some tuning is
need in this phase.
Marco
Il 1
n not happy with this.
Marco
have a lot of mail users, as
one single mail with a lot of recipients will slow-down the delivery
until all the "sub-deliveries" are handled for a specific server.
Marco
Il 19. 05. 17 16:02, richard lucassen ha scritto:
On Fri, 19 May 2017 15:52:05 +0200
marco wrote:
So if I unde
e also these domains in a file,
mysql, tcp or ldap... It should be nice if a future release of Postfix
could support "type:table" on "masquerade_domains".
Thank you very much
Marco
y
"!pattern" to exclude a name from the list.
Would that work for you?
Yes, of course.
Many thanks for considering this.
Marco
is some specification to
always accept these recipients, or if I made some mistakes in my conf.
mail_version = 3.3.2
Thank you very much
Marco
R-DAEMON@, even if you change the
empty_address_recipient.
As you suggest, I think I have to define some transport for
MAILER-DAEMON recipient address. Otherwise I get double-bounce.
Warm Regards
Marco
Hello Everybody
I wan't to have my local recipeints checked against my Active Directory.
So I have created the .cf file with the LDAP parameters:
bind_dn = u...@domain.local
bind_pw = **
server_host = 192.168.8.254
#Global Catalog port
server_port = 3268
search_base = DC=doma
ix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Im Auftrag von Patrick Ben Koetter
Gesendet: Samstag, 28. August 2010 18:25
An: Postfix Users
Betreff: Re: local_recipient_maps with LDAP
* Marco Rebsamen :
> I see
> If i got multiple domains, what do i do ?
> Somet
Ok, I'm really confused about that LDAP lookup stuff :-/
What I want to do is to check if an address to which a message is addressed
really exists.
I'm currently using this script for local receipient checks:
bind_dn = j...@hive.loc
bind_pw =
server_host = 192.168.8.254
#Global Catalog po
-Ursprüngliche Nachricht-
Von: Victor Duchovni [mailto:victor.ducho...@morganstanley.com]
Gesendet: Montag, 30. August 2010 21:18
An: Marco Rebsamen
Cc: postfix-users@postfix.org
Betreff: Re: local_recipient_maps with LDAP
On Mon, Aug 30, 2010 at 08:50:33PM +0200, Marco Rebsamen wrote
prüngliche Nachricht-
Von: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Im Auftrag von Victor Duchovni
Gesendet: Montag, 30. August 2010 21:54
An: postfix-users@postfix.org
Betreff: Re: local_recipient_maps with LDAP
On Mon, Aug 30, 2010 at 09:46:26PM +0200, Marco Rebs
>> I added all the non-local domains to the parameter
virtual_alias_domains
>> and set virtual_alias_maps to ldap:/etc/postfix/virtual.cf
> Do you understand what virtua alias domains are for?
I thought I would...
>> I tested it with postmap -q and it worked.
> What does "worked" mean?
I got the
ix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
Im Auftrag von Victor Duchovni
Gesendet: Dienstag, 31. August 2010 21:29
An: postfix-users@postfix.org
Betreff: Re: local_recipient_maps with LDAP
On Tue, Aug 31, 2010 at 08:07:52PM +0200, Marco Rebsamen wrote:
> > Probably "mail&
I have a barracuda server that receives mails, filter them and forward to a
linux system running postfix.
Both machine have a public IP (static).
The linux system is configured to be used as SMTP for sasl authenticated
users as well, besides to be used as SMTP for the people on $mynetworks
(perm
* Wietse Venema [2009-11-26 12:20:19 -0500]:
> Marco Giardini:
> > I have a barracuda server that receives mails, filter them and forward to a
> > linux system running postfix.
> >
> > Both machine have a public IP (static).
> >
> > The linux system is
Hi,
I'm trying to configure virtual vacation on my server.
In documentation I see which I do insert similary value in transport
vacation:[autoreply.mydomain.com]
What is the autoreply.mydomain.com?
It's same of mx record?
Thank you
Hi,
I have configured virtual vacation like this:
In master.cf:
--
vacationunix - n n - - pipe
flags=Rq user=vacation argv=/var/spool/postfix/vacation/vacation.pl -f
${sender} -- ${recipient}
--
In main.cf:
--
t
relevant lines of master.cf, and the output of postconf -n are below.
Any help to figure out what happened/is still happening and fix it is very
welcome, thanks.
Marco
[root@newvps postfix]# grep smtp master.cf | grep -v '^#'
smtp inet n - n - - smtpd
in addition to what I just wrote, I realized only in this instant that an
email from one of two IPs in mynetworks:
mynetworks = 127.0.0.0/8, ip.1, ip.2 (THESE ARE FIXED IPS OF TWO
is rejected with this message in the log:
master.cf.orig:smtp inet n - n - - sm
ted at the beginning
of the thread, to improve the setup, is still very welcome, if anybody
feels like it!
Marco
.
10.1.1.1 -> FROM: j...@test.co.uk
10.1.1.2 -> FROM: m...@test.co.uk
I saw many things going around filters and the check_client_access but I
didn't get if it's possible or not.
Appreciate any help! Thank you :-)
All the best,
Marco
ng side, the
VERP-ed address in the return-path field.
My issue is that in the log lines following "XVERP" I can only see the
original MAIL FROM address...
My question is about whether there is a way to log the VERP-ed MAIL FROM,
so to be sure about which translation happened.
Thank you very much in advance
Marco
Hello Wietse,
On Tue, Apr 20, 2021 at 5:48 PM Wietse Venema wrote:
> Marco Pizzoli:
> > Hi all,
> > I have successfully configured VERP to work with my Postfix instance.
> >
> > I see the logs and I effectively see
> > [truncated] /smtpd[999]: unknown[x.x.x.x]:
Hello,
+1 for this Request for Improvement.
I also faced this need.
Changing the machine solver was, unfortunately, not an option.
Thanks
Marco
On Thu, Apr 22, 2021 at 12:21 PM Simon Wilson
wrote:
> Is there a way to make Postfix/postscreen use a specific DNS server?
>
> Reaso
On Thu, Apr 22, 2021 at 4:37 PM Benny Pedersen wrote:
> On 2021-04-22 12:58, Marco Pizzoli wrote:
> > Hello,
> > +1 for this Request for Improvement.
> > I also faced this need.
> >
> > Changing the machine solver was, unfortunately, not an option.
>
> w
On Thu, Apr 22, 2021 at 5:21 PM Benny Pedersen wrote:
> On 2021-04-22 16:44, Marco Pizzoli wrote:
>
> > I am afraid you did not get my point.
>
> i dont know your solution then
>
> rpz and qname can be problematic
>
> https://labs.ripe.net/author/wouter_de_vries/ma
ter =
relayhost = [smtp.myhost.de]
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl/sasl_passwd
smtp_sasl_security_options = noanonymous
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
What information should I provide here further?
BR
Marco
-BEGIN PGP SIGNATURE-
Ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/20/2015 11:31 PM, k...@rice.edu wrote:
> Hi Marco,
>
> What do your postfix logs say for one of the duplicated
> deliveries?
I've attached the piece of the mail.info where the duplicate occurs
> When I have seen duplica
On 10/20/2015 11:31 PM, wie...@porcupine.org wrote:
Marco Stoecker:
-- Start of PGP signed section.
Hi,
I do have a combination of postfix and mailman and use postfix as a
relayhost. I get all the mails for mailman via fetchmail. The whole
system is Debian 8 with its packages for postfix
On 10/21/2015 12:51 PM, Wietse Venema wrote:
> Marco Stoecker:
>>> All the evidence that you need is logged by Postfix and mailman:
>>> track down a duplicate delivery back to the source and look for
>>> delivery errors.
>>
>> Will do a double-check of all
On 10/23/2015 01:26 AM, Wietse Venema wrote:
> Marco Stoecker:
>>> You need to find the records where the same message is delivered
>>> more than once to the same recipient, then look for all the records
>>> with the same Postfix QUEUE ID. That will show if the d
On 10/27/2015 05:06 PM, Viktor Dukhovni wrote:
On Tue, Oct 27, 2015 at 08:45:20AM +0100, Marco Stoecker wrote:
Here is the log, where postfix got the original message (which was
sent
to 5 mailing lists) and handed over to mailman (which is done 5 times
with different postfix ID's).
No
On 10/27/2015 06:10 PM, Bill Cole wrote:
On 27 Oct 2015, at 12:40, Marco Stoecker wrote:
[...]
I do need some assistance, as this is very new for me.
Thx in advance.
So this is the "Received" header of 5 out of 5 messages. I can't see
where the duplication happend :
On 10/28/2015 01:09 AM, Viktor Dukhovni wrote:
On Tue, Oct 27, 2015 at 05:40:35PM +0100, Marco Stoecker wrote:
message1:
Delivered-To: vorstand@localhost
Received: from wakis02.local (localhost [IPv6:::1])
by wakis02.local (Postfix) with ESMTP id 98DC6269A;
Thu, 22 Oct 2015 10:40:43 +0200
ive "envelope 1 Received" to the relevant stanza of his
> .fetchmailrc file, telling fetchmail to skip the first Received header
> in fetched messages.
>
Thx Bill and Viktor!
as I discussed this topic in parallel in the mailman mailinglist, we
came there today also to the conclusion, that fetchmail is the root
cause, due to missing envelope information/maildrop capabilities.
Based on the Fetchmail docs 'envelope 1 Received' is only half of the
solution. I have to set an alias for the postfix mailserver in addition
cause fetchmail.log shows 'fetchmail: line rejected, mx.kundenserver.de
is not an alias of the mailserver'
How do I set the alias for the mailserver?
BR
Marco
On 10/29/2015 01:07 AM, Viktor Dukhovni wrote:
> On Thu, Oct 29, 2015 at 12:26:20AM +0100, Marco Stoecker wrote:
>
>> Thx Bill and Viktor!
>> as I discussed this topic in parallel in the mailman mailinglist, we
>> came there today also to the conclusion, that fetchmail i
rongly that no others will be checked if that
> fails, falling back to the inherently broken scanning of To/Cc headers.
>
> Based on that and the Fetchmail docs, it seems to me (imperfect as my
> analysis has proven to be...) that a likely solution is for the OP to
> add the directive "envelope 1 Received" to the relevant stanza of his
> .fetchmailrc file, telling fetchmail to skip the first Received header
> in fetched messages.
>
problem solved :-D
The indication of envelope 1 Received + aka mx.kundenserver.de in the
fetchmailrc was the solution.
Thx a lot
Marco
?
Thanks in advance
Marco
Hello Wietse,
On Fri, Nov 18, 2016 at 5:20 PM, Wietse Venema wrote:
> Marco Pizzoli:
> > Hi all,
> > I am sending a bunch of emails to a set of target domains.
> > I see that many of them are all served by the same MTA and this MTA is
> > limiting my sending because
information between Postfix instances?
I would really if you could share your personal experience on how to deal
in general with a scenario like this.
Thanks a lot in advance
Marco
Hi Wietse,
On Wed, Feb 18, 2015 at 1:23 PM, Wietse Venema wrote:
> Marco Pizzoli:
>
> > Is there a way to share this kind of information between Postfix
> instances?
>
> This is not implemented. Postfix by design can recover from a crash
> in any program except the mas
..@someotherdomain.com
should be relayed through that MTA, not directly to destination? (I am
almost sure it is, as I said my first problem is to know/use the right
search
terms for this function, sorry)
b) would it work, as far as SPF and DKIM are concerned? Would it cause
other problems?
Thanks,
Marco
ave to configure SASL auth and
> "smtp_sender_dependent_authentication = yes".
that's likely the next step, now I know where to go, thanks.
Marco
2015-02-24 13:44 GMT+01:00 Marco Fioretti :
> Hi Wietse!
>
> indeed, judging from this howto I found thanks to your pointer:
>
> http://kostja-osipov.livejournal.com/32518.html
>
> *sender_dependent_relayhost_maps *seems exactly what I need,
>
> > Does your system h
= may
smtp_sasl_tls_security_options = noanonymous
#, noplaintext
2015-02-24 18:22 GMT+01:00 Wietse Venema :
> Marco Fioretti:
> > 2015-02-24 13:44 GMT+01:00 Marco Fioretti :
> >
> > > Hi Wietse!
> > >
> > > indeed, judging from this howto I found th
virtual_mailbox_maps = hash:/etc/postfix/mymaps/vmailboxes.map
virtual_transport = procmail
virtual_uid_maps = static:5000
2015-02-24 19:18 GMT+01:00 Wietse Venema :
> Marco Fioretti:
> > Playing with several combination of the parameters suggested by Wietse
> > doesn't seem to make any diff
]: disconnect from localhost[127.0.0.1]
2015-02-24 19:28 GMT+01:00 Wietse Venema :
> Marco Fioretti:
> > here is postconf -n output:
>
> And the logging for this? You have changed settings.
>
> Wietse
>
> > alias_database = hash:/etc/aliases
> > alias_maps = has
weak spots.
Thanks all, again!
Marco
2015-02-24 19:51 GMT+01:00 Viktor Dukhovni :
> On Tue, Feb 24, 2015 at 01:44:01PM -0500, Wietse Venema wrote:
>
> > Marco Fioretti:
> > > right, sorry. Here is the logs of a new message sent just now, with the
> > > config
deally, a way to see the process name something
like "master-instance1"
i.e. rspamd does exactly this, assigning a different process name just to
explicit the "incarnation" of that process
Thank you in advance
Marco
POP3 server to Dovecot and making
use of its "sync" capabilities, but again I would appreciate hearing other
ideas...
Thank you in advance
Marco
duce the network dependency.
Worth a try.
Marco
.com/posts/20160516_port25_announces_release_of_powermta_v45r5/
I guess that the matter is to create a daemon receiving MX information from
smtp clients and making them available to the scheduler.
Thanks in advance
Marco
On Wed, Aug 2, 2017 at 6:57 PM, mark burdett wrote:
> That's true, as a work-around. Unfortunately we're talking about not just
> opening a new TCP connection but also reestablishing TLS, which means yet
> more RTT and CPU. So the increased concurrency will be significant and
> will require up
On Wed, Aug 2, 2017 at 7:44 PM, Viktor Dukhovni
wrote:
> On Wed, Aug 02, 2017 at 07:11:23PM +0200, Marco Pizzoli wrote:
>
> > Have a look at:
> > - smtp_tls_session_cache_database <-- this is the most important thing.
> I
> > suggest lmdb as the backing store
>
hieve the intended behaviour?
Thank you in advance for your help
Marco
; and transport it using a specific gateway?
>
I already asked in the past:
http://postfix.1071664.n5.nabble.com/Feature-request-MX-rollup-td90800.html
Marco
>
> Cheers,
> Peter
>
eventually get my sending slow
again...
Thank you in advance for everything you can develop in order to overcome
this limitation.
Marco
P.s. As a side note: the second limitation I face in using Postfix for bulk
email sending is the missing "MX-rollup" feature I already reported twic
Greetings,
I had my personal postfix/dovecot server, configured for some of my
own domains, running without problems on a linux VPS. For reasons
totally out of my control, I had to migrate everything to another VPS
two days ago, without notice, (details at the bottom if anybody is
interested...),
n my postconf -n output is still
very welcome (as I said, right now I am running postfix 2.10.1, while
the config files I am using are from a
2.5/2.6 installation, I do not remember exactly)
Thanks,
Marco
> On 10 Dec 2018, at 8:08 am, Marco Fioretti wrote:
>
> Greetings,
>
really confusing.
Not sure if I can test anything more on the postfix side, until the
reverse pointer gets updated in DNS. Or not?
Thanks,
Marco
>
> Postfix and Dovecot in CentOS systems work fine with that even though
> the daemon runs as user postfix group postfix.
>
> On 12/1
puzzle without knowing what it
represents...
Later,
Marco
hello all,
this is the same server, same situation for which I asked for help
yesterday. Right now, after trying to test and follow up the advice
received, this is the status:
IMAPS: not working yet because of SSL "no shared cipher". Details
here: https://dovecot.org/pipermail/dovecot/2018-Decembe
a
scritto:
>
> Marco Fioretti skrev den 2018-12-11 11:35:
>
> > IMAPS: not working yet because of SSL "no shared cipher". Details
> > here: https://dovecot.org/pipermail/dovecot/2018-December/113862.html
>
> current SSL dovecot settings in conf.d/10-ssl.con
/postfix/mymaps/vhosts.map
virtual_mailbox_maps = hash:/etc/postfix/mymaps/vmailboxes.map
virtual_transport = procmail
virtual_uid_maps = static:1001
postconf: warning: /etc/postfix/master.cf: unused parameter: flags=D
THANKS,
Marco
(*) please don't ask why this mismatch... it is one more of the things
that
:47, Robert Chalmers wrote:
>
> Where/what is the -D in your master.cf file
>
>
>
>
> On 11 Dec 2018, at 14:35, Marco Fioretti wrote:
>
> /etc/postfix/master.cf: unused
> parameter: flags=D"
>
>
>
, it had always
worked as expected, and never given me reasons to remember its
existence. Do you mean that the "flags=D" setting is obsolete in the
current version of postfix?
Marco
Il giorno mar 11 dic 2018 alle ore 16:36 Robert Chalmers
ha scritto:
>
> You may actually have a -D w
>
> Like /use/sbin/master -D type of thing?
>
> Turn on verbose output with a -v and see if you can catch it.
>
>
>
>
> -
>
>
>
> > On 11 Dec 2018, at 3:49 pm, Marco Fioretti wrote:
> >
> > Hello Robert,
> > there is no "-D" in
OK, I removed that part of the procmail line, and restarted. Here is
output of postconf -Mf and, respectively, postconf -n
(just for my own knowledge: this has nothing to do with the ipv6
complaints from google, or has it?)
Thanks,
Marco
###
smtp
t mind
removing that part of the line!
But if you check the output of postconf -Mf that I posted a few minutes ago...
now the question becomes "why there is a warning about "user=myvmail_user"?
As far as I can see, this postfix+procmail part of the system is
working as expected now. It
is "only" gmail interfacing and webmail configuration that are still giving me
pains.
Marco
;
> Robert
>
>
>
>
>
>
> __
> Robert Chalmers
> https://robert-chalmers.uk
> aut...@robert-chalmers.uk
> @R_A_Chalmers
>
> On 11 Dec 2018, at 4:44 pm, Marco Fioretti wrote:
>
> OK, I removed that part of the procmail line, and restarted. Here is
&
erfacing is always difficult. If you are running ipv6, and don’t
> need it, turn it off. Maybe Gmail will be ok then
>
> robert
>
>
>
>
>
>
> > On 11 Dec 2018, at 16:52, Marco Fioretti wrote:
> >
> > Il giorno mar 11 dic 2018 alle ore 17:03 Matus UHLAR - fan
address'.
The second type is the notifications from gmail that they won't accept
my email because of the ipv6 mismatch I already reported.
If I misunderstood what you are asking, please tell me where/how to
get it, no problem. Ditto if you want to receive the complete log
privately, without any editing.
Thanks in advance,
Marco
server, just to confirm to me that everything is fine, please let me
know.
Thanks, and off to dinner and bed now...
Marco
postconf -n:
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec
Hello,
In main.cf I have :
smtpd_banner = $myhostname ESMTP $mail_name (DATA TELECOM SERVICE)
But when I do : telnet myserver.tld 25 from another server I get :
220 **
I don't find why I don't get the good banner.
However,
ad mail sent earlier!)
Best regards,
Marco Tchi
Thanks for the replies.
It was indeed due to our new ASA Firewall!
Regards
Marco
-Message d'origine-
De : owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] De la part de Bastian Blank
Envoyé : mardi 20 janvier 2009 11:38
À : postfix-users@postfix.org
Objet
ould I set smtpd_recipient_overshoot_limit ? I should set
it to 0 ?
Regards,
Marco
helo=
I'm pretty sure I'm missing something very simple, but I just can't see it!
Thanks for any hints in the right direction!
[cid:blank29.gif]
Marco van Kammen
Applicatiebeheerder
[cid:blank4823.gif]
[cid:blank6784.gif]
Mirabeau | Managed ServicesDr. C.J.K. van Aalstweg
Hello,
I am using Postfix 2.3.3 and Kaspersky Antispam/Antivirus on our MX.
Mailboxes are hosted on another server.
The MX is relaying 250 domains or so, and it doesn't have resources
issues.
Our problem is that mail stay a long time in the active queue before the
content filter, but when it's sen
Ok, so the problem is definitely a content filter problem ?
This has nothing to do with our Postfix configuration if I understand.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Wietse Venema
Envoyé : vendredi 26 septembre 2008 15:00
À : Marco TCHI
d the message to the content
filter ?
Marco
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Wietse Venema
Envoyé : vendredi 26 septembre 2008 15:40
À : Postfix users
Objet : Re: Delivery delay problems
Marco TCHI HONG:
> Our problem is that mail st
:
smtpd (port 25, 100) -> spawn/kas-pipe (port 9026, 50) ->
spawn/smtpscanner (port 10025, 60) -> spawn (port 9025, 70).
spawn/kas-pipe (port 9026, 50) : to antispam
spawn/smtpscanner (port 10025, 60) : to antivirus
spawn (port 9025, 70) : back to postfix
[EMAIL PROTECTED] marc
1 - 100 of 206 matches
Mail list logo
