[pfx] Re: Searching for old Postfix 2.0.6 RPM-packaged for Red Hat 6.2 (classic)

> RHEL 6.2 came with Postfix 2.6.6, not 2.0.6 and you can get a copy from > CentOS vault: No, the question was about "Red Hat Linux", not "Red Hat Enterprise Linux". "Red Hat 6.2" was released long ago in the year 2000. When dealing with such old systems a copy of the cdrom images is helpful in

[pfx] Re: Searching for old Postfix 2.0.6 RPM-packaged for Red Hat 6.2 (classic)

> So I am posting here, to ask whether someone has in his archives an RPM > package of Postfix targeted to Red Hat 6.2 (classic edition)? Try to download and mount the ISO(s). Those included RPM packages back then. https://archive.org/details/disc1_202002 The source seems legit, but use at you

[pfx] Re: [mailop] FYI: nixspam RBL has shutdown

>> [ Repost from "mailop" list ] >> >> Just FYI for those with the nixspam RBL configured in their systems (For >> example it's enabled in rspamd by default) > > Is it safe to assume that it will go away by itself during a future upgrade > of rspamd? > Or should we/I manually remove it from the

[pfx] Re: logging, postlogd

>> With systemd logging, logs are by default lossy (rate-limits too tight >> and many users don't notice until it is too late). Also logging is > > System-wide "defaults to 1 messages in 30s" and "is applied per- > service", so this can be easily resolved by providing postfix.service > with

[pfx] Re: Opening up port 465

> 2024-11-08T16:14:09.034570+01:00 mail postfix/submissions/smtpd[107564]: > connect from unknown[192.168.1.1] > 2024-11-08T16:14:09.040936+01:00 mail postfix/submissions/smtpd[107564]: > SSL_accept error from unknown[192.168.1.1]: -1 > 2024-11-08T16:14:09.042051+01:00 mail postfix/submissions/sm

[pfx] Re: DMARC reports

> I'm sorry that I may have been a bit unclear of my issue. > I'm not confused about receiving the report, but the content of it. > And what to change in my config so that I do not see fail records regarding > mail coming from my own server. > I think I have got what I need from Wietse and are tes

[pfx] Re: DMARC reports

> My server is still rather new, so I have a not so tight policy set up. > And I ask for reports at the dmarc record. You have set the following dmarc record: $ host -t txt _dmarc.jungersen.dk _dmarc.jungersen.dk descriptive text "v=DMARC1; p=none; pct=100; rua=mailto:postmas...@jungersen.dk";

[pfx] Re: Process and deliver email but return error to the client?

>> That is probably because your mailserver's ip reputation >> has not been reset by t-online. Have you ever contacted > > What do you mean with reset? T-Online refused to accept mails from servers > using our own IP ranges with completely new IPs. > There would be nothing to reset. Not having s

[pfx] Re: Process and deliver email but return error to the client?

> we are struggling with t-online.de: Why don't you post the corresponding maillog entry? T-online's smtp error messages are quite elaborate and usually contain an email address that you can contact in case of problems. > As you may know as SMTP client you have to fulfill a bunch of requirements

[pfx] Re: Mails sent to rspamd twice

> Now I have had several suggestions that using amavis is not the preferred way > to go. > > Therefore I started all over. > > Back to where I just had a clean install of clamav and clamav-daemon. > > And of course my working postfix > > I then added: > *** > > clamav { > attachments_onl

[pfx] Re: Mails sent to rspamd twice

> On 2024-09-10 19:10 Danjel Jungersen via Postfix-users: > Den 09.09.2024 kl. 15.14 skrev Wietse Venema via Postfix-users: >> Danjel Jungersen via Postfix-users: >>> On 09-09-2024 13:46, chandan via Postfix-users wrote: On 2024-09-09 10:53, Danjel Jungersen via Postfix-users wrote: > Hey

[pfx] Re: Feature Request: Adjustable Header Log Size Limit in INFO/WARN/REJECT Header_Check

> Viktor Dukhovni via Postfix-users : > > On Wed, Jan 24, 2024 at 08:27:53PM +0100, Matthias Schneider via > Postfix-users wrote: > >> Using a Milter is an option, but it often involves correlating >> information from both the milter process and the log for a >> comprehensive view. > > Everyt

[pfx] Re: IPv6 and Cloud server CPU

> Q2: > given the minuscule work-load, is there any preference/preclusion between > employing the 'usual' x86 processor or 2 Arm Ampere processors? Both offer > Linux. Cost is effectively same. You should check if the software you want to use is available for the desired platform. Distributions

[pfx] Re: postfix does not use the MX of the parent domain

> When sending a mail to some @helpdesk.inria.fr address, postfix tries > to connect to helpdesk.inria.fr (which does not have a MX): > > Nov 21 15:43:26 joooj postfix/smtp[748304]: D1A104A9: > to=<[...]@helpdesk.inria.fr>, relay=none, delay=76462, delays=76431/0.1/30/0, > dsn=4.4.1, status=de

[pfx] Re: Redirecting mail with an mx record containing *.protection.outlook.com or *.prod.outlook.com to a different transport

>> Another option would be to use the DNS resolver (Bind, unbound, etc) >> support to manipulate zone lookups. > > But the OP wants a dedicated transport (for concurrency control and > scheduling), not a change of destination IP, though in a multi-stage MTA > setup that IP could point at a dedic

[pfx] Re: Domain scoring

> Do you know any plugins for scoring a domain? > For example, new registered domain, free domain get the low scores. Postfix is not an antispam solution. Its job is to reliably deliver emails. Therefore it has some functions to avoid overload like query blocklists but to analyze emails use con

[pfx] Re: Deny any sender address with subdomain

> question 1st : is it a good idea to reject any email which is not sent from a > domain (means sen...@domain.tld) any other like sen...@sub.domain.tld or > sub.sub.domain.tld is rejected ? Generally, no, because you will reject legitimate domains that just look like subdomains, e.g. *.co.uk, *

[pfx] Re: forwarding questions

> I have a local real mailbox: u...@foo.com > When I setup this alias map in virtual_alias_maps file: > > u...@foo.com u...@gmail.com > > (then postmap this file). > The message sent to u...@foo.com won't reach into mailbox, but just forwarded > to gmail. > > How can I setup it to both reach lo

[pfx] Re: Sender address rejected, but domain is found?

>> ;; QUESTION SECTION: >> ;eurobank-direktna.rs .IN >> NS >> >> ;; ANSWER SECTION: >> eurobank-direktna.rs . 3600IN NS >> bgdit01edns01.eurobank.rs . >> >> This is

[pfx] Re: Sender address rejected, but domain is found?

>; Delegation NS >eurobank-direktna.rs. IN NS ns1.eurobank.rs. ; AD=0 >eurobank-direktna.rs. IN NS ns2.eurobank.rs. ; AD=0 >eurobank-direktna.rs. IN NS ns3.eurobank.rs. ; AD=0 > >; Authoritative NS >eurobank-direktna.rs. IN NS bgdit01edns01.eurobank.rs. > > The latter host

[pfx] Re: Postfix Amavis (Virus Checker) PHPList workaround

>> content_filter=smtp-amavis:[127.0.0.1]:10024 meta_directory = /etc/postfix >> >> smtp_tls_security_level = may >> smtpd_tls_security_level = may >> [...] > > 127.0.0.1:2510 inet n - n - - smtpd > -o syslog_name=postfix/submission > -o smtpd_sasl_auth_enable=

[pfx] Re: Sender address rejected, but domain is found?

> Hi, I realize this is probably one of the most frequently asked questions, > but I really can't figure out why this was rejected. > > Apr 25 12:06:01 petra postfix-226/smtpd[592344]: NOQUEUE: reject: RCPT from > mail.email.eurobank.rs [195.242.76.237]: 450 > 4.

[pfx] Re: Use of PTR record

> Running mailservice with Postfix > PTR record is set to myserver.mydomain.com (1.2.3.4) Check if your PTR record is traceable: dig +trace -x 1.2.3.4 ptr If that works check your resolver in /etc/resolv.conf, e.g.: nameserver 127.0.0.1 dig @127.0.0.1 -x 1.2.3.4 ptr You have a dns problem, not

[pfx] Re: Postfix Amavis (Virus Checker) PHPList workaround

> Applicable snippets from files are: > > My main.cf > > > content_filter=smtp-amavis:[127.0.0.1]:10024 meta_directory = /etc/postfix > > smtp_tls_security_level = may > smtpd_tls_security_level = may > > > > I did this to master.cf > > 127.0.0.1:2510 inet n - n -

[pfx] Re: Postfix Amavis (Virus Checker) PHPList workaround

> I run a postfix install which requires authentication and pipes all email > through Amavis (spam checking). > > My PHPList (broadcast only) goes through port 587, and since it sits on the > server, it doesn’t need authentication (I’m the only user). > > I just added Amavis Clamscan, which i

[pfx] Re: temporary lookup error with utf8mb4 characters

> Wietse Venema via Postfix-users : > > And here is a more conservative patch for MySQL client retries. > > It closes the server connection after every error, and it delays > making a new server connection only after specific errors. > > Closing the connection eliminates the possibility that t

[pfx] Re: temporary lookup error with utf8mb4 characters

>>> I've patched postfix 3.7.4 on a low volume server. >> >> Thank you! >> >>> "charset" has to be present and defined in all mysql configs, otherwise >>> startup fails: >>> (no backwards compatibility) >>> >>> postfix/proxymap[3996]: fatal: /etc/postfix/test.mysql.cf: bad string >>> length 0

[pfx] Re: temporary lookup error with utf8mb4 characters

> Wietse Venema via Postfix-users : > >>> My conclusion to hard-solve this issue on my system is transform all >>> tables to utf8mb4. >>> >>> But: > >>> - I don't see any option to change default charset on mysql_table >>> connector, maybe should be interesting add this option on configuratio

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

> 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-xforwa

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

> John Levine via Postfix-users : > [...] > If you are a customer, what happened when you contacted them through > their customer support channels and asekd for the support you are > paying for? Web.de is a german freemail provider like gmail. They might provide support for paid accounts only.

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

> one of web.de's sender IPs is listed into zen.spamhaus.org as the following > info. > > 554 5.7.1 Service unavailable; Client host [82.165.159.35] blocked using z > en.spamhaus.org; https://www.spamhaus.org/sbl/query/SBL175032 Try to send your email via web.de (browser), which might use server

[pfx] Re: MySQL error from not all the receiver

> unfortunately I don't know this topic, but I'm really willing to study. > Please do you have any documentation on this? Sorry, I can't recommend an up to date howto. Perhaps other list members can help. A lot of links at https://www.postfix.org/docs.html are outdated or do not exist anymor

[pfx] Re: MySQL error from not all the receiver

> I have checked the commands you listed in your first email, but I do not find > any errors in the database, table, or MySQL service. Perhaps, as you say, > this is not the correct path for the configuration. Currently you are connecting via unix domain sockets. Mysql usually listens to 127.0

[pfx] Re: use object storage as message store

> Is it possible to use an object storage system (like aws's S3) to store > message files? if this can be implemented we may have a more persistent > storage for email. AFAIK aws's S3 has three replicas for each file in their > system by default. At that scale emails are usually delivered via

[pfx] Re: MySQL error from not all the receiver

> smtp_sasl_password_maps is configured with a connection parameter to db > connection and a simply select query. > [...] > if i use external smarthost, this mail is always sent regularly. I am also not sure what you want to achieve: https://www.postfix.org/postconf.5.html#smtp_sasl_password_map

[pfx] Re: MySQL error from not all the receiver

> ok thanks. > > But what is the correct syntax for connect in db to set in sasl_password ? > how should i write it? > > now i try to follow your suggest of the first mail... Try to solve your problem step by step. Currently you are at "Can't connect to local MySQL server". In case your MySQL

[pfx] Re: MySQL error from not all the receiver

> i think the problem is "sasl-password" authentication file. No, your problem is related to mysql which is a database (daemon), that is accessed via sockets, not a file. > [...] > query = SELECT password FROM mailbox WHERE username = '%s' AND active = '1' > > and then "postmap" command. > >

[pfx] Re: MySQL error from not all the receiver

> - postfix/smtp[313760]: warning: connect to mysql server localhost: Can't > connect to local MySQL server through socket '/run/mysqld/mysqld.sock' (2) Have a look at your mysql logs (/var/log/mysql*, journalctl, /var/lib/mysql/*.err). MySQL may not be running, there may be corrupt tables (My

[pfx] Re: milter-reject: END-OF-MESSAGE

> 2023-03-10 11:54:43 #31829(rspamd_proxy) <71bd42>; proxy; > rspamd_task_write_log: id: , qid: <3129536A7A2>, ip: 165.72.200.209, > from: , (default: F (soft reject): [5.31/15.00] > [BAYES_HAM(-2.99){99.97%;},DCC_BULK(2.00){bulk Body=1 Fuz1=4 > Fuz2=many;},MIME_HEADER_CTYPE_ONLY(2.00){},MISSIN

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

> * Patrick Ben Koetter via Postfix-users : > >> * Gerald Galster via Postfix-users > <mailto:list+post...@gcore.biz>>: >> I just wrote that because p@rick (sys4 AG) asked on the mailop mailinglist >> 2023-02-17 "Should mailing list messages be DKIM

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

>>> 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 no need for changing implementatio

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

> They add their own DKIM on top, aka "put an envelope" around "the > message", therefore the mail can be verified (to be from them). That's my point. I do not see a lot of benefit to verify a sender across a *discussion list*. Broken DKIM mails are usually rejected by mta before reaching mailma

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

> 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 no need for changing implementations, it's alrea

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

>> 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 manually alter the To: fi

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

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/ >> as an alternative to marc.info,

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

>> 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/ as an alternative to marc.info, mail-archive.com,