[pfx] IPv6 and RBL checks

[Jos Chrispijn via Postfix-users]

Hi all,

Recently I noticed this in my logfile:

0.3.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.bl.spamcop.net: 
Host or domain name not found. Name service error for 
name=0.3.9.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.bl.spamcop.net 
type=A: Host not found, try again


According to Postfix/postscreen it happens to be the reversed notation 
of the IPv6 sender of the email:
May 11 23:14:27 terra postfix/postscreen[4111]: PASS NEW 
[2607:f8b0:4864:20::930]:43019


Can someone explain why bl.spamcop.net reverses the ipv6 ip, thus not 
recognizing it like postscreen?

Thanks, Jos___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

[pfx] Use of PTR record

[Jos Chrispijn via Postfix-users]

Running mailservice with Postfix
PTR record is set to myserver.mydomain.com (1.2.3.4)

Every time I receive external e-mail, my logfile shows:
Apr 25 15:01:39 terra postfix/smtpd[12479]: 073416D2: 
client=unknown[1.2.3.4], sasl_method=LOGIN, sasl_username=me


How can I configure that client=unknown[1.2.3.4] will be replaced with 
the PTR record text instead?
I could force that by puting 'myserver.mydomain.com 1.2.3.4' in my hosts 
file, but I am not quite convinced that is the only solution.


Thanks, Jos

-- With both feet on the ground you can't make any step forward
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org

Problem translating domain

[Jos Chrispijn]

Recently read this in my logfile

midna_domain_to_ascii_create: Problem translating domain 
"�M-^X§�M-^X®�M-^Xª�M-^...


Can you tell what is triggering this?
Thanks.

-- With both feet on the ground you can't make any step forward

Re: Remote's Receiving mail reate issue

[Jos Chrispijn]

Kapetanakis Giannis:


I do this, which might help.


Will check that out, thanks for this.
J


-- With both feet on the ground you can't make any step forward

Re: Remote's Receiving mail reate issue

[Jos Chrispijn]

M Champion:

Because gmail returns a 4XX error, Postfix will retain those messages in 
the queue and try again later. If nothing has changed on the Google side 
regarding your SPAM rating, those messages will likely be accepted on a 
later attempt if only in small numbers at a time.


I see. thanks for explaining.
Best, Jos

-- With both feet on the ground you can't make any step forward

Remote's Receiving mail reate issue

[Jos Chrispijn]

Delivering an email to google resulted in this message:

"The user you are trying to contact is receiving mail at a rate that 
450-4.2.1 prevents additional messages from being delivered. Please 
resend your 450-4.2.1 message at a later time. If the user is able to 
receive mail at that 450-4.2.1 time, your message will be delivered. For 
more information, please 450-4.2.1 visit 450 4.2.1 "


Never saw this before; is this something I can prevent with postfix or 
is it google server related?


Best, Jos

-- With both feet on the ground you can't make any step forward

Re: Certificate Postfix.org missing?

[Jos Chrispijn]

IL Ka:


I believe this is about http://www.postfix.org/ 
There is no https there.


That's the one I meant, sorry I didn't include the www subdomain.
I expexted www always to be included as a subdomain name as you can't 
predict which URL users will type in their browser's URL bar.


Best, Jos

-- With both feet on the ground you can't make any step forward

Re: Certificate Postfix.org missing?

[Jos Chrispijn]

Wietse Venema:


There is neither a service at port 443, nor a postfix.org website.


You mean you don't authorize this site to use the Postfix name?
Don't understand, too cryptic.

Best, Jos

-- With both feet on the ground you can't make any step forward

Certificate Postfix.org missing?

[Jos Chrispijn]

Might be wrong, but just saw that the https// certificate is missing on 
your informatie website?


Best, Jos

-- With both feet on the ground you can't make any step forward 

Cloud9.net related responses

[Jos Chrispijn]

Hi team, can it be that responses in this mailinglist are also send by 
cloud9.net instead of only postfix.org?
Just asking to prevent contermination by importing parallel newsgroup 
source.


Best, Jos

-- With both feet on the ground you can't make any step forward

Re: Postscreen Logfile Analyser

[Jos Chrispijn]

On 11-9-20 21:08, Michael Orlitzky wrote:


I still use postfix-logwatch (http://logreporters.sourceforge.net/), but
there are a few patches to apply since the maintainer went AWOL:


Thanks for this; I am a nub on perl, but will certainly give it a try.

Best,
Jos Chrispijn

-- With both feet on the ground you can't make any step forward

Re: Postscreen Logfile Analyser

[Jos Chrispijn]

On 12-9-20 8:31, Admin Beckspaced wrote:


I use pslogscan for postscreen


Thanks, I think I can make this work.

Best,
Jos Chrispijn


-- With both feet on the ground you can't make any step forward

Postscreen Logfile Analyser

[Jos Chrispijn]

Can someone recommend a reliable Postscreen logfile analyser (FreeBSD 12)?
Thanks in advance!
/jos

-- With both feet on the ground you can't make any step forward 

Re: Outgoing mail is defered (not bounced) if EHLO returns 550 and closes connection

[Jos Chrispijn]

On 28-7-20 23:02, Michael Wyraz wrote:

I'm not 100% if that's a BUG or misconfiguration or misbehavior of the 
other MTA. But the resulting behavior is at least not what's expected.


Looks like your IP address is blocked by Cloudmark

-- CUT --

If you believe the reputation of your IP address is not correct or if 
the reputation has changed, you may request a reset of all related email 
traffic statistics within CSI for your IP address.


Please note this is not a portal for submitting complaints regarding 
content based spam signatures. Those requests must be directed at the 
service provider who is blocking the message. This portal will only 
accept statistical reset requests for IP addresses published by 
Cloudmark Sender Intelligence.


-- CUT --


-- With both feet on the ground you can't make any step forward

Re: Postfix -> Whatapp

[Jos Chrispijn]

On 29-5-20 13:03, Laura Smith wrote:


I would suggest you look at Doveot and its global IMAP Seive functionality.  
You can pipe stuff into shell scripts and hence do whatever you wish.



Thanks, will check that too. Thanks for your support!

Best, Jos


-- With both feet on the ground you can't make any step forward

Re: Postfix -> Whatapp

[Jos Chrispijn]

Hi,

On 27-5-20 17:49, @lbutlr wrote:

On 26 May 2020, at 13:24, J Doe  wrote:

You may want to investigate doing this at the MDA.  If you run Dovecot in 
conjunction with Postfix, you could write a Sieve script that calls a shell 
script that then sends the notification to whatever third-party service you 
would like.


I used to do this with procmail to send notifications on important mails via an 
SMS gateway. For a time I was also able to post alerts to a private twitter 
account. That no longer seems to work (but I also haven’t investigated why or 
if I can fix it as the need passed).

But it *is* outside the scope of postfix-users.


thanks, will dive into that as well.
Best, Jos


-- With both feet on the ground you can't make any step forward

Re: Postfix -> Whatapp

[Jos Chrispijn]

On 26-5-20 21:59, Wietse Venema wrote:


Sure. Use recipient_bcc_maps to add an extra recipient to their
email messages.That extra recipient goes through transport_maps to a
pipe daemon that invokes a command that sends a whatsapp message.


Great suggestion, thanks for that!
Best, Jos

-- With both feet on the ground you can't make any step forward

Re: Postfix -> Whatapp

[Jos Chrispijn]

On 26-5-20 21:24, J Doe wrote:

You may want to investigate doing this at the MDA.  If you run Dovecot 
in conjunction with Postfix, you could write a Sieve script that calls a 
shell script that then sends the notification to whatever third-party 
service you would like.


As a side-note - there actually is a Sieve RFC that covers notifications 
via XMPP / Jabber, but that isn't available in Dovecot at the moment.


Thanks, I will check this solution is also workable for me.
Best, Jos


-- With both feet on the ground you can't make any step forward

Re: Postfix -> Whatapp

[Jos Chrispijn]

On 26-5-20 21:18, vi...@vheuser.com wrote:


I hate to see folks on a user list throw down at a question.
More helpful than "No way, utterly" is "Here's how to".


Thanks. I just asked if this is possible. Sorry if I offended someone.


The question was how to initiate a script upon receipt of an email.
Here's a suggestion:
https://unix.stackexchange.com/questions/178396/run-script-on-receipt-of-email


Thanks for your suggestion, will follow up that one.
Jos

-- With both feet on the ground you can't make any step forward

Postfix -> Whatapp

[Jos Chrispijn]

Is there a way of Postfix sending a Whatsapp message to a user when 
there came in email for her/him?


Thanks, Jos

-- With both feet on the ground you can't make any step forward 

Re: COMMAND PIPELINING

[Jos Chrispijn]

On 30-1-20 16:00, Wietse Venema wrote:


It might make sense to log commands also in a losless form. Because
then we would have the complete client input (except that one would
have to enable the 'bare newline' postscreen test to reveal if the
client sent  or just ).


Thanks, understood.


-- With both feet on the ground you can't make any step forward

Re: COMMAND PIPELINING

[Jos Chrispijn]

On 29-1-20 21:19, Viktor Dukhovni wrote:


That's not enough context to tell.  Would need to know the preceding
sequence.  If this keeps happening, you'll need to make a PCAP capture
of an SMTP session from that server.

Thanks, will include more information next time I notice it.

Best, Jos

-- With both feet on the ground you can't make any step forward

COMMAND PIPELINING

[Jos Chrispijn]

Can someone tell me what this server tries to accomplish:

COMMAND PIPELINING from [183.89.214.13]:44487 after ???: 
\000\234\000\235\000/\0005\300\022\000\n\001\000\000d\000\000\000\023\000\021\000\000\016mail.some.net\000\005\000\005\001\000\000\000\000\000\n\000\n\000\b\000\035\000\027\000\030\000\031\000\v\000\002\001\000\000\r\000\030\000\026\b\004\b\005\b\006\004\001\004\003\005\001\005\003\006\001\006\003\002\001\002\003\377\001\000\001


Thanks,
Jos Chrispijn

-- With both feet on the ground you can't make any step forward

Re: Mail rejected with 5.7.1 HDR9020 Date header is in the distant future

[Jos Chrispijn]

Best check your header_checks configuration. It should look like this:

/^Date: .* [0-1][0-9][0-9][0-9]/    REJECT Your email has a date 
from the past. Fix your system clock and try again.
/^Date: .* 200[0-9]/    REJECT Your email has a date 
from the past. Fix your system clock and try again.
/^Date: .* 201[0-9]/    REJECT Your email has a date 
from the past. Fix your system clock and try again.

/^Date: .* 2020/    DUNNO
/^Date: .* 20[2-9][1-9]/    REJECT Your email has a date in 
the future. Fix your system clock and try again.
/^Date: .* 2[1-9][0-9][0-9]/    REJECT Your email has a date in 
the future. Fix your system clock and try again.
/^Date: .* [3-9][0-9][0-9][0-9]/    REJECT Your email has a date in 
the future. Fix your system clock and try again.


Hope this helps!

Best, Jos

On 6-1-20 18:31, Roel Wagenaar wrote:

L.S.

Lately I find rejections in my mail log, my mailers all have ntp running,
yet the reject reason is: 5.7.1 HDR9020 Date header is in the distant
future.


Jan  6 18:18:24 mail1 postfix-in/smtpd[19887]: connect from
english-breakfast.cloud9.net[168.100.1.7]
Jan  6 18:18:24 mail1 postfix-in/smtpd[19887]: E59C49805:
client=english-breakfast.cloud9.net[168.100.1.7]
Jan  6 18:18:25 mail1 postfix-in/cleanup[19907]: E59C49805: reject: header
Date: Mon, 6 Jan 2020 17:16:46 + from
english-breakfast.cloud9.net[168.100.1.7];
from= to= proto=ESMTP
helo=: 5.7.1 HDR9020 Date header is in the
distant future
Jan  6 18:18:25 mail1 postfix-in/smtpd[19887]: disconnect from
english-breakfast.cloud9.net[168.100.1.7] ehlo=1 mail=1 rcpt=1 data=0/1
quit=1 commands=4/5

Anyone have an idea where I am to look for the problem?


-- With both feet on the ground you can't make any step forward

Re: Reject Chinese mail

[Jos Chrispijn]

On 21-11-19 6:42, Reto wrote:
Apparently you also don't speak English properly. Do you want people 
to spam block the full .de domain because of that? 


Idiot

-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 3-6-19 13:09, Wietse Venema wrote:
postmap hash:/postfix/tables/spamtrap what is this? 


# spamtrap 180711
partmaps@   DISCARD

in main.cf
check_recipient_access  hash:/postfix/tables/spamtrap,

I added this some time ago referring to

http://postfix.1071664.n5.nabble.com/Need-to-clarfiy-how-to-implement-spamtrap-address-checking-amp-discard-with-before-queue-filtering-td761.html

/jos


-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

Hi Jan,

On 30-5-19 14:47, Jan Ceuleers wrote:

Jos, what I think everybody is trying to tell you is that your cron job
has swept the problem under the rug, for now, but that it is still there.


Yes, I noted, thanks for that.

What I have done is running this batch after a Postfix or Dovecot update 
and the issue has gone away.


#! /bin/sh -x
newaliases
postalias hash:/etc/aliases
postmap hash:/postfix/tables/transport
postmap hash:/postfix/tables/virtual_alias_domains
postmap hash:/postfix/tables/virtual_alias_maps
postmap hash:/postfix/tables/helo_checks
postmap hash:/postfix/tables/sender_checks
postmap hash:/postfix/tables/spamtrap
postfix reload
postfix flush

/jos

-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 30-5-19 14:25, Wietse Venema wrote:

Again, this confirms my suspicion that the system has gotten messed
up. Postfix has been around for decennia and it does not require
restarts to stay functional.


Ok, thanks y'all for helping out. Everything is fine now.

/jos

-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 30-5-19 13:50, Wietse Venema wrote:

On a sane system (LINUX included), Postfix can run without ever
needing a baby sitter cronjob.

OK - never experienced this issue but only for the last few weeks.

What I suspected was an effed-up system; your need to run a baby
sitter cronjob confirms my suspicion.


I ran Postfix' update batch that contains (amongst others)

newaliases
postalias hash:/etc/aliases
postfix reload
postfix flush

and it seems that this did the trick - no errors anymore.


Are you running Postfix on real hardware, or on some mini-size box
like a Raspberry, or some other resource-constrained environment
like a VPS or jail?


The issue I had was on a real server.
My other server runs on a Raspberry indeed, on which I have no Postfix 
issues - running smoothly.

No VPS or Jail involved.


-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 30-5-19 12:52, @lbutlr wrote:

On 30 May 2019, at 02:39, Jos Chrispijn  wrote:
Where did that come from? (It doesn't exist on my system).
Amongst others (updating tables), this is now standard on my Postfix 
upgrade batch.

I don't know about you, but new aliases and postalias and postmap are tools 
that I run extremely rarely. I think the last made I made to aliases might have 
been as much as 10 years ago. I've changed virtual more frequently, but still 
rarely.

postfix flush is nearly always a bad idea, and I can't imagine it's useful 
after a reload, or at least I can't think of a reason you'd want to do that; if 
you've reloaded, postfix will requeue the mail on its own.


I had to trace the cause of the issue; found out that running this on a 
regular basis (at least after postfix and/or Dovecot) update this did 
the trick for me.


Wietse, does this match the cause you expected it to be?

Thanks, Jos

-- With both feet on the ground you can't make any step forward

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 29-5-19 19:21, Jos Chrispijn wrote:
Interesting that you ask, as I just checked postfix after a restart 
and it all goes well again.
Decided to restart from cron every 12 hours, but I guess that is just 
symptom suppression


A friend advised me to run /postfix/update and it looks as if this did 
the trick. Part of that file contains:


newaliases
postalias hash:/etc/aliases
postfix reload
postfix flush

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 23-5-19 14:27, Wietse Venema wrote:

It is also possible that your kernel can't handle the exclusive
lock request because it is running out of kernel resources. How
often are you restarting/reloading Postfix?

I have some supicions, but let's hear from you first.
Interesting that you ask, as I just checked postfix after a restart and 
it all goes well again.
Decided to restart from cron every 12 hours, but I guess that is just 
symptom suppression


/jos

Re: Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

On 22-5-19 13:11, Wietse Venema wrote:

postscreen needs exclusive access to the btree file, and some other
program other program already has access to the file (exclusive or
non-exclusive). That could be another postscreen, or postmap, or
some other program.


As far as I know there are no other programs using the btree file.
I will check further, thanks for your reply.

/jos

-- With both feet on the ground you can't make any step forward

Postscreen - fatal: btree:/var/db/postfix/postscreen_cache

[Jos Chrispijn]

Dear team,

I get this error messages in my logfile more frequently:

May 21 21:23:51  kernel: May 21 21:23:51  postfix/postscreen[77391]: 
fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: 
Resource temporarily unavailable

Can you tell me what exactly goes wrong and how to solve this? Thanks.

Best regards,
Jos Chrispijn

-- With both feet on the ground you can't make any step forward

Re: 550 Messages should have one or no Message-ID headers, not 2.

[Jos Chrispijn]

Thought so neither - will continue my search: the component itself or 
the mailer ofthe hostingprovider.


Thanks for letting me know.

    Jos


On 29-3-2018 20:18, Wietse Venema wrote:

Jos Chrispijn:

To: arecipi...@someserver.com
X-PHP-Originating-Script: 0:class.phpmailer.php
Date: Thu, 29 Mar 2018 14:40:07 +0200
From: newslet...@someserver.com
Reply-To: newslet...@someserver.com
Message-ID: <odm3nza3ac815y53bamtuymjmynziwnze0o...@www.somesite.nl>

That is not a Postfix Message-ID header. See below for examples
of a real Postfix queue ID.


MIME-Version: 1.0
Content-Type: multipart/alternative;
   boundary="b1_7637dbbd774694148fb9e0abfd84efd7"
Content-Transfer-Encoding: 8bit
Message-ID: <12673aa57c00480ab09c641ac2b732d6@hostingprovider.com>

That is also not a Postfix message-ID header.

Postfix Message-ID headers have one of the following formats:

<20180329053241.c57e2332...@english-breakfast.cloud9.net>

 20180329053241 is the UTC time in seconds in in MMDDHHMMSS
 form, and C57E2332224 is a short Postfix queue ID (hexadecimal
 string with 5 characters for the sub-second time in microseconds,
 followed by the file inode number).

<40bxk51ky2zj...@spike.porcupine.org>

 40BXk51Ky2zJrNr is a long Postfix queue ID (6 or more characters
 for the UTC time in seconds, 4 characters for the sub-second
 time in  microseconds, the 'z', followed by the file inode
 number.

Wietse


-- With both feet on the ground you can't make any step forward

550 Messages should have one or no Message-ID headers, not 2.

[Jos Chrispijn]

Dear list,

I sent out a newsletter(J!website with Acyba component) some times a month
Since two weeks (cannot remember the exact date) I get this message back 
via Postfix after sending outthe newsletter.


I am thinking of the newsletter component (Acyba) in combination with 
the phpmailer of my hosting provider.

Would that be an option?

--- cut ---

MailEnable: Message could not be delivered to some recipients.
The following recipient(s) could not be reached:
 Recipient: [SMTP:subscri...@somedomain.com]
 Reason: 550 Messages should have one or no Message-ID headers, not 2.

Message contents follow:

Received: from ([127.0.0.1]) with MailEnable ESMTP; Thu, 29 Mar 2018 
14:40:07 +0200


Subject: xxx

To: arecipi...@someserver.com
X-PHP-Originating-Script: 0:class.phpmailer.php
Date: Thu, 29 Mar 2018 14:40:07 +0200
From: newslet...@someserver.com
Reply-To: newslet...@someserver.com
Message-ID: 
X-Mailer: PHPMailer 5.2.19 (https://github.com/PHPMailer/PHPMailer)
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="b1_7637dbbd774694148fb9e0abfd84efd7"
Content-Transfer-Encoding: 8bit
Message-ID: <12673aa57c00480ab09c641ac2b732d6@hostingprovider.com>
Date: Thu, 29 Mar 2018 14:40:07 +0200
X-ME-Bayesian: 0.00

This is a multi-part message in MIME format.
--b1_7637dbbd774694148fb9e0abfd84efd7
Content-Type: text/plain; charset=us-ascii

test

--b1_7637dbbd774694148fb9e0abfd84efd7

Content-Type: text/html; charset=us-ascii



Newsletter 4 | April Easter Edition

--- cut original text ---

thanks for your reply
/Jos

Re: Forward local user email or another local user

[Jos Chrispijn]

Op 26-10-2017 om 17:59 schreef Jos Chrispijn:

Can you tell me how I can force this to be done with Postfix directly?


Finally the solution was so simple:

- create user jdoe (main domain)
- add entry to /etc/aliases:

jdoe:  

- update /postfix/tables
- restart postfix

When I now send a domain user an email, instead of arriving in 
/var/mail/jdoe it is piped to 

Solved!

-- With both feet on the ground you can't make any step forward

Re: Forward local user email or another local user

[Jos Chrispijn]

Op 27-10-2017 om 0:17 schreef Bill Cole:

So, passwords -can- be used with virtual users for SMTP?

Yes. Any authentication identity can be used for Postfix's 
SMTP/Submission authentication because Postfix doesn't really do the 
authentication.


That is an interesting statment. I really didn't know that (sorry for 
the mix up here).
Where can I find this to work regarding configuration of these kind of 
accounts? I know have a control file virtual_alias_maps in which I refer 
non main domein addresses to domain users.


-- With both feet on the ground you can't make any step forward

Re: Forward local user email or another local user

[Jos Chrispijn]

Op 26-10-2017 om 20:17 schreef Matus UHLAR - fantomas:
if you want to send mail to a user Y and you don't want to use 
password of

user Y, but you must use a password, you must use password of user X
(whatever X and Y mean)

It is all about _existing_ user accounts
Using (virtual) aliases provides only email addresses of non existing 
users, which I cannot use for the push service (that is going to send 
out the message(s).


I don't want the mail to come into the inbox of existing user X but 
directly forwarded into the one of existing user Y.


-- With both feet on the ground you can't make any step forward

Forward local user email or another local user

[Jos Chrispijn]

I have a service running that requires me to configure an SMTP user X 
with password to send daily statistics to.


Cannot use a virtual alias user (and forward to the final user Y) 
because I have to provide a password as well.


So I set up a dedicated user X account (with password) for this to be 
used to pass through incoming email to the final user Y account (which I 
didn't want to use for that SMTP action).


Can you tell me how I can force this to be done with Postfix directly?
I can solve it by some forward action once it arrives in the inbox of 
user X, and forward it to user Y, but would be better if I can do such 
directly with Postfix.


-- With both feet on the ground you can't make any step forward

Re: Multi-domein postmaster account

[Jos Chrispijn]

On 16-5-2015 16:56, Viktor Dukhovni wrote:

On Sat, May 16, 2015 at 09:58:53AM -0400, Wietse Venema wrote:


Jos Chrispijn:


I have a number of domains that are not used but in my helo_checks file
(you are not in my domain).
Is there a way of redirecting incoming email to
postmas...@thesedomains.com without having to create an entry for each
domein in virtual_alias_maps?

You must specify postmaster@domain otherwise you would receive
all mail for all postmasters at all domains.

The only exception is that for domains listed in mydestination,
bare username aliases with no @domain part match a mailbox in
any of the domains.  However, in that case all the domains are
live.  The original post is rather unclear about the sense in
which the domains in question are not used or why in that case
postmaster mailboxes are still required.


Thanks for this guys - I will check how I can get this to work. All 
domains are indeed 'live'.


BR, Jos Chrispijn

Multi-domein postmaster account

[Jos Chrispijn]

I have a number of domains that are not used but in my helo_checks file 
(you are not in my domain).
Is there a way of redirecting incoming email to 
postmas...@thesedomains.com without having to create an entry for each 
domein in virtual_alias_maps?


BR, Jos Chrispijn

-- Artificial intelligence is no match for natural stupidity

Beste wishes for 2015!

[Jos Chrispijn]

I would like to thank the Postfix team and all list members for their 
supportand hope everyone enjoys an informative and productional 2015.


Keep up the good work!
BR, Jos Chrispijn

- /Vision is not seeing things as they are, but as they will be...
/

-- Jos Chrispijn

Bouncing email containing attachments

[Jos Chrispijn]

Can you tell me how I can block email from certain users who have 
attachment(s) included?


I want to force senders to use WeTransfer - bouncing their email should 
also create a separate reply asking this user to use WeTransfer instead 
of email (as in attachments).


As attachements in fact are the email itself, should I scan for mime 
headers (or something like that) to trigger this action?


Thanks for your reply.
Jos Chrispijn

Re: Bouncing email containing attachments

[Jos Chrispijn]

Noel Jones schreef op 25-11-2014 at 18:23 CET:
You'll need to use a milter or proxy for this. Maybe milter-regexp 
will do the trick. Yes, you'll need to examine the envelope sender, 
and the mime headers. -- Noel Jones 


Thanks for your response - will check your suggestion and see if it fits 
my needs.

BR, Jos

Re: Postscreen and exceptions

[Jos Chrispijn]

Wietse Venema:
Don't use spamcop, or use it only with small weight in a scoring 
system. Wietse


What is your concern about Spamcop?

Happy to learn,
Jos

Re: Rules on incoming email

[Jos Chrispijn]

 On 20-9-2010 9:11, Stan Hoeppner wrote:

I was in a similar situation not long ago using TBird rules to do my
message sorting into IMAP folders. When accessing my mail vi my
Roundcube webmail server nothing was sorted. I grew tired of this. I
was already using Dovecot for my IMAP server, so I converted to using
Dovecot LDA for delivery instead of Postfix local, and using Sieve
scripts to sort the mail into folders.

That is a good tip, I allready use Dovecot IMAP. Thanks
Jos Chrispijn.

Rules on incoming email

[Jos Chrispijn]

 I have this email client that takes care of distrubition of email to 
different mail folders.
As I now started to read my email with a mobile phone, there is a load 
of messages that aren't sorted, as my 'home client' hasn't taken care of 
that.
Is there a way of using rules on my email the moment it comes in so that 
I am not dependend on my mail clients' rules anymore?


Thanks,
Jos Chrispijn

Re: Rewrite destination domain

[Jos Chrispijn]

LuKreme wrote:
Every time I peruse the logs, find his typo, and sent him log lines. 
This works for a few days, or weeks, maybe. Then the cycle repeats. 
He's old, and essentially untrainable.


You can only lead a horse to the water...

Jos Chrispijn

Re: 4.5.3 too many recipients

[Jos Chrispijn]

Uit een eerder bericht (21-11-2008 13:41):
i have a very simple postfix setup running at school.
  
now the principal wants to send mails to all the parents that
registered their emailaddress and signed on for a newsletter every week.
This causes him to get a 452: 4.5.3 Too many recipients.

Do you CC 200 addresses in one
message?
Jos Chrispijn