Re: Setup SquirreMail with Virtual Host

On 19 Jan 2018, at 10:20 (-0500), Rodrigo Cunha wrote: [SNIP: NOTHING regarding Postfix!] What you posted is all Apache HTTPD configuration. Your problems appear to be with SquirrelMail, a webmail application that interacts with a web server (i.e Apache HTTPD) an IMAP server (maybe

Re: Cyrus vs Dovecot for SASL AUTH and IMAP

On 16 Jan 2018, at 17:19 (-0500), J Doe wrote: Hi, I am looking to use either Cyrus or Dovecot for both SASL authentication and IMAP. While Postfix 3.1.0 supports both, I was wondering which to prefer if security is my most important deciding factor ? Does one have a better track record

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-20, Viktor Dukhovni wrote: >> On Jan 19, 2018, at 6:10 PM, Grant Edwards wrote: >> >>> Note that with my suggestion to override "default_transport" not only the >>> original messages, but also any bounces or delay notifications

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

> On Jan 19, 2018, at 6:10 PM, Grant Edwards wrote: > >> Note that with my suggestion to override "default_transport" not only the >> original messages, but also any bounces or delay notifications go out via >> the same transport. > > Ah. That's a problem. I would

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-19, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 5:48 PM, Grant Edwards wrote: >> >> >> It does some stuff via the ssh-2 protocol. > > Note that with my suggestion to override "default_transport" not only the > original

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

> On Jan 19, 2018, at 5:48 PM, Grant Edwards wrote: > > > It does some stuff via the ssh-2 protocol. Note that with my suggestion to override "default_transport" not only the original messages, but also any bounces or delay notifications go out via the same

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-19, Matus UHLAR - fantomas wrote: > On 19.01.18 19:15, Grant Edwards wrote: >>Becuase postfix doesn't implement the protocols used by that >>command-line utility to transfer the mail to another server via the >>network. > > which one is that? It does some stuff via

Re: Question regarding SASL auth only over TLS in SMTP server

On 1/19/2018 3:21 PM, J Doe wrote: > > /etc/postfix/main.cf > smtpd_sasl_security_options = noanonymous, noplaintext > smtpd_sasl_tls_security_options = noanonymous > smtpd_tls_auth_only = yes Typically one would put all three lines above in main.cf. Although the

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 19.01.18 19:15, Grant Edwards wrote: Becuase postfix doesn't implement the protocols used by that command-line utility to transfer the mail to another server via the network. which one is that? -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to

Question regarding SASL auth only over TLS in SMTP server

Hi, I have a question about enabling SASL authentication in the Postfix SMTP server *ONLY* over TLS. In the documentation [1] under the “Encrypted SMTP session (TLS)” heading, it lists recommended configurations for SASL auth that restrict the SASL mechanisms to noanonymous and noplaintext:

Re: No messages delivered to INBOX [RESOLVED]

On Tue, 16 Jan 2018, Rich Shepard wrote: Running postfix-3.2.4 on Slackware-14.2. My server and workstation are on the same host. Yesterday, about mid-day, messages to me stopped being delivered to my INBOX. /var/spool/mail shows: Earlier today I added another recipe to

Re: postscreen-policy (was: Feature request for postscreen: "defer")

Patrick Ben Koetter: > * Wietse Venema : > > Patrick Ben Koetter: > > > * Wietse Venema : > > > > Wietse Venema: > > > > > Unlike DNS lookups, the access map lookup is a blocking operation, > > > > > and if your tcp map takes 80ms to complete

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-19, Viktor Dukhovni wrote: > On Fri, Jan 19, 2018 at 06:45:29PM +, Grant Edwards wrote: > >> > That'd be magic. How exactly is the command-line MTA supposed to >> > get the mail "relayed" without connecting to a remote host? >> >> Let's not worry about

Re: postscreen-policy (was: Feature request for postscreen: "defer")

* Wietse Venema : > Patrick Ben Koetter: > > * Wietse Venema : > > > Wietse Venema: > > > > Unlike DNS lookups, the access map lookup is a blocking operation, > > > > and if your tcp map takes 80ms to complete (a typical trans-atlantic > > > >

Re: Postfix using all CPU after nightly mail submission

Zach Sheppard: > Wietse: > > I have not made any changes to rsyslog.conf. All it does it redirect all > mail log messages to one log in /var/log/mail which I rotate with a cron > script nightly. However, I do agree that it really could be the only other > process that could be hanging the server.

Re: Postfix using all CPU after nightly mail submission

On Fri, Jan 19, 2018 at 02:04:05PM -0500, Zach Sheppard wrote: > I have not made any changes to rsyslog.conf. All it does it redirect all > mail log messages to one log in /var/log/mail which I rotate with a cron > script nightly. However, I do agree that it really could be the only other >

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 19.01.18 20:20, Viktor Dukhovni wrote: > A pipe(8) transport is the more sensible approach. Given the additional information posted by the OP in the meantime, I agree. -Ralph

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On Fri, Jan 19, 2018 at 08:05:49PM +0100, Ralph Seichter wrote: > "Relaying" implies passing mail to another server via network. Also, I > have no idea why you would not want Postfix to do its job, but anyway: > Postfix can pass incoming mail to a binary during local delivery. You > can for

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-19, Ralph Seichter wrote: > On 19.01.18 19:45, Grant Edwards wrote: > >> Let's not worry about how the command-line MTA works. It has the same >> usage as /usr/bin/sendmail and it works. What I am asking for is an >> SMTP relay server that will relay

RE: Relay via command-line MTA instead of 'relayhost' SMTP server?

If I understand you right, take a look at the transport file in /etc/postfix. My postfix transport table has entries similar to this: example.com smtp:[192.168.1.96] Our mx host(s) accept mail for our domains, then automatically relays it to an internal server which our users access.

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

Grant Edwards: > I'm trying to figure out how to set up an SMTP server that accepts > incoming mail and relays it by invoking a command-line MTA > (e.g. /usr/bin/sendmail or equivalent) instead of connecting to a > 'smarthost' SMTP server. > > Can Postfix do that? Sure. Just set up the TIS

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On Fri, Jan 19, 2018 at 06:45:29PM +, Grant Edwards wrote: > > That'd be magic. How exactly is the command-line MTA supposed to > > get the mail "relayed" without connecting to a remote host? > > Let's not worry about how the command-line MTA works. It has the same > usage as

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 19.01.18 19:45, Grant Edwards wrote: > Let's not worry about how the command-line MTA works. It has the same > usage as /usr/bin/sendmail and it works. What I am asking for is an > SMTP relay server that will relay incoming my by invoking it. "Relaying" implies passing mail to another server

Re: Postfix using all CPU after nightly mail submission

Wietse: I have not made any changes to rsyslog.conf. All it does it redirect all mail log messages to one log in /var/log/mail which I rotate with a cron script nightly. However, I do agree that it really could be the only other process that could be hanging the server. I'm not able to determine

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

On 2018-01-19, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 1:15 PM, Grant Edwards wrote: >> >> I'm trying to figure out how to set up an SMTP server that accepts >> incoming mail and relays it by invoking a command-line MTA >> (e.g.

Re: Relay via command-line MTA instead of 'relayhost' SMTP server?

> On Jan 19, 2018, at 1:15 PM, Grant Edwards wrote: > > I'm trying to figure out how to set up an SMTP server that accepts > incoming mail and relays it by invoking a command-line MTA > (e.g. /usr/bin/sendmail or equivalent) instead of connecting to a > 'smarthost'

Relay via command-line MTA instead of 'relayhost' SMTP server?

I'm trying to figure out how to set up an SMTP server that accepts incoming mail and relays it by invoking a command-line MTA (e.g. /usr/bin/sendmail or equivalent) instead of connecting to a 'smarthost' SMTP server. Can Postfix do that? -- Grant Edwards grant.b.edwards

Re: Postfix using all CPU after nightly mail submission

Zach Sheppard: > However, whenever Postfix gets a large e-mail load it processes the e-mails > for around 30-45 minutes and then consistently uses around 70-80% of the > CPU effectively locking up the entire system so much so that I can't even > login and debug without either disabling the network

Re: Postfix using all CPU after nightly mail submission

On 19 January 2018 at 16:02, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 10:58 AM, Dominic Raferd wrote: >> >>> The pipes to "sort" should not be needed. The output of "postconf" is >>> pre-sorted. >> >> yes I thought that - but

Re: Postfix using all CPU after nightly mail submission

> On Jan 19, 2018, at 10:58 AM, Dominic Raferd wrote: > >> The pipes to "sort" should not be needed. The output of "postconf" is >> pre-sorted. > > yes I thought that - but without piping through sort I see: > $ comm -1 -2 <(postconf -n) <(postconf -d) > comm: file

Re: Postfix using all CPU after nightly mail submission

On 19 January 2018 at 15:55, Viktor Dukhovni wrote: > > >> On Jan 19, 2018, at 10:46 AM, Dominic Raferd wrote: >> >> Here's a way to check for explicit settings in main.cf that are >> actually defaults and so could be removed (works under

Re: Postfix using all CPU after nightly mail submission

> On Jan 19, 2018, at 10:46 AM, Dominic Raferd wrote: > > Here's a way to check for explicit settings in main.cf that are > actually defaults and so could be removed (works under bash): > > comm -1 -2 <(postconf -n|sort) <(postconf -d|sort) The pipes to "sort" should

Re: Postfix using all CPU after nightly mail submission

On 19 January 2018 at 15:21, Viktor Dukhovni wrote: > > > > > default_destination_concurrency_limit = 50 > > This is the default, remove the setting. > > ... Here's a way to check for explicit settings in main.cf that are actually defaults and so could be removed

Re: Debian Stretch reboot problem

Black Sheep, 19.01.2018 16:28 +0100: > Does anyone know a robust workaround for the bug in Debian Stretch whereby on > reboot Postfix services do not fully start, and mail is not accepted? It’s > recorded as bug#877992 but there seems to have been no solution through a > number of upgrades. #

Debian Stretch reboot problem

Does anyone know a robust workaround for the bug in Debian Stretch whereby on reboot Postfix services do not fully start, and mail is not accepted? It’s recorded as bug#877992 but there seems to have been no solution through a number of upgrades. It’s especially a nuisance right now with

Re: Postfix using all CPU after nightly mail submission

> On Jan 19, 2018, at 9:55 AM, Zach Sheppard > wrote: > > bounce_queue_lifetime = 0 This is a bad idea. Don't do that. Allow transient delivery failures to be retried. > default_destination_concurrency_limit = 50 This is the default, remove the setting. >

Re: Setup SquirreMail with Virtual Host

Report Feedback for solution this problem: postfix with suport squirrelmail in apache2. Considerations: My LAMP(in DEBIAN 7) IP:192.168.2.50 configuration in my bind(DNS Autorytative): step 1: setup my mail in DNS: vim db.oduvaldocozzi.intranet mail IN A 192.168.2.50 oduvaldocozzi.intranet. IN

Re: Postfix using all CPU after nightly mail submission

> On Jan 19, 2018, at 8:52 AM, Zach Sheppard > wrote: > > Jan 15 00:42:42 mailrelay postfix/qmgr[5601]: 8EF0980973: > from=<...@oconee.k12.sc.us>, size=2408, nrcpt=1 (queue >

Re: Postfix using all CPU after nightly mail submission

Hi Bastian, I did read that debug readme and saw the following: >> If you can't use a test email address, please anonymize email addresses and host names consistently. Replace each letter by "A", each digit by "D" so that the helpers can still recognize syntactical errors. ...and is why I

Re: Postfix using all CPU after nightly mail submission

On Fri, 19 Jan 2018, Bastian Blank wrote: Date: Fri, 19 Jan 2018 22:06:15 From: Bastian Blank To: postfix-users@postfix.org Subject: Re: Postfix using all CPU after nightly mail submission On Fri, Jan 19, 2018 at 08:52:39AM -0500, Zach Sheppard

Re: Postfix using all CPU after nightly mail submission

On Fri, Jan 19, 2018 at 08:52:39AM -0500, Zach Sheppard wrote: > I see no errors or alarms in the mail log nor syslog. The only odd message > I see is a series of ^@ symbols before the system freezes: Please read http://www.postfix.org/DEBUG_README.html#mail about how to report problems. > Jan

Postfix using all CPU after nightly mail submission

Hello, We use a Postfix installation on Debian 9 in our network to serve as a send-only SMTP server for a very large application in our school district. This application does not have its own built-in SMTP server and requires a relay to send notification e-mails to students, teachers, and parents

Re: Setup SquirreMail with Virtual Host

I recommend you post this in the "Apache users" list instead. On 2018-01-18 21:33, Rodrigo Cunha wrote: > Dear, i have a problem in config vhost squirremail. > I'm following the steps in the tutorial > [http://www.100security.com.br/postfix-squirrelmail-outlook/ >