On Sun, Feb 15, 2015 at 09:03:17PM -0700, Sherman Boyd wrote:
> > * Define "incoming" mail.
> > * Define "outgoing" mail.
>
> Incoming: from outside via SMTP
At what point in processing to you want the ligths to blink?
* Beginning of mail transaction?
* Queue file creation?
* Comp
> * Define "incoming" mail.
> * Define "outgoing" mail.
Incoming: from outside via SMTP
Outgoing: to outside via SMTP
Best regards,
Sherman Boyd
On Sun, Feb 15, 2015 at 10:10 AM, Viktor Dukhovni <
postfix-us...@dukhovni.org> wrote:
> On Sun, Feb 15, 2015 at 09:29:50AM -0700, Sherman Boyd wr
On 2/15/2015 10:29 AM, Sherman Boyd wrote:
> Hello. I'm working on a little ARM server that runs Postfix. On
> incoming or outgoing email I want to trigger an animation on an
> attached ring of LEDs. My first attempt was to follow the approach
> here (content filter re-injecting with sendmail) :
Viktor Dukhovni:
> On Sun, Feb 15, 2015 at 03:44:45PM -0500, Wietse Venema wrote:
>
> > Viktor Dukhovni:
> > > On Sun, Feb 15, 2015 at 02:08:58PM -0500, Wietse Venema wrote:
> > >
> > > > Excellent. We narrowed down the problem to the VSTREAM_GETC() call,
> > > > established why the call failed,
On Sun, Feb 15, 2015 at 03:44:45PM -0500, Wietse Venema wrote:
> Viktor Dukhovni:
> > On Sun, Feb 15, 2015 at 02:08:58PM -0500, Wietse Venema wrote:
> >
> > > Excellent. We narrowed down the problem to the VSTREAM_GETC() call,
> > > established why the call failed, and I added logging in so that
Viktor Dukhovni:
> On Sun, Feb 15, 2015 at 02:08:58PM -0500, Wietse Venema wrote:
>
> > Excellent. We narrowed down the problem to the VSTREAM_GETC() call,
> > established why the call failed, and I added logging in so that
> > this will be easier to diagnose in the future.
>
> Should there be an
> On 15 Feb 2015, at 07:56 , John wrote:
>
> On 2/15/2015 9:40 AM, Mauricio Tavares wrote:
>> On Sun, Feb 15, 2015 at 9:12 AM, John wrote:
>>> A couple of the servers I support are medical offices, and for patient
>>> confidentiality reasons they need to send email out encrypted.
>>> After a l
On Sun, Feb 15, 2015 at 02:08:58PM -0500, Wietse Venema wrote:
> Excellent. We narrowed down the problem to the VSTREAM_GETC() call,
> established why the call failed, and I added logging in so that
> this will be easier to diagnose in the future.
Should there be an explicit flush after the attr_
Mats Luspa:
> Hello!
>
> I've now added your logging code.
>
> That code confirms that it's problems to read socket according to
> logging below ("inside mail_command_client" is my own logging added to
> confirm that I used the correct binary. Thank you for your efforts
> again):
>
> 2015-
On Sun, Feb 15, 2015 at 09:29:50AM -0700, Sherman Boyd wrote:
> Hello. I'm working on a little ARM server that runs Postfix. On incoming
> or outgoing email I want to trigger an animation on an attached ring of
> LEDs. My first attempt was to follow the approach here (content filter
> re-inject
Hello!
I've now added your logging code.
That code confirms that it's problems to read socket according to
logging below ("inside mail_command_client" is my own logging added to
confirm that I used the correct binary. Thank you for your efforts
again):
2015-02-15T17:51:31+02:00 outgoingm
Hello. I'm working on a little ARM server that runs Postfix. On incoming
or outgoing email I want to trigger an animation on an attached ring of
LEDs. My first attempt was to follow the approach here (content filter
re-injecting with sendmail) :
http://blog.thecodingmachine.com/content/triggeri
On 2/15/2015 9:40 AM, Mauricio Tavares wrote:
On Sun, Feb 15, 2015 at 9:12 AM, John wrote:
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in or
Set /mynetworks/ to 127.0.01/8and ::1,removed /permit_mynetworks/ from
relay and recipient restrictions, but had to add to relay_restriction in
amavis setup in master.
everything seems to work.
--
John Allen
KLaM
--
definition: Camel, a horse designed by
On Sun, Feb 15, 2015 at 9:12 AM, John wrote:
> A couple of the servers I support are medical offices, and for patient
> confidentiality reasons they need to send email out encrypted.
> After a lot of discussion they have come to the conclusion that in order to
> avoid accidentally sending confide
pe...@ixp.jp:
> On Feb/12.11:28:57, Wietse Venema wrote:
> > Jean-Christophe Delaye:
> > > "milter.c", line 546: non-constant initializer involving a cast
>
> > 545 static ATTR_OVER_TIME time_table[] = {
> > 546 7 + VAR_MILT_CONN_TIME, DEF_MILT_CONN_TIME, 0, 1, 0,
> > ...
> > And
A couple of the servers I support are medical offices, and for patient
confidentiality reasons they need to send email out encrypted.
After a lot of discussion they have come to the conclusion that in order
to avoid accidentally sending confidential data unencrypted, all email
must be encrypted
Am 15.02.2015 um 13:37 schrieb John:
I think I am asking the wrong question.
What would be the effects of setting /mynetworks/ to 127.0.0.1/8 and
::1/128? I assume that I would need these in order to allow
inter-process communication on the server.
Could I remove the /permit_mynetworks/ stanza
I think I am asking the wrong question.
What would be the effects of setting /mynetworks/ to 127.0.0.1/8 and
::1/128? I assume that I would need these in order to allow
inter-process communication on the server.
Could I remove the /permit_mynetworks/ stanza in my restriction classes
in main?
19 matches
Mail list logo
