Re: Mail forwarding through a relay

On Thu, 12 Sep 2019 at 05:14, John Regan wrote: > Hi, > > I have a postfix-3.2.6 system that acts as a mail server and pop/imap > using dovecot for a small domain. The problem is that people are > increasingly using it as a relay to a personal account, such as Gmail and > Yahoo. > > This is resul

Mail forwarding through a relay

Hi, I have a postfix-3.2.6 system that acts as a mail server and pop/imap using dovecot for a small domain. The problem is that people are increasingly using it as a relay to a personal account, such as Gmail and Yahoo. This is resulting in the receiving system rejecting the message due to SPF fa

Re: message_size_limit, queue_minfree, and mail spool not on root directory

>>> If in doubt, RTFM? >>> >>> queue_minfree (default: 0) >>>The minimal amount of free space in bytes in the queue file system >>> that >>>is needed to receive mail. This is currently used by the Postfix >>> SMTP >>>server to decide if it will accept any mail at all. >

Re: policyd v1 HRP (helo random db)

Benny Pedersen: > https://wiki.policyd.org/checkhelo > > i dont know if it makes sense to add this to postscreen testing ? By design, Postscreen DOES NOT inspect SMTP sessions that are handled by a Postfix SMTP server process. So there is no way for postscreen to count the total number of unique

policyd v1 HRP (helo random db)

https://wiki.policyd.org/checkhelo i dont know if it makes sense to add this to postscreen testing ? will it be to expansive testing it and tracking it ?

Re: EHLO restrictions and address literals

On 11 Sep 2019, at 17:05, J Doe wrote: I glanced briefly to see if there were any other ways to restrict this but none seemed evident to me. Is there a way to achieve this ? As Viktor noted: a pcre check_helo_access map is useful. I have such a map with a few dozen lines of patterns that o

Re: EHLO restrictions and address literals

> On Sep 11, 2019, at 5:05 PM, J Doe wrote: > > Is there a way to achieve this ? Alternatively, should I not be attempting > to do this because legitimate server’s sometimes EHLO address literals ? You could try something like: ... warn_if_reject check_helo_access pcre:${confi

EHLO restrictions and address literals

Hi, I have a question regarding restrictions I can place on EHLO in the smtpd_helo_restrictions parameter. I have a Postfix server that is Internet facing. I periodically receive e-mail where the other MTA sends a EHLO of an address literal. I checked RFC 5321 (SMTP), and confirmed that this

Re: Postfix, Amavis and DKIM body hashes

* Bastian Blank: > Any reason you don't use Amavis for DKIM signing? Over time, I have contributed code to Amavis, OpenDKIM and dkimpy- milter. Right now, I use the latter as a basis, because I need to implement a very flexible DKIM signing mechanism. As you know from your existing merge request,

Re: Question regarding DNSBL behaviour

> On Sep 10, 2019, at 4:41 PM, Bill Cole > wrote: > >> Hello, >> >> I have a question regarding DNSBL usage with the main.cf >> smtpd_client_restrictions parameter. >> >> I have a server configured to check SpamHaus: >> >> main.cf >> . . . >> smtpd_client_restrictions = reject_rbl

[SOLVED] Re: Postfix, Amavis and DKIM body hashes

* Wietse Venema: > Postfix by default converts when it does not see 8BITMIME > support announced in the SMTP "server" EHLO response. Thanks Wietse, "disable_mime_output_conversion=yes" does the trick for me. I was hoping I had missed some configuration switch. -Ralph

Re: Postfix, Amavis and DKIM body hashes

Ralph Seichter skrev den 2019-09-11 21:24: Before filing a bug report for Amavis, I just want to make sure I did not miss some peculiarity of after-queue content filters? google amavisd 8bitmime , so amavisd only and always see 7bit mime, i remember this was it when i used amavisd with amavis

Re: Postfix, Amavis and DKIM body hashes

Ralph Seichter: > # /etc/postfix/master.cf > submission inet n - n - - smtpd >-o smtpd_milters=unix:/run/dkimpy-milter/socket >-o content_filter=amavis:localhost:10124 >[...] > amavis unix - - n - 2 smtp >-o smtp_send_xforward_command=yes You may want to add

Re: Postfix, Amavis and DKIM body hashes

On Wed, Sep 11, 2019 at 09:24:39PM +0200, Ralph Seichter wrote: > Before filing a bug report for Amavis, I just want to make sure I did > not miss some peculiarity of after-queue content filters? Any reason you don't use Amavis for DKIM signing? Bastian -- Bones: "The man's DEAD, Jim!"

Postfix, Amavis and DKIM body hashes

For quite some time, I have used OpenDKIM and lately dkimpy-milter to sign messages entering Postfix via port 587: # /etc/postfix/master.cf submission inet n - n - - smtpd -o smtpd_milters=unix:/run/dkimpy-milter/socket -o content_filter=amavis:localhost:10124 [...] amavis u

Re: Warning mail to sender when seding to hotmail

On 11.09.19 13:28, Ignacio García wrote: We have our servers IPs at OVH IP address-space and from time to time, when we send emails to a small, particular set of very-well-known domains owned by one very large corporation, there are periods where our customer's emails go, by default, to the SPA

Warning mail to sender when seding to hotmail

Hi there We have our servers IPs at OVH IP address-space and from time to time, when we send emails to a small, particular set of very-well-known domains owned by one very large corporation, there are periods where our customer's emails go, by default, to the SPAM folder no-matter-what. Under

Re: message_size_limit, queue_minfree, and mail spool not on root directory

W. Michael Petullo: > > If in doubt, RTFM? > > > > queue_minfree (default: 0) > >The minimal amount of free space in bytes in the queue file system > > that > >is needed to receive mail. This is currently used by the Postfix > > SMTP > >server to decide if it will accep