You could simply have a startup script on the local server that connects runs
smtpctl on the remote machine through SSH keys, so the command is run as soon
as the server is started, automatic and no delays.
Hope that helps
-Original Message-
From: Seth [mailto:l...@sysfu.com]
Sent: Wed
On Tue, 27 Jan 2015 21:11:52 -0800, Sunil Nimmagadda
wrote:
I was wondering what if your "local" server is the primary MX and
then your "public" server a backup MX. That way, whenever your local
server is online the mails end up directly in it and your backup
server automatically checks for p
On Tue, Jan 27, 2015 at 08:47:24PM -0800, Seth wrote:
> On Tue, 27 Jan 2015 20:18:04 -0800, Edgar Pettijohn
> wrote:
> >>Still need to solve the problem of scheduling that big morning dump.
> >>
> >>Of email.
> >>
> >cron
>
> That's not really going to work because the power-up time could vary be
On Tue, 27 Jan 2015 20:18:04 -0800, Edgar Pettijohn
wrote:
Still need to solve the problem of scheduling that big morning dump.
Of email.
cron
That's not really going to work because the power-up time could vary
between 2-4 hours. The mail needs to flow as soon as possible after
poweri
On 01/27/15 20:45, Seth wrote:
On Tue, 27 Jan 2015 17:22:43 -0800, Edgar Pettijohn
wrote:
*bounce-warn* /n/{*s*|*m*|*h*|*d*}[, /.../]
Specify the delays for which temporary failure reports must be
generated when messages are stuck in the queue. For example:
bounce-warn1h, 6h,
On Tue, 27 Jan 2015 17:22:43 -0800, Edgar Pettijohn
wrote:
*bounce-warn* /n/{*s*|*m*|*h*|*d*}[, /.../]
Specify the delays for which temporary failure reports must be
generated when messages are stuck in the queue. For example:
bounce-warn 1h, 6h, 2d
will generate a failure rep
On 01/27/15 18:57, Seth wrote:
I administer an email system which uses a VPS running OpenSMTPD as the
public facing bit.
The VPS relays email to and from a separate OpenSMTPD mail server
which is located on premises. We'll call this the 'local' server.
The local server gets powered down eve
I administer an email system which uses a VPS running OpenSMTPD as the
public facing bit.
The VPS relays email to and from a separate OpenSMTPD mail server which is
located on premises. We'll call this the 'local' server.
The local server gets powered down every night, however this currentl
On 27. januar 2015 at 3:58 PM, "Herbert J. Skuhra" wrote:
>
> Please show output of 'smtpd -dv'
It's quite big so I put it here instead:
https://gist.github.com/anonymous/bf9b0a7e935d6e961c05
> and (user's) procmailrc.
I don't have one actually. I'm using this approach:
https://calomel.org/op
Please show output of 'smtpd -dv' and (user's) procmailrc.
On Tue, Jan 27, 2015 at 03:08:40PM +, openda...@hushmail.com wrote:
> I apologize for the inconvenience, but the `procmail: not found` errors are
> still there.
>
> As for aliases, it seems FreeBSD supports both /etc/mail/aliases and
I apologize for the inconvenience, but the `procmail: not found` errors are
still there.
As for aliases, it seems FreeBSD supports both /etc/mail/aliases and
/usr/local/etc/mail/aliases.
O.D.
On 27. januar 2015 at 2:51 PM, openda...@hushmail.com wrote:
>
>On 27. januar 2015 at 1:24 PM, "Herber
On 27. januar 2015 at 1:24 PM, "Herbert J. Skuhra" wrote:
>
>Try /usr/local/etc/mail/aliases instead.
>
Oh man -- that was it! Now getting `delivery: Ok`.
Thank you so much. You and everyone else who chipped in. Time to send some
emails.
All the best,
O.D.
--
You received this mail because
On Tue, Jan 27, 2015 at 01:02:49PM +, openda...@hushmail.com wrote:
> On 27. januar 2015 at 12:49 PM, "Herbert J. Skuhra"
> wrote:
> >
> >1. Create an alias for root and run newaliases.
>
> I already have this (I've also run newaliases):
>
> # cat /etc/mail/aliases
Try /usr/local/etc/mail/
On 27. januar 2015 at 12:49 PM, "Herbert J. Skuhra" wrote:
>
>1. Create an alias for root and run newaliases.
I already have this (I've also run newaliases):
# cat /etc/mail/aliases
root: opendaddy
# Basic system aliases -- these MUST be present
MAILER-DAEMON: postmaster
postmaster: root
# Ge
On Tue, Jan 27, 2015 at 11:48:30AM +, openda...@hushmail.com wrote:
> Hello!
>
> On 27. januar 2015 at 11:21 AM, "Edgar Pettijohn"
> wrote:
> >>>
> >>> Maybe 'smtpd -dv' shows more information?
> >> # smtpd -dv
> >> fatal: control socket already listening
> >>
> >> Thanks!
> >>
> >> O.D.
> >
On Tue, Jan 27, 2015 at 11:10:42AM +, openda...@hushmail.com wrote:
> On 27. januar 2015 at 8:25 AM, "Herbert J. Skuhra"
> wrote:
> >
> >On Mon, Jan 26, 2015 at 11:54:09PM +, openda...@hushmail.com
> >
> >I guess the error does not come from your smtpd.conf, otherwise
> >the log
> >woul
Hello!
On 27. januar 2015 at 11:21 AM, "Edgar Pettijohn"
wrote:
>>>
>>> Maybe 'smtpd -dv' shows more information?
>> # smtpd -dv
>> fatal: control socket already listening
>>
>> Thanks!
>>
>> O.D.
>>
>>
>Remember to "service smtpd stop" first, before this test.
Ah yes! Now we got some action:
On 01/27/15 05:10, openda...@hushmail.com wrote:
On 27. januar 2015 at 8:25 AM, "Herbert J. Skuhra" wrote:
On Mon, Jan 26, 2015 at 11:54:09PM +, openda...@hushmail.com
I guess the error does not come from your smtpd.conf, otherwise
the log
would show:
Jan 26 14:05:20 mybox smtpd[23304]:
On 27. januar 2015 at 8:25 AM, "Herbert J. Skuhra" wrote:
>
>On Mon, Jan 26, 2015 at 11:54:09PM +, openda...@hushmail.com
>
>I guess the error does not come from your smtpd.conf, otherwise
>the log
>would show:
>
>Jan 26 14:05:20 mybox smtpd[23304]: delivery: TempFail for
>cf077883a36bcae2:
I have an issue in a relay configuration.
I have an OpenSMTPD server which authenticate distant users and relaying
their mails to an other SMTP server who is in charge to local delivery or
external relaying.
Below is its configuration :
listen on 127.0.0.1 port submission tls-require auth pki
Hey guys,
I've been trying to get OpenSMTPD to work well with virtual users for a while,
finally got it to work. I wrote a HOWTO for anybody who's interested. It uses
text based files but good for small installations, I currently use this for a
small PHPList server I manage, much less hassle th
On Mon, Jan 26, 2015 at 11:54:09PM +, openda...@hushmail.com wrote:
> Hello,
>
> On 26. januar 2015 at 8:18 PM, "Herbert J. Skuhra"
> wrote:
> >
> >To understand why you get this error run:
> >
> >% whereis procmail | xargs -t ls -l
>
> Indeed, similar to the command parv gave me earlier:
>
22 matches
Mail list logo
