Thanks Jeroen, adding bounce,2bounce to notify_classes did exactly what I
was looking for.
On Sat, Dec 18, 2010 at 11:45, Jeroen Geilman jer...@adaptr.nl wrote:
On 12/18/10 8:16 PM, John Brahy wrote:
Hello,
I'm having a problem configuring what I thought would be a postmaster
account
Hello Postfix happy users !
I am trying to figure out if it is possible to limit the delivery
concurrency for some destinations.
For example :
- emails matching patterns @foo.com and @bar.com must be sent with a
slow delivery concurrency
- other emails must be sent with (let's say) default
Le 20/12/2010 08:03, Ramesh a écrit :
HI All,
I am planning to configure backup MX for primary MX. i have few queries..
All email id's in primary MX need to be same in secondary MX?
yes. and all checks done on the primary should be done on the secondary
as well.
also, if the secondary
Le 20/12/2010 10:39, Lionel TRESSENS a écrit :
Hello Postfix happy users !
I am trying to figure out if it is possible to limit the delivery
concurrency for some destinations.
For example :
- emails matching patterns @foo.com http://foo.com and @bar.com
http://bar.com must be sent with a
Oh thanks !
This is great ;)
Regards
Lionel
2010/12/20 mouss mo...@ml.netoyen.net
Le 20/12/2010 10:39, Lionel TRESSENS a écrit :
Hello Postfix happy users !
I am trying to figure out if it is possible to limit the delivery
concurrency for some destinations.
For example :
- emails
Hi
how can I disable notifications for expire messages.
DBA9ED01B53: from=, status=expired, returned to sender
DBA9ED01B53: sender non-delivery notification: E737FD0192B
I want to disable notification for expire messages but not for bounces.
* alex m...@deltaindigo.ro:
Hi
how can I disable notifications for expire messages.
DBA9ED01B53: from=, status=expired, returned to sender
DBA9ED01B53: sender non-delivery notification: E737FD0192B
I want to disable notification for expire messages but not for bounces.
You can't.
On 12/20/2010 12:44 PM, Ralf Hildebrandt wrote:
* alexm...@deltaindigo.ro:
Hi
how can I disable notifications for expire messages.
DBA9ED01B53: from=, status=expired, returned to sender
DBA9ED01B53: sender non-delivery notification: E737FD0192B
I want to disable notification for expire
I will be out of the office starting 12/20/2010 and will not return until
01/04/2011.
On Mon, 2010-12-20 at 07:03 +, Ramesh wrote:
HI All,
I am planning to configure backup MX for primary MX. i have few queries..
All email id's in primary MX need to be same in secondary MX?
Is it possible to configure separate email clients to receive and send for
both mail server's,
Hello
I'm searching for an automated solution that will split
bigs emails in several parts ( as we do with mpack manually )
then reassemble them at reception.
It would be transparent for the user that would
receive only one big email.
Any infos welcome
Thanks
On Monday 20 December 2010 13:11:16 Frank Bonnet wrote:
Hello
I'm searching for an automated solution that will split
bigs emails in several parts ( as we do with mpack manually )
then reassemble them at reception.
It would be transparent for the user that would
receive only one big
Thanks for the reply
My purpose is for internals emails use only ! so the control would be OK
On 12/20/2010 01:17 PM, J. Roeleveld wrote:
On Monday 20 December 2010 13:11:16 Frank Bonnet wrote:
Hello
I'm searching for an automated solution that will split
bigs emails in several parts (
On 2010-12-20 2:03 AM, Ramesh wrote:
I am planning to configure backup MX for primary MX. i have few
queries..
snip
Please send suggestion's or URL to know more about this.
Don't bother... backup MX's should only be implemented by those who have
a very good reason for doing so, and are a
On Monday 20 December 2010 13:22:25 Frank Bonnet wrote:
Thanks for the reply
My purpose is for internals emails use only ! so the control would be OK
If it is for internal email only, why do you want to split up the emails?
If it's because postfix rejects too large emails you can always
Le 20/12/2010 13:11, Frank Bonnet a écrit :
Hello
I'm searching for an automated solution that will split
bigs emails in several parts ( as we do with mpack manually )
then reassemble them at reception.
It would be transparent for the user that would
receive only one big email.
Do you mean
Hi,
I am a little bit stuck with prepending one and exactly one additional header
to outgoing mails that are sent from local users. In fact I want to add a
VBR-Info:- header for outgoing mails.
Local users use a seperate MSA port (own IP-socket in master.cf). The socket is
configured with
Hello
I receive periodically some spams that pretend to be
from my domain.
Looking in emaila headers I can see where the email come from
Received: from 174.subnet222-124-154.static.astinet.telkom.net.id
(unknown [222.124.154.172])
Of course the header has been rewrited but is there a
* Frank Bonnet f.bon...@esiee.fr:
Hello
I receive periodically some spams that pretend to be
from my domain.
Looking in emaila headers I can see where the email come from
Received: from 174.subnet222-124-154.static.astinet.telkom.net.id
(unknown [222.124.154.172])
Hi again,
# header_checks
if !/^VBR-Info:.*roessner-net(work-solutions)?/
/^From:@roessner-net\.com/ PREPEND VBR-Info:
md=roessner-net.com; mv=dwl.spamhaus.org; mc=all
/^From:@roessner-network-solutions\.com/ PREPEND VBR-Info:
md=roessner-network-solutions.com;
Hello,
I would like to have a program called when a message is delivered in a mailbox.
I'm currently trying this with a filter, which gives me a race condition
between real delivery and the moment my hook/filter runs.
I (partly) understand I can do this with a 'maildrop' program, but would
On 12/20/10 3:49 PM, Frank Bonnet wrote:
Hello
I receive periodically some spams that pretend to be from my domain.
If this is in the From: header, there's not much you can do about that.
The envelope sender you can trivially protect.
After you have allowed submission, and have passed
On 12/20/2010 8:37 AM, Christian Roessner wrote:
Hi,
I am a little bit stuck with prepending one and exactly one additional header
to outgoing mails that are sent from local users. In fact I want to add a
VBR-Info:- header for outgoing mails.
Local users use a seperate MSA port (own
On 12/20/10 4:29 PM, Ronald Klop wrote:
Hello,
I would like to have a program called when a message is delivered in a
mailbox. I'm currently trying this with a filter, which gives me a
race condition between real delivery and the moment my hook/filter runs.
That sounds wrong. Any of the
Hello postfix list!
I've recently checked the gmail bulk mail guidelines, and I've seen that
they recommend this header in the email:
Precedence: bulk
The source is this URL:
https://mail.google.com/support/bin/answer.py?answer=81126#format
We have a designed our own mail server for clients
On 12/20/2010 10:49 AM, Martin Spinassi wrote:
Hello postfix list!
I've recently checked the gmail bulk mail guidelines, and I've seen that
they recommend this header in the email:
Precedence: bulk
The source is this URL:
https://mail.google.com/support/bin/answer.py?answer=81126#format
We
On 12/20/2010 10:55 AM, Christian Roessner wrote:
Yes, that will work fine if you put your check_sender_access rule under
smtpd_data_restrictions.
I am unsure if that works. I thought that check_sender_access only uses the
envelope-from tag. So where is the difference between putting it in
DATA
.CRLF -- Testing after this point, if in smtpd_data_restrictions. But
does this behave differently then the above?
Of course it works. And BTW, smtpd_data_restrictions are run after the DATA
command, not after the dot -- that's smtpd_end_of_data_restrictions.
:-)
With the
With the default smtpd_delay_reject=yes, smtpd_{client, helo, sender,
recipient}_restrictions are repeated for each recipient, but
smtpd_data_restrictions are run only once.
That is really good to know and makes things much easier now. I give it a try.
Thanks :-) Works. It is
On Mon, Dec 20, 2010 at 01:11:16PM +0100, Frank Bonnet wrote:
I'm searching for an automated solution that will split
bigs emails in several parts ( as we do with mpack manually )
then reassemble them at reception.
It would be transparent for the user that would
receive only one big email.
I'm using Postfix 2.7.0.
I use LDAP do manage/list domains that I relay for.
My problem is, when mail arrives to a domain I make relay for, and
this account has an alias to another domain I also relay for, the
transport to the second e-mail is not found.
Suppose I relay for both
On Mon, Dec 20, 2010 at 04:17:08PM -0200, Lauro Costa G. Borges wrote:
I'm using Postfix 2.7.0.
Good, this is a reasonably recent release. You may want to consider
updating to 2.7.2:
20100515
Bugfix (introduced Postfix 2.6): the Postfix SMTP client
XFORWARD
On 12/18/2010 11:03 PM, Victor Duchovni wrote:
postfix/master[20377]: warning: process /usr/libexec/postfix/qmgr pid 20380
killed by signal 15
This is SIGTERM. Are you running postfix stop frequently?
No. In fact I'm not running it at all. In fact in the interest of
troubleshooting this,
For some of the smtpd restrictions I would like to merely tag a
message instead of outright reject it. It would be either delivered
as usual with the tagging in place for the client or user agent to
check for, or be used to deliver the mail to a special folder. If the
tagging is done by adding
Le 20/12/2010 17:55, Christian Roessner a écrit :
Yes, that will work fine if you put your check_sender_access rule under
smtpd_data_restrictions.
I am unsure if that works. I thought that check_sender_access only uses the
envelope-from tag.
It is.
So where is the difference between
Le 20/12/2010 15:49, Frank Bonnet a écrit :
Hello
I receive periodically some spams that pretend to be
from my domain.
Looking in emaila headers I can see where the email come from
Received: from 174.subnet222-124-154.static.astinet.telkom.net.id
(unknown [222.124.154.172])
Of course the
Hi all,
really thanks for all info, but the problem already is fixed. It needed help
here for the check_sender_access adding to smtpd_data_restrictions and the help
of Mark Martinec for amavisd-new, to get header_checks working in a dual setup
MSA/MTA.
Many thanks for all your help.
It works
Phil Howard:
For some of the smtpd restrictions I would like to merely tag a
message instead of outright reject it. It would be either delivered
as usual with the tagging in place for the client or user agent to
check for, or be used to deliver the mail to a special folder. If the
tagging
On Tuesday, December 21, 2010 04:59:16 am Victor Duchovni wrote:
Historically, Outlook Express would generate and re-assemble large
messages via message/partial MIME encapsulation.
http://tools.ietf.org/html/rfc2046#section-5.2.2
This format is not directly supported by most MUAs and
mouss wrote:
anyway, reading your prepend info tells us that you're trying to do
something regarding spamhaus based on the From header. This is most
probably wrong. if you tell us what you're trying to do, we will tell
you why you are wrong ;-p
If we are talking about VBR-Info based on a DKIM
40 matches
Mail list logo
