Re: Trash plugin unexpected results

2017-10-16 Thread Stephan H
Something about the calculation is wrong.  The user I was testing with only
had the 1 large email in the trash with a 30 MB quota.  If I need 17.5 MB
and I have a 16MB file I can delete, then removing the file releases enough
space.  It seems as though the trash plugin only accounts for email files
during calculations, not also including quota total.

On Oct 15, 2017 11:27 PM, "Aki Tuomi"  wrote:

> Trash plugin won't delete messages from your folders if the deletion
> would not give enough space to start with, and in your case removing the
> attachment would have still left the user over quota, so trash plugin
> did not take action.
>
> Oct 07 17:33:13 lmtp(31543, 1...@testdo.com): Debug: trash plugin: Failed
> to remove enough messages (needed 17035766 bytes, expunged only 16803594
> bytes)
>
> Aki
>
> On 16.10.2017 09:06, Aki Tuomi wrote:
> > Does indeed sound bit strange, will have to try replicate this to see
> > what happens.
> >
> > Aki
> >
> >
> > On 13.10.2017 23:37, Stephan Herker wrote:
> >> Just wondering if anyone has seen this behavior or if there are some
> >> documents that would let me know the limitations of the trash plugin.
> >> I don't think I'll be commonly using accounts with 30 MB quotas, but I
> >> feel like the trash plugin should account for the whole quota.
> >>
> >> Any help is appreciated.
> >>
> >> On 10/10/2017 8:20 AM, Stephan Herker wrote:
> >>> I have the trash plugin enabled and testing it out I had an account
> >>> with a 30MB quota.  In the accounts trash it had an email with a
> >>> large attachment.  I sent the same email again to the account
> >>> expecting the trash plugin to purge the message from trash to make
> >>> space for the new message in the inbox.  However I got an error
> >>> saying it couldn't remove enough trash to make space.  This behavior
> >>> seems unexpected because it seems like the trash plugin didn't
> >>> account for the quota and size available. Debug logs and dovecot -n
> >>> output below.
> >>>
> >>> SNIP
> >>>
> >>> Any help is appreciated, thanks.
> >>>
>


Re: Trash plugin unexpected results

2017-10-16 Thread Stephan H
Something about the calculation is wrong.  The user I was testing with only
had the 1 large email in the trash with a 30 MB quota.  If I need 17.5 MB
and I have a 16MB file I can delete, then removing the file releases enough
space.  It seems as though the trash plugin only accounts for email files
during calculations, not also including quota total.

On Oct 15, 2017 11:27 PM, "Aki Tuomi"  wrote:

> Trash plugin won't delete messages from your folders if the deletion
> would not give enough space to start with, and in your case removing the
> attachment would have still left the user over quota, so trash plugin
> did not take action.
>
> Oct 07 17:33:13 lmtp(31543, 1...@testdo.com): Debug: trash plugin: Failed
> to remove enough messages (needed 17035766 bytes, expunged only 16803594
> bytes)
>
> Aki
>
> On 16.10.2017 09:06, Aki Tuomi wrote:
> > Does indeed sound bit strange, will have to try replicate this to see
> > what happens.
> >
> > Aki
> >
> >
> > On 13.10.2017 23:37, Stephan Herker wrote:
> >> Just wondering if anyone has seen this behavior or if there are some
> >> documents that would let me know the limitations of the trash plugin.
> >> I don't think I'll be commonly using accounts with 30 MB quotas, but I
> >> feel like the trash plugin should account for the whole quota.
> >>
> >> Any help is appreciated.
> >>
> >> On 10/10/2017 8:20 AM, Stephan Herker wrote:
> >>> I have the trash plugin enabled and testing it out I had an account
> >>> with a 30MB quota.  In the accounts trash it had an email with a
> >>> large attachment.  I sent the same email again to the account
> >>> expecting the trash plugin to purge the message from trash to make
> >>> space for the new message in the inbox.  However I got an error
> >>> saying it couldn't remove enough trash to make space.  This behavior
> >>> seems unexpected because it seems like the trash plugin didn't
> >>> account for the quota and size available. Debug logs and dovecot -n
> >>> output below.
> >>>
> >>> SNIP
> >>>
> >>> Any help is appreciated, thanks.
> >>>
>


Re: hosting emails at home

2017-12-10 Thread Stephan H
I have dovecot postfix setup on my home server as well.  I use a virtual
server in the cloud as my mx record and mail relay and have my home record
on dynamic dns.  It's really effective.

On Dec 10, 2017 2:37 PM, "Fabian A. Santiago" 
wrote:

> On December 10, 2017 2:49:35 PM EST, "André Rodier" 
> wrote:
> >Hello Mike,
> >
> >Yes, I am using a static IP address, but in theory, you could use a
> >dynamic one.
> >
> >Nothing technically would prevent email exchanges between two boxes, as
> >long as the SPF records are up to date and the DKIM is properly setup.
> >
> >Unfortunately, some ISPs are simply blacklisting full range of private
> >IP addresses just because they are not officials / commercials.
> >
> >Kind regards,
> >André
> >
> >On 10/12/17 19:24, Mike wrote:
> >>
> >> Nice.
> >>
> >> Are you using a static IP in this setup?
> >>
> >> It doesn't seem like it, but wanted to be sure.
> >>
> >> Mike.
> >>
> >> Quoting André Rodier :
> >>
> >>> Hello everyone,
> >>>
> >>> I have been using Postfix and Dovecot for my personal emails for
> >years.
> >>> After being tired of reinstalling my personal mail server many
> >times, I
> >>> am currently writing some Ansible scripts to do it automatically.
> >>>
> >>> I obviously checked the other projects, and did not found anything
> >close
> >>> to what I am looking for, so I am implementing it now.
> >>>
> >>> The final goal is to have a box that once online, would setup
> >itself, by
> >>> creating the certificates, the DKIM keys and update the appropriate
> >DNS
> >>> records.
> >>>
> >>> This is so far what I have achieved:
> >>> - Automatic generation of certificates using LetsEncrypt
> >>> - Automatic update of the domain entries: imap, smtp, webmail, etc.
> >>> - Automatic generation of a DKIM keys
> >>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
> >>> - LDAP server for user accounts, with or without system login.
> >>> - Installation of Postfix, Dovecot and Roundcube
> >>>
> >>> Sending DKIM signed emails is working, and the IMAP server is
> >configured
> >>> as well, although basic.
> >>>
> >>> The postfix and dovecot configuration are not yet entirely finished.
> >I
> >>> am planing to add an anti spam system, and sieve, amongst other
> >things.
> >>>
> >>> Although in development during my spare time, the system is normally
> >>> robust and you should be able to run it multiple times without
> >errors.
> >>>
> >>> If anyone is interested to use it, to have a look, or to take part,
> >it
> >>> is here: https://github.com/progmaticltd/homebox
> >>>
> >>> Kind regards,
> >>> André Rodier.
> >>
> >>
>
> Non static ip'd mail servers are also blocked because they're typically
> spammers.
> --
>
> Thanks,
>
> Fabian S.
>
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>


Re: hosting emails at home

2017-12-10 Thread Stephan H
Which part?  Hosting the email server at home or the relay in the cloud?

On Dec 10, 2017 14:53, "Fabian A. Santiago" <fsanti...@garbage-juice.com>
wrote:

> On December 10, 2017 3:39:05 PM EST, Stephan H <her...@gmail.com> wrote:
> >I have dovecot postfix setup on my home server as well.  I use a
> >virtual
> >server in the cloud as my mx record and mail relay and have my home
> >record
> >on dynamic dns.  It's really effective.
> >
> >On Dec 10, 2017 2:37 PM, "Fabian A. Santiago"
> ><fsanti...@garbage-juice.com>
> >wrote:
> >
> >> On December 10, 2017 2:49:35 PM EST, "André Rodier" <an...@rodier.me>
> >> wrote:
> >> >Hello Mike,
> >> >
> >> >Yes, I am using a static IP address, but in theory, you could use a
> >> >dynamic one.
> >> >
> >> >Nothing technically would prevent email exchanges between two boxes,
> >as
> >> >long as the SPF records are up to date and the DKIM is properly
> >setup.
> >> >
> >> >Unfortunately, some ISPs are simply blacklisting full range of
> >private
> >> >IP addresses just because they are not officials / commercials.
> >> >
> >> >Kind regards,
> >> >André
> >> >
> >> >On 10/12/17 19:24, Mike wrote:
> >> >>
> >> >> Nice.
> >> >>
> >> >> Are you using a static IP in this setup?
> >> >>
> >> >> It doesn't seem like it, but wanted to be sure.
> >> >>
> >> >> Mike.
> >> >>
> >> >> Quoting André Rodier <an...@rodier.me>:
> >> >>
> >> >>> Hello everyone,
> >> >>>
> >> >>> I have been using Postfix and Dovecot for my personal emails for
> >> >years.
> >> >>> After being tired of reinstalling my personal mail server many
> >> >times, I
> >> >>> am currently writing some Ansible scripts to do it automatically.
> >> >>>
> >> >>> I obviously checked the other projects, and did not found
> >anything
> >> >close
> >> >>> to what I am looking for, so I am implementing it now.
> >> >>>
> >> >>> The final goal is to have a box that once online, would setup
> >> >itself, by
> >> >>> creating the certificates, the DKIM keys and update the
> >appropriate
> >> >DNS
> >> >>> records.
> >> >>>
> >> >>> This is so far what I have achieved:
> >> >>> - Automatic generation of certificates using LetsEncrypt
> >> >>> - Automatic update of the domain entries: imap, smtp, webmail,
> >etc.
> >> >>> - Automatic generation of a DKIM keys
> >> >>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
> >> >>> - LDAP server for user accounts, with or without system login.
> >> >>> - Installation of Postfix, Dovecot and Roundcube
> >> >>>
> >> >>> Sending DKIM signed emails is working, and the IMAP server is
> >> >configured
> >> >>> as well, although basic.
> >> >>>
> >> >>> The postfix and dovecot configuration are not yet entirely
> >finished.
> >> >I
> >> >>> am planing to add an anti spam system, and sieve, amongst other
> >> >things.
> >> >>>
> >> >>> Although in development during my spare time, the system is
> >normally
> >> >>> robust and you should be able to run it multiple times without
> >> >errors.
> >> >>>
> >> >>> If anyone is interested to use it, to have a look, or to take
> >part,
> >> >it
> >> >>> is here: https://github.com/progmaticltd/homebox
> >> >>>
> >> >>> Kind regards,
> >> >>> André Rodier.
> >> >>
> >> >>
> >>
> >> Non static ip'd mail servers are also blocked because they're
> >typically
> >> spammers.
> >> --
> >>
> >> Thanks,
> >>
> >> Fabian S.
> >>
> >> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
> >>
>
> Stephan h, may I ask why you do that? Just out of curiosity.
> --
>
> Thanks,
>
> Fabian S.
>
> OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
>


Re: hosting emails at home

2017-12-10 Thread Stephan H
Originally I was on a business connection, so no port blocking.  I moved to
a residential connection at home and they blocked port 25.  So  I  enabled
my VPS in the cloud to relay my mail to the imap server in my home.  It's a
very simple setup.  I only allow a couple IPs to relay anything through (
my home IP and other VPS's).  Any other connection must be delivering to my
IP or it's rejected.  Then In the transport maps tell it to utilize a non
standard port

domain.com  relay:[home.domain.com:28]

On the home server's postfix I just define the relay host which also uses a
non standard port

relayhost: [vps1.domain.com:26]

At this point you just have to setup your postfix/dovecot config how you
want.  I'm using postfixadmin and both postfix and dovecot use mysql to
determine domains, users, and passwords.

On Sun, Dec 10, 2017 at 2:27 PM, Fabian A. Santiago <
fsanti...@garbage-juice.com> wrote:

> On December 10, 2017 5:25:46 PM EST, Stephan H <her...@gmail.com> wrote:
> >Which part?  Hosting the email server at home or the relay in the
> >cloud?
> >
> >On Dec 10, 2017 14:53, "Fabian A. Santiago"
> ><fsanti...@garbage-juice.com>
> >wrote:
> >
> >> On December 10, 2017 3:39:05 PM EST, Stephan H <her...@gmail.com>
> >wrote:
> >> >I have dovecot postfix setup on my home server as well.  I use a
> >> >virtual
> >> >server in the cloud as my mx record and mail relay and have my home
> >> >record
> >> >on dynamic dns.  It's really effective.
> >> >
> >> >On Dec 10, 2017 2:37 PM, "Fabian A. Santiago"
> >> ><fsanti...@garbage-juice.com>
> >> >wrote:
> >> >
> >> >> On December 10, 2017 2:49:35 PM EST, "André Rodier"
> ><an...@rodier.me>
> >> >> wrote:
> >> >> >Hello Mike,
> >> >> >
> >> >> >Yes, I am using a static IP address, but in theory, you could use
> >a
> >> >> >dynamic one.
> >> >> >
> >> >> >Nothing technically would prevent email exchanges between two
> >boxes,
> >> >as
> >> >> >long as the SPF records are up to date and the DKIM is properly
> >> >setup.
> >> >> >
> >> >> >Unfortunately, some ISPs are simply blacklisting full range of
> >> >private
> >> >> >IP addresses just because they are not officials / commercials.
> >> >> >
> >> >> >Kind regards,
> >> >> >André
> >> >> >
> >> >> >On 10/12/17 19:24, Mike wrote:
> >> >> >>
> >> >> >> Nice.
> >> >> >>
> >> >> >> Are you using a static IP in this setup?
> >> >> >>
> >> >> >> It doesn't seem like it, but wanted to be sure.
> >> >> >>
> >> >> >> Mike.
> >> >> >>
> >> >> >> Quoting André Rodier <an...@rodier.me>:
> >> >> >>
> >> >> >>> Hello everyone,
> >> >> >>>
> >> >> >>> I have been using Postfix and Dovecot for my personal emails
> >for
> >> >> >years.
> >> >> >>> After being tired of reinstalling my personal mail server many
> >> >> >times, I
> >> >> >>> am currently writing some Ansible scripts to do it
> >automatically.
> >> >> >>>
> >> >> >>> I obviously checked the other projects, and did not found
> >> >anything
> >> >> >close
> >> >> >>> to what I am looking for, so I am implementing it now.
> >> >> >>>
> >> >> >>> The final goal is to have a box that once online, would setup
> >> >> >itself, by
> >> >> >>> creating the certificates, the DKIM keys and update the
> >> >appropriate
> >> >> >DNS
> >> >> >>> records.
> >> >> >>>
> >> >> >>> This is so far what I have achieved:
> >> >> >>> - Automatic generation of certificates using LetsEncrypt
> >> >> >>> - Automatic update of the domain entries: imap, smtp, webmail,
> >> >etc.
> >> >> >>> - Automatic generation of a DKIM keys
> >> >> >>> - Automatic update of specific records (MX, SPF, DKIM, etc.)
> >&g