[pfx] Re: temporary lookup error with utf8mb4 characters

2023-04-17 Thread Wietse Venema via Postfix-users
V?ctor Rubiella Monfort via Postfix-users: > Hi, I have more info and I try to explain it better: > > First of all I have smtputf8_enable = no (disabled). > > I have several databases related with several mysql_virtual maps: > > - Some with utf8 + utf8_general_ci collation > > - Another ones

[pfx] Re: any web.de staff here?

2023-04-16 Thread Wietse Venema via Postfix-users
Jaroslaw Rafa via Postfix-users: > Dnia 16.04.2023 o godz. 16:32:41 Gerald Galster via Postfix-users pisze: > > > > Mails classified as spam or external forwards seemingly take another route > > via mout-xforward.web.de. These servers are SBL-listed by intention, most > > likely because the spam

[pfx] Re: temporary lookup error with utf8mb4 characters

2023-04-14 Thread Wietse Venema via Postfix-users
Viktor Dukhovni via Postfix-users: > On Fri, Apr 14, 2023 at 01:06:16PM -0400, Wietse Venema via Postfix-users > wrote: > > > Wietse Venema via Postfix-users: > > > As for the temp error becoming persistent, the Postfix pgsql: client > > > code returns an err

[pfx] Re: temporary lookup error with utf8mb4 characters

2023-04-14 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > As for the temp error becoming persistent, the Postfix pgsql: client > code returns an error when it gets an error from all of the hosts > configured in the Postfix pgsql: client configuration file, or when > all hosts have been flagged as 'down

[pfx] Re: temporary lookup error with utf8mb4 characters

2023-04-14 Thread Wietse Venema via Postfix-users
V?ctor Rubiella Monfort via Postfix-users: > Hi again, > > I realized than same error is raised when database is in utf8 if email > contains utf8mb4 characters. > > Which is the convenient database collation for postfix? We can force > postfix to accept only utf8 characters?. With

[pfx] Postfix 3.8 release candidsate 1

2023-04-12 Thread Wietse Venema via Postfix-users
I'm wrapping up the Postfix 3.8 stable release, and have rolled out a release candidate postfix-3.8.0-RC1. This is mainly so that people can find out if Postfix 3.8 will build and run as expected. The changes involve code and documentation improvements, SRV record lookup, configuration for a

[pfx] Re: SPF: HELO does not publish an SPF Record

2023-04-12 Thread Wietse Venema via Postfix-users
Fourhundred Thecat via Postfix-users: > > On 2023-04-12 15:30, Wietse Venema via Postfix-users wrote: > > Fourhundred Thecat via Postfix-users: > >> > On 2023-04-12 14:48, Byung-Hee HWANG via Postfix-users wrote: > > > > The smtp_helo_name used in th

[pfx] Re: SPF: HELO does not publish an SPF Record

2023-04-12 Thread Wietse Venema via Postfix-users
Fourhundred Thecat via Postfix-users: > > On 2023-04-12 14:48, Byung-Hee HWANG via Postfix-users wrote: > >>2) change smtp_helo_name to > >> > >> smtp_helo_name = $mydomain > > > > It is very strange, i think. > > what do you mean? > is it strange to use example.com, instead of

[pfx] Re: HELO checks for desktop clients

2023-04-10 Thread Wietse Venema via Postfix-users
Did you set 'smtpd_delay_reject=no'? Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org

[pfx] Re: postfix and opendkim

2023-04-10 Thread Wietse Venema via Postfix-users
Fourhundred Thecat via Postfix-users: > Hello, > > I am setting up opendkim on my postfix server: > > what is the practical difference between using inet or UNIX domain > socket in /etc/opendkim.conf ? > > If I leave socket at the default settings: > >Socket

[pfx] Re: REPOST: Envelope sender is not modified correctly

2023-04-09 Thread Wietse Venema via Postfix-users
Fran?ois via Postfix-users: > I'm sorry if any part of my request seemed disagreeable: not my intention. > > I did post the relevant parts (I believe) of main.cf: > > canonical_maps = regexp:/etc/postfix/canonical > canonical_classes = envelope_sender You failed to post "postconf -n" output as

[pfx] Re: REPOST: Envelope sender is not modified correctly

2023-04-09 Thread Wietse Venema via Postfix-users
Fran?ois via Postfix-users: > >Envelope from? Header from? > > I just don't know. I tried to find the info but could not. My best guess: > header from. It sets both. With a very simple canonical map main.cf: canonical_maps = inline:{{f...@porcupine.org = b...@porcupine.org}} Command:

[pfx] Re: REPOST: Envelope sender is not modified correctly

2023-04-09 Thread Wietse Venema via Postfix-users
Fran?ois via Postfix-users: > mail program links to mailx. mailx man page says: > > -r address > Sets the From address. Overrides any from variable specified Envelope from? Header from? Wietse ___ Postfix-users mailing list --

[pfx] Re: REPOST: Envelope sender is not modified correctly

2023-04-09 Thread Wietse Venema via Postfix-users
How do you specify the test message envelope sender addresses? You can't put them in a message header (From:, Return-Path:, etc.). Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to

[pfx] Re: Question to reject_rbl_client zen.spamhaus.org

2023-04-09 Thread Wietse Venema via Postfix-users
tom--- via Postfix-users: > I have this setting in main.cf: > > smtpd_recipient_restrictions = > permit_mynetworks, > permit_sasl_authenticated, > reject_unauth_destination, > check_policy_service unix:private/policyd-spf, > reject_rbl_client zen.spamhaus.org, >

[pfx] Re: Headers and Forwarding

2023-04-08 Thread Wietse Venema via Postfix-users
Viktor Dukhovni via Postfix-users: > Apparently, reading RFC5321 and RFC5322 is too tedious. Reading RFCs is so old-school. It's much easier to be ignorant. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send

[pfx] Re: invalid and non-fqdn hostname

2023-04-08 Thread Wietse Venema via Postfix-users
raf via Postfix-users: > > From reading the code, these two restrictions seem equivalent except when > > SMTPUTF8 extension is used. > > when the SMTPUTF8 is in play, reject_non_fqdn_helo_hostname will convert a > > hostname containing UTF to an internationalized domain name > > before checking.

[pfx] Re: confused about two options

2023-04-08 Thread Wietse Venema via Postfix-users
tom--- via Postfix-users: > Hello, > > 1. use MIME encoding for 8bit chars I suppose you mean that you encode message header or boody content using Base64 or Quoted-Printable. > 2. Content-Transfer-Encoding: 7bit Both base64 and quoted-printable are 7-bit transfer encodings. > Do they mean

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Wietse Venema via Postfix-users
Steffen Nurpmeso via Postfix-users: > Wietse Venema wrote in > <4pshgn4l8vzj...@spike.porcupine.org>: > |Wietse Venema via Postfix-users: > |> I have some, starting after I updated from 3.8-202304331 to 3.8-2023040\ > |> 2. > > There are snapshots, ther

[pfx] Re: simple content filter for outgoing message

2023-04-06 Thread Wietse Venema via Postfix-users
Corey Hickman via Postfix-users: > Hello buddies, > > I just want to make some simple filters for outgoing messages. > for example, the message content has some keywords (like "VPN sale") > included, it will be rejected by the system. > > I know there are the software Rspamd and Spamassassin,

[pfx] Re: Success DSN for virtual mailboxes not working

2023-04-06 Thread Wietse Venema via Postfix-users
Nuno Pereira via Postfix-users: > My best guess for now is that the virtuals are messing around with notify. Is > there any way to put it marking the virtual destination as the final > destination, even not being so? I have demonstrated that Postfix will send "success" notification after virtual

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > I have some, starting after I updated from 3.8-202304331 to 3.8-20230402. > This was not found running the tests under Valgrind. > > Apr 4 07:29:42 spike postfix/smtp[37107]: 4PrQXP6G74zJrP4: > to=<...@gmail.com>, relay=gmail

[pfx] Re: pf snap 3.8-20230402 mem corruption issues

2023-04-06 Thread Wietse Venema via Postfix-users
Florian Piekert via Postfix-users: Checking application/pgp-signature: FAILURE -- Start of PGP signed section. > Hello all, > > I get dozens of > Apr 6 10:34:22 blueberry postfix/smtp[2590]: panic: myfree: corrupt or > unallocated memory block > Apr 6 10:34:23 blueberry postfix/qmgr[4313]:

[pfx] Re: secondary MX server

2023-04-02 Thread Wietse Venema via Postfix-users
fh--- via Postfix-users: > > > > > If I remember correctly, someone mentioned NoListing recently on that > > list. > > For this, you *need* a secondary MX, and it is actually your main mail > > server - the primary MX never accepts mail... > > Hallo, > > 1. what's the advantage of this

[pfx] Re: [ext] Re: Issues on incoming queue

2023-03-31 Thread Wietse Venema via Postfix-users
Ralf Hildebrandt via Postfix-users: > * Wietse Venema via Postfix-users : > > > Start by looking for "@domain" wildcards in virtual_alias_maps or > > Somewhat related: I was under the impression that virtual_alias_maps > "@domainA @domainB" did

[pfx] Re: Issues on incoming queue

2023-03-31 Thread Wietse Venema via Postfix-users
Israel britto via Postfix-users: [ Charset ISO-8859-1 converted... ] > Hey, I have a strange problem, my incoming queue is growing and my active and > deferred queues are low on queue items. I checked and I have a lot of > incoming mailer-daemon and double-bounce emails, is there a way to

[pfx] Re: Success DSN for virtual mailboxes not working

2023-03-31 Thread Wietse Venema via Postfix-users
There is a difference in MailScanner logging when a SUCCESS DSN is created and when it is not created. Wietse Venema via Postfix-users: > Nuno Pereira via Postfix-users: > > Logs of message with success DSN sent: > > > > Mar 31 13:26:16 MAIL01 postfix/cleanup[110]: 2106

[pfx] Re: Success DSN for virtual mailboxes not working

2023-03-31 Thread Wietse Venema via Postfix-users
Nuno Pereira via Postfix-users: > Logs of message with success DSN sent: > > Mar 31 13:26:16 MAIL01 postfix/cleanup[110]: 21069213F: > message-id= uYAAA4AABB+0ZLW85dyTYzsfdF+fjJNAQA=@otherdomain.com> > Mar 31 13:26:19 MAIL01 MailScanner[1402982]: Requeue: 21069213F.A0295 to >

[pfx] Re: Success DSN for virtual mailboxes not working

2023-03-31 Thread Wietse Venema via Postfix-users
Nuno Pereira via Postfix-users: > > De: Wietse Venema via Postfix-users > > Enviada: 30 de mar?o de 2023 21:25 > > Para: Postfix users > > Assunto: [pfx] Re: Success DSN for virtual mailboxes not working > > > > Nuno Pereira via Postfix-users: > >

[pfx] Re: Success DSN for virtual mailboxes not working

2023-03-30 Thread Wietse Venema via Postfix-users
Nuno Pereira via Postfix-users: > Hello. > > We have a setup where postifix is configured to send all mails sent to domain > virtualdomain.com are virtual and sent to realdomain.com. > > This is done with the following configuration: > > virtual_alias_domains = virtualdomain.com > >

[pfx] Re: max_use and smtp connection cache

2023-03-28 Thread Wietse Venema via Postfix-users
Amit Gupta via Postfix-users: > Is there any relation between max_use and the smtp connection cache? C None whatsoever. The max_use parameter specifies a limit for number of consequtive client connections that a short-lived Postfix daemon process will handle before it terminates. For example, a

[pfx] Re: Different set of milters for one domain?

2023-03-28 Thread Wietse Venema via Postfix-users
Dan Mahoney (Gushi) via Postfix-users: > Hey there all, > > Dayjob sometimes receives mail for one domain that we'd like to have > bypass certain milters (specifically, we want to exempt them from some > filtering/scanning mitlers since the domain is pretty much entirely > passthrough) -- The

[pfx] Re: destination based rate limiting

2023-03-27 Thread Wietse Venema via Postfix-users
Gino Ferguson via Postfix-users: > Hi, > > How can one set up outbound rate limiting for a certain mail service > provider? Did you mean concurrency limit (number of parallal deliveries) or rate limit (for example, number of deliveries per minute)? > Can postfix 'recognise' that

[pfx] Re: smtp_tls_security_level per user

2023-03-25 Thread Wietse Venema via Postfix-users
postfix--- via Postfix-users: > smtp_tls_security_level = may/encrypt sets global policy for the > server. Is there a way to override that on a per user basis when > delivering mail to another public server? For example if the server > default is "may" can email being sent from

[pfx] Re: difference between relay and smtp

2023-03-22 Thread Wietse Venema via Postfix-users
Gino Ferguson via Postfix-users: > Hi, > > > Can you explain me the practical difference between relay and smtp delivery > on a relay server? Background for what is different: https://www.postfix.org/ADDRESS_CLASS_README.html Wietse ___

[pfx] Re: timeout after END-OF-MESSAGE

2023-03-20 Thread Wietse Venema via Postfix-users
Fourhundred Thecat via Postfix-users: > Hello, > > I occasionally see timeout after END-OF-MESSAGE in my logs: > >timeout after END-OF-MESSAGE from mail-lf1-f49.google.com[209.85.167.49] >disconnect from mail-lf1-f49.google.com[209.85.167.49] ehlo=2 > starttls=1 mail=1 rcpt=1 bdat=1

[pfx] Re: Allow TLSv1 only for internal senders

2023-03-18 Thread Wietse Venema via Postfix-users
If you must (not necessariy a god idea), your options are: - Multiple Posifix instances on different IP addresses. Each instance has its own main.cf and master.cf. - Single Postfix instance with different smtpd configurations in master.cf on different server IP addresses, using main.cf only for

[pfx] Re: Improper use of SMTP command pipelining

2023-03-16 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > William Bowden via Postfix-users: > > I have disabled reject_unauth_pipelining to no avail the server appears to > > be one of the big boys server any clues or ideas to allow this through. > > > > Prove it. Show output > >

[pfx] Re: Improper use of SMTP command pipelining

2023-03-16 Thread Wietse Venema via Postfix-users
William Bowden via Postfix-users: > I have disabled reject_unauth_pipelining to no avail the server appears to > be one of the big boys server any clues or ideas to allow this through. > Prove it. Show output postconf -n postconf -P Also, Postfix should log this: improper

[pfx] Re: /etc/postfix/access only doamin is blocked

2023-03-15 Thread Wietse Venema via Postfix-users
Gerd Hoerst via Postfix-users: > Hi ! > > in email source text is > > From: Der heutige Gewinner! That is is a header, that not used in SMTPD access maps. Look in your logs for from=. THAT is the address in the SMTP RCPT TO command that ia uaws in SMTPD access maps. Wietse

[pfx] Re: /etc/postfix/access only doamin is blocked

2023-03-15 Thread Wietse Venema via Postfix-users
Gerd Hoerst via Postfix-users: > > domain.com DISCARD Spam rule domain block > > .domain.com DISCARD Spam rule domain block > > as is wrote? i tried with both versions , depending on my setting in > parent_domain_matching_subdomains both did not work.. How would we know that you did

[pfx] PATCH: check_ccert_access fails when table spec contains spaces inside braces

2023-03-14 Thread Wietse Venema via Postfix-users
Sean Gallagher via Postfix-users: > I have been trying to understand why check_ccert_access does not work > with an inline:{} table and I believe I have uncovered a subtle bug. > > My investigation has focused on > https://github.com/vdukhovni/postfix/blob/master/postfix/src/global/map_search.c

[pfx] Re: use object storage as message store

2023-03-12 Thread Wietse Venema via Postfix-users
Steffen Nurpmeso via Postfix-users: > Postfix users wrote in > <4pzsd16nkpzj...@spike.porcupine.org>: > ... > |Postfix must wait for fsync() to complete (or whatever its Cloud > |equivalent is), before it can take responsibility for delivery of > > (postfix does not support FULLFSYNC on

[pfx] Re: use object storage as message store

2023-03-12 Thread Wietse Venema via Postfix-users
Demi Marie Obenour via Postfix-users: > On 3/12/23 01:21, Bill Cole via Postfix-users wrote: > > On 2023-03-12 at 00:03:32 UTC-0500 (Sun, 12 Mar 2023 00:03:32 -0500) > > Phil Stracchino via Postfix-users > > is rumored to have said: > > > >> On 3/11/23 19:04, pyh--- via Postfix-users wrote: >

[pfx] Re: Integrating a new milter with Postfix

2023-03-12 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > EML via Postfix-users: > > I've written a before-queue milter that I'm trying to integrate with > > Postfix, but there doesn't seem to be any specific documentation on how > > to do this. During development, I ran the milter manually, l

[pfx] Re: Integrating a new milter with Postfix

2023-03-12 Thread Wietse Venema via Postfix-users
EML via Postfix-users: > I've written a before-queue milter that I'm trying to integrate with > Postfix, but there doesn't seem to be any specific documentation on how > to do this. During development, I ran the milter manually, listening on > port 7950, with nothing in master.cf, and this in

[pfx] Re: mailman mangling (Was: Re: milter: could it splice (, somehow)?)

2023-03-11 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > Steffen Nurpmeso via Postfix-users: > > Steffen Nurpmeso wrote in > > <20230311005401.bynjz%stef...@sdaoden.eu>: > > ... > > |>From [.] > > This is part of the mbox format, and most likely happens at your end. >

[pfx] Re: mailman mangling (Was: Re: milter: could it splice (, somehow)?)

2023-03-11 Thread Wietse Venema via Postfix-users
Steffen Nurpmeso via Postfix-users: > Steffen Nurpmeso wrote in > <20230311005401.bynjz%stef...@sdaoden.eu>: > ... > |>From [.] This is part of the mbox format, and most likely happens at your end. The Postfix-Mailman interface uses LMTP which requires no such quoting. Wietse

[pfx] Re: Sender Caninical Condition

2023-03-10 Thread Wietse Venema via Postfix-users
SysAdmin EM via Postfix-users: > Good days, request help, is it possible to use conditions in the > sender_canonical file? we are migrating an entire system and some customers > do not have our SPF added. > > I would like to add a condition for you to rewrite the from when it does > not match a

[pfx] Re: milter_header_checks + WARN length limit

2023-03-10 Thread Wietse Venema via Postfix-users
Aleksandr Stankevic: > Hi, > > I understand that there's always a limit - this is expected. > But the unexpected part was that the limit is very different on same-ish > functions. > I think making the limit the same for both scenarios would be best - if > either 60 or 200 ( more preferred :P ).

[pfx] The joke writes itself

2023-03-09 Thread Wietse Venema via Postfix-users
Wietse Venema via Postfix-users: > Peter via Postfix-users: > > I think that [postfix] or [postfix-users] and [postfix-devel] > > [postfix-announce] are just fine, but if you want shortened versions, > > might I suggest: > > > > [pf] [pf-dev] [pf-ann] > >

[pfx] Re: [P-U] Re: The joke writes itself.

2023-03-09 Thread Wietse Venema via Postfix-users
Peter via Postfix-users: > I think that [postfix] or [postfix-users] and [postfix-devel] > [postfix-announce] are just fine, but if you want shortened versions, > might I suggest: > > [pf] [pf-dev] [pf-ann] Changed to: [pfx], [pfx-dev], [pfx-ann] Wietse

[P-U] Re: The joke writes itself.

2023-03-09 Thread Wietse Venema via Postfix-users
Peter via Postfix-users: > On 10/03/23 10:04, Dan Mahoney via Postfix-users wrote: > > I know that P-U stands for postfix users. I get it that a short subject > > tag was desired, but would [postfix] have been that much more distracting, > > without adding the obvious third-grader label that

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Wietse Venema via Postfix-users
Gerald Galster via Postfix-users: > > This list uses Mailman configuration settings, not handcrafted code. > > If people believe that it is worthwhile to change the Mailman > > implementation or the DMARC spec, then I suggest that they work > > with the people responsible for that. > > There is

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Wietse Venema via Postfix-users
This list uses Mailman configuration settings, not handcrafted code. If people believe that it is worthwhile to change the Mailman implementation or the DMARC spec, then I suggest that they work with the people responsible for that. Wietse ___

[P-U] Re: milter_header_checks + WARN length limit

2023-03-09 Thread Wietse Venema via Postfix-users
Aleksandr Stankevic via Postfix-users: > Hi, > > I've got a milter that, as part of the job, adds an X-Test-Tracking header > with a 76 char length string. > Then, in postfix, i've got a milter_header_checks which uses WARN to log > this to logs, like: > /^X-Test-Tracking/ WARN > I've noticed

[P-U] Re: New List Host and Reply-to Header

2023-03-09 Thread Wietse Venema via Postfix-users
postfix--- via Postfix-users: > Is it the best idea to add a reply-to header to the author on mailing list > emails? > The problem I see is many people will hit reply in their email client which > will create an email from them to the author, bypassing the mailing list. > Unless they remember to

[P-U] Re: Postfix lists are migrating to a new list server

2023-03-09 Thread Wietse Venema via Postfix-users
Michael via Postfix-users: > wietse, > > On Monday, 6 March 2023 17:08:49 CET, Wietse Venema wrote: > > This week, the Postfix mailing lists will be migrated from Majordomo at > > Cloud9.net to Mailman at Sys4.de. > > [...] > > what a coincidence! Let me help r

[P-U] Re: Postfix lists are migrating to a new list server

2023-03-07 Thread Wietse Venema via Postfix-users
Gerald Galster via Postfix-users: > The tab "Archiving" under "List Settings" offers "Archive policy": > "Public archives", "Private archives", "Do not archive this list". These settings are mutually exclusive, i.e. the setting "Private archives" turns OFF "Do not archive this list". The correct

[P-U] Re: Postfix lists are migrating to a new list server

2023-03-07 Thread Wietse Venema via Postfix-users
Gerald Galster via Postfix-users: > > >> Out of sheer curiosity ... Mailman 2 or 3? > > > > Mailman 3 with ARC support enabled. Additionally all listmail will be DKIM > > signed. > > Do you plan to enable a public archive at > https://list.sys4.de/hyperkitty/list/postfix-us...@de.postfix.org/

[P-U] Postfix lists have migrated to a new list manager

2023-03-07 Thread Wietse Venema via Postfix-users
The Postfix mailing list migration should be complete by now, except for some old messages that may still be queued on some mail servers. I'll manually handle any sub/unsubscribe requests that may still arrive at the old address. See below for the pre-migration announcement, with a summary of

Re: Cyrus LMTP delivery and DSN's

2023-03-07 Thread Wietse Venema
Peter Wienemann: > Dear Wietse, > > On 24.02.23 22:57, Wietse Venema wrote: > > You need to configure the Postfix LMTP client that it is doing final > > delivery (LMTP does not assume that every delivery is final, they > > could be to a content filter instead). &

Re: Postfix lists are migrating to a new list server

2023-03-06 Thread Wietse Venema
Fongaboo: > > Did CLOUD9.NET finally close up shop? They were my first dial-up > shell account. I'm still their customer. I think they left the market for dialup, shell, and email accounts. Wietse > On Mon, 6 Mar 2023, Wietse Venema wrote: > > > This week, the

Postfix lists are migrating to a new list server

2023-03-06 Thread Wietse Venema
This week, the Postfix mailing lists will be migrated from Majordomo at Cloud9.net to Mailman at Sys4.de. Thanks to Cloud9.net for hosting the Postfix lists for 24 years, and thanks to Sys4 for being the new host. This is the pre-migration announcement. If you don't receive a post-migration

Re: Problem to receive mail from gmail

2023-03-06 Thread Wietse Venema
Di Battista Francesco: > It is possible the problem is mx server? Is your mail server's IP address a consumer IP address or a business IP address? Maybe that makes a difference for gmail. Are you sure that you gave gmail the right email address? Wietse

Re: limit sending to known domains

2023-03-06 Thread Wietse Venema
mailm...@ionos.gr: > > Hello everyone, > > My current postfix configuration allows an authenticated (SASL) user to send > emails with any From: address. > > 1) Is there a way to limit From: addresses to known/configured > (virtual_mailbox_domains) domains only? Postfix does not limit

Re: Problem to receive mail from gmail

2023-03-06 Thread Wietse Venema
Di Battista Francesco: > Hi all, > I have configured a new postfix server. > It works fine, but I can't receive mail only from gmail. > > When I send email from gmail, I do not receive an error message. If your log shows no connections from a Google mail server IP address then a) Google mail

Re: Transport maps - lookups happen for recipient but also for sender (which is not necessary)

2023-03-03 Thread Wietse Venema
liquid cooled: > Thanks for the quick response, > > 2) $ postconf -n | grep ldap > transport_maps = hash:/etc/postfix/lookup/transport, ldap:/etc/postfix/ > mailtransport.cf In that case, Postfix will always want to look up user@domain, domain, and parent domains, because that is how transport

Re: Transport maps - lookups happen for recipient but also for sender (which is not necessary)

2023-03-03 Thread Wietse Venema
liquid cooled: > Hello, > > I found out that my postfix does a lot of useless (LDAP) requests (in my > opinion) when transport maps are enabled and in place. > I use transport maps to map incoming mails to different destination hosts, > based on destination mail address. > So there should be no

Re: (GNU) egrep is obsolescent

2023-03-02 Thread Wietse Venema
Steffen Nurpmeso: > Hello. > > I do not think this has been reported already, on systems which > use GNU grep(1) postfix produces obsoletion messages. > > $ egrep x y > egrep: warning: egrep is obsolescent; using grep -E This was updated months ago in Postfix 3.8 and on-line documentaton.

Re: Helo reject working?

2023-03-02 Thread Wietse Venema
Alberto: > Except, as in this case, when the would-be sender tries an unsupported > command, e.g. AUTH. It's really not feasible to postpone rejection in > those cases. > > > +1 > I've changed "smtp_delay_reject" directive to "no", because there are too > many connections with this approach. >

Re: postfix-mysql is installed but getting: unsupported dictionary type: mysql

2023-02-28 Thread Wietse Venema
Jonathan Capra: > Turns out, when trying to set up for some rsyncing of config files to my > secondary server, I added ACLs to the contents of /etc/postfix. Turns out > postfix does not like if any non-root user has access to dynamicmaps.cf. > > It was still owned by root outright, but the

Re: Cyrus LMTP delivery and DSN's

2023-02-27 Thread Wietse Venema
Ken Smith: > > Wietse Venema wrote: > > {snip} > >> But senders are not getting DSN's > > Why should Postfix send those? > > > > - What delivery status notifications did a remote SMTP client > > request in the RCPT TO command? > > > > - Wh

Re: Outgoing content-filter

2023-02-27 Thread Wietse Venema
Rafael Azevedo: > Wietse, > Also I've noticed that when the filter is applied it kinds of groups the > pipe process per domain. Indeed. It would be wasteful to filter the same message mutilple times. Wietse

Re: Outgoing content-filter

2023-02-27 Thread Wietse Venema
Wietse Venema: > That is evendence that content_filter is not being used. Are you > aware that your "smtpd -o content_filter=blah" will only process > messages that arrive via SMTP port 25? Rafael Azevedo: > Hi Wietse, thanks for the reply. > > Yes I am. And this m

Re: resolving IP addresses of connecting clients

2023-02-27 Thread Wietse Venema
Fourhundred Thecat: > > On 2023-02-27 15:08, Wietse Venema wrote: > > Fourhundred Thecat: > >> > >> The problem is, postfix does not seem to distinguish between IP having > >> no DNS record, and my DNS server being temporarily unavailable. > > &g

Re: Outgoing content-filter

2023-02-27 Thread Wietse Venema
Rafael Azevedo: > Even running this as the filter-script it just doesn't work: > > #!/bin/bash > # Localize these. > echo Message content rejected; > exit 75; > > > The message goes to final recipient instead of being rejected. That is evendence that content_filter is not being used. Are you

Re: double extensions

2023-02-27 Thread Wietse Venema
Sorry, we do not accept double extension file type img. Sorry, these patterns don't work. Use the header_checks manpage example instead. Wietse > > W dniu 27.02.2023 o 15:56, Wietse Venema pisze: > > natan: > >> Hi > >> I gat many many e-mails with virus an

Re: double extensions

2023-02-27 Thread Wietse Venema
natan: > Hi > I gat many many e-mails with virus and double exstension like: > *.jpg.img > *.pdf.img > *.*.img > > I try in header_checks.pcre > [broken regexp omitted] > > and not working The following blocks a 'bad' extension before a 'good' one such as 'name.exe.pdf'. 1) Take the example

Re: Cyrus LMTP delivery and DSN's

2023-02-27 Thread Wietse Venema
Ken Smith: > and I can see these lines are now being added to the delivered e-mail > headers > > Delivered-To: k...@kensnet.org > X-Original-To: k...@kensnet.org > > But senders are not getting DSN's Why should Postfix send those? - What delivery status notifications did a remote SMTP client

Re: resolving IP addresses of connecting clients

2023-02-27 Thread Wietse Venema
Fourhundred Thecat: > Hello, > > I am using simple python script to parse postfix logs, and ban offending > IP addresses. One of the patterns I am matching is unknown host: > > NOQUEUE: reject: RCPT from unknown[195.133.40.183]: 450 4.7.25 > Client host rejected: cannot find your hostname >

Re: is a cidr table red as a textfile by postfix?

2023-02-26 Thread Wietse Venema
HCImap: > hi, > > I am configuring a postfix-based mailserver at home, using the > docker-based mailserver > > https://github.com/docker-mailserver/docker-mailserver > > Under the hood the version is: > > # postconf mail_version > mail_version = 3.5.17 > > I am trying to use a cidr table to

Re: Issues creating makefile - lines commented out

2023-02-25 Thread Wietse Venema
James Brown: > > On 25 Feb 2023, at 12:09 pm, Wietse Venema wrote: > > > > James Brown: > >> Now it just has one error: > >> > >> dict_mysql.c:171:10: fatal error: 'mysql.h' file not found > >> #include > >> ^~~~

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
James Brown: > Now it just has one error: > > dict_mysql.c:171:10: fatal error: 'mysql.h' file not found > #include > ^ > 1 error generated. > make: *** [dict_mysql.o] Error 1 > make: *** [update] Error 1 > > % locate mysql.h >

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
Viktor Dukhovni: > On Fri, Feb 24, 2023 at 10:41:01AM -0500, Wietse Venema wrote: > > > I have to retract my comment aobut changes to shells. The behavior > > of backslash-newline inside 'string' (single quotes) is to preserve > > the backslash and the newline i.e. the

Re: Cyrus LMTP delivery and DSN's

2023-02-24 Thread Wietse Venema
Ken Smith: > Hi, first post to this list but long term Linux user here. > > I have Postfix configured for virtual domains and delivery to cyrus-imap > via LMTP over IP. All is working well besides one detail. > > It seems that when senders request a DSN they do not get any response. > I've

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
Norton Allen: > On 2/24/2023 12:27 AM, James Brown wrote: > > Sorry if this is a bit of a basic question, but I?m trying to compile from > > source on macOS 13.21.1 but the makefile has lines commented out. > > > > I?m trying: > > > > make -f Makefile.init makefiles \ > > CCARGS='-DUSE_TLS

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
Wietse Venema: > James Brown: > > > On 24 Feb 2023, at 11:57 pm, Wietse Venema wrote: > > > > > > James Brown: > > >> Sorry if this is a bit of a basic question, but I?m trying to compile > > >> from source on macOS 13.21.1 but the makef

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
James Brown: > > On 24 Feb 2023, at 11:57 pm, Wietse Venema wrote: > > > > James Brown: > >> Sorry if this is a bit of a basic question, but I?m trying to compile from > >> source on macOS 13.21.1 but the makefile has lines commented out. > >> >

Re: postfix header check question

2023-02-24 Thread Wietse Venema
Wietse Venema: > Spam Petya: > > Hi! > > > > I am still getting NDR-s. I uploaded come ndr header to a txt file to test > > with postmap, and I am seeing the REJECT, so the header_check is working if > > I understand right. > > I used this command to test

Re: postfix header check question

2023-02-24 Thread Wietse Venema
Spam Petya: > Hi! > > I am still getting NDR-s. I uploaded come ndr header to a txt file to test > with postmap, and I am seeing the REJECT, so the header_check is working if > I understand right. > I used this command to test: postmap -vq - > regexp:/etc/postfix/header_checks < uploaded_text.txt

Re: Issues creating makefile - lines commented out

2023-02-24 Thread Wietse Venema
James Brown: > Sorry if this is a bit of a basic question, but I?m trying to compile from > source on macOS 13.21.1 but the makefile has lines commented out. > > I'm trying: > > make -f Makefile.init makefiles \ > CCARGS='-DUSE_TLS -DUSE_SASL_AUTH \ ... > -DHAS_MYSQL

Re: Switching from sender_dependant_relayhost_map to a content-filter

2023-02-22 Thread Wietse Venema
itan...@univ-brest.fr: > > Le 22/02/2023 ? 15:18, Wietse Venema a ?crit?: > > itan...@univ-brest.fr: > >> Hello, > >> > >> we're trying to use content-filter instead of > >> sender_dependant_relayhost_map. > > Why? > Previously, this se

Re: Switching from sender_dependant_relayhost_map to a content-filter

2023-02-22 Thread Wietse Venema
itan...@univ-brest.fr: > Hello, > > we're trying to use content-filter instead of > sender_dependant_relayhost_map. Why? > This content-filter sends directly mail, no return to Postfix. When mail is undeliverable, how shall this filter send the non-delivery notification? > We're facing an

Re: issue warning for deferred emails

2023-02-21 Thread Wietse Venema
Doug Denault: > > This command:-+ > > > > postcat -eq 7883F510EBC | grep warning_message_time > > > > If the output is empty, then you did not enable delay warnings. > > > > You may have to specify a different queue ID than 7883F510EBC, if > > that message has already been returned to the

Re: issue warning for deferred emails

2023-02-21 Thread Wietse Venema
Doug Denault: > On Mon, 20 Feb 2023, Wietse Venema wrote: > > > Doug Denault: > >> On Mon, 20 Feb 2023, Wietse Venema wrote: > >> > >>> Doug Denault: > >>>> The most current message (edited for privacy): > >>>> > >>

Re: issue warning for deferred emails

2023-02-20 Thread Wietse Venema
Doug Denault: > On Mon, 20 Feb 2023, Wietse Venema wrote: > > > Doug Denault: > >> The most current message (edited for privacy): > >> > >> Feb 20 09:25:14 freeport postfix/qmgr[88969]: 7883F510EBC: > >> from=, size=1943447, nrcpt=41 (queue ac

Re: issue warning for deferred emails

2023-02-20 Thread Wietse Venema
Doug Denault: > The most current message (edited for privacy): > > Feb 20 09:25:14 freeport postfix/qmgr[88969]: 7883F510EBC: > from=, size=1943447, nrcpt=41 (queue active) > Feb 20 09:25:15 freeport postfix/smtp[67456]: 7883F510EBC: > to=, relay=none, delay=329206, >

Re: issue warning for deferred emails

2023-02-20 Thread Wietse Venema
Doug Denault: > On Sun, 19 Feb 2023, Viktor Dukhovni wrote: > > > On Sun, Feb 19, 2023 at 10:35:43PM -0500, Doug Denault wrote: > > > >> With my setup no warning is deferred errors such as 'time out' or > >> 'Connection refused' until the message is delete from the queue. > >> > >> I added: > >>

Re: A user is unknown, but I can't find out why

2023-02-18 Thread Wietse Venema
Gerben Wierda: > Feb 18 12:18:44 snape smtp/smtpd[15128]: NOQUEUE: reject: RCPT from > ms11p00im-qufo17282001.me.com[17.58.38.57]: 550 5.1.1 > : Recipient address rejected: User unknown; > from= to= proto=ESMTP > helo= The address is rejected by Postfix SMTP server address validation. I

<    2   3   4   5   6   7   8   9   10   11   >