[courier-users] szmlink counts as quota

[SZÉPE Viktor]

Hello!

I am trying to prevent multiple Trash, Junk, Sent folders created by  
various mail clients.

For example these are the symlinks for Sent:
.Sent
.Sent Items -> .Sent
.Sent Messages -> .Sent

Could it be that that Courier counts Sent folder size three time while  
calculating quota?
BTW this account is over 1GB quota while the Maildir folder's size is 481 MB.



SZÉPE Viktor
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md
-- 
+36-20-4242498  s...@szepe.net  skype: szepe.viktor
Budapest, III. kerület





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[Ángel]

On 2017-05-18 at 19:03 +0200, Alessandro Vesely wrote:
> Although the real issue is maildrop, let me note the following about 
> courier-base:
> 
> * couriertcpd could be just suggested or recommended, not required,
> 
> * testmxlookup could be moved to courier-mta,
> 
> * I don't see how maildir utilities can be useful on a standalone SMTP server.
> Perhaps they could be moved to courier-imap, courier-pop, or both.
> 
> Ale

While we are on the topic of debian package wishlists...
(not sure if this is the best venue, but otoh I feel it's good to
discuss it first rather than simply filing a bug)


...I would like having couriertls at its own package:

1) It is a standalone tool, useful on its own.
It can be used as a cli tool (as a "tls telnet"), as well as by other
programs (I have used it that way to support TLS)

2) It used to be at a different package, so it would be consistent with
previous practice
(kind of, it had an -apparently unneeded- depends on courier-base)

3) That would allow having a virtual package with two versions, so that
the sysadmin could choose whether to have it linked against openssl or
gnutls (they used to have slightly different features, so in the past I
ended up recompiling the courier-ssl package to switchj libraries)

This is specially interesting from a security point of view imho, since
should a problem develop on either of these libraries, you could easily
switch to the other library while keeping the upper level server
unchanged (assuming the config used compatible ciphers, etc.).


I apologize for the annoyance, tell me if there's anything I can do to
help with it.


Best regards


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[Sam Varshavchik]

Alessandro Vesely writes:

Although the real issue is maildrop, let me note the following about courier- 
base:


* couriertcpd could be just suggested or recommended, not required,


It most certainly is required. The default startup script require it.

I suppose you could customize the package to use inetd. Or systemd. To  
listen on the port and start the server.


This would mostly work for imap and pop3. But this is going to lose quite a  
bit of functionality with smtp, which depends on couriertcpd for setting  
environment variables based on the connecting IP address.




pgpwicQitusdk.pgp
Description: PGP signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[SZÉPE Viktor]

Idézem/Quoting Alessandro Vesely :

> On Thu 18/May/2017 00:19:07 +0200 Markus Wanner wrote:
>> On 17.05.2017 09:48, Alessandro Vesely wrote:
>>
>>> My suggestion is to avoid disassembling the Courier tarball.  That is, have
>>> maildrop included by default in courier-mta, and possibly merge it with
>>> courier-base as well (why were they split, BTW?)
>>
>> Flexibility. And separation of concerns.
>>
>> I like being able to install courier-imap, but not courier-pop, for
>> example. Or running just the courier-mta without either of the other
>> two. That's quite common for Debian, I'd say.
>
> Although the real issue is maildrop, let me note the following about  
> courier-base:
>
> * couriertcpd could be just suggested or recommended, not required,
>
> * testmxlookup could be moved to courier-mta,
>
> * I don't see how maildir utilities can be useful on a standalone  
> SMTP server.
> Perhaps they could be moved to courier-imap, courier-pop, or both.
>
> Ale
> --

Debian policy states that a software should not be in more than one package.
It may seem strange that some parts are abstracted out of a common code base.

In Debian it is usual to have one software component in one package.
For example when you update it you don't have to download and install  
the whole software.

Looking at things from inside Debian these may come handy: you never  
have to deal with building a software from source, maintainers do that  
for you.

All the best to you!


SZÉPE Viktor
https://github.com/szepeviktor/debian-server-tools/blob/master/CV.md
-- 
+36-20-4242498  s...@szepe.net  skype: szepe.viktor
Budapest, III. kerület





--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[Alessandro Vesely]

On Thu 18/May/2017 00:19:07 +0200 Markus Wanner wrote:
> On 17.05.2017 09:48, Alessandro Vesely wrote:
> 
>> My suggestion is to avoid disassembling the Courier tarball.  That is, have
>> maildrop included by default in courier-mta, and possibly merge it with
>> courier-base as well (why were they split, BTW?)
> 
> Flexibility. And separation of concerns.
> 
> I like being able to install courier-imap, but not courier-pop, for
> example. Or running just the courier-mta without either of the other
> two. That's quite common for Debian, I'd say.

Although the real issue is maildrop, let me note the following about 
courier-base:

* couriertcpd could be just suggested or recommended, not required,

* testmxlookup could be moved to courier-mta,

* I don't see how maildir utilities can be useful on a standalone SMTP server.
Perhaps they could be moved to courier-imap, courier-pop, or both.

Ale
-- 

























signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[Sam Varshavchik]

Markus Wanner writes:


> The
> differences are in the configuration. The biggest difference is
> maildrop, because it ties in directly into mail delivery, and it has
> Courier-specific features, and Courier has maildrop-specific features as
> well.

Understood.

(If you're provided a maildrop binary, how do you tell which variant it is?)


$ maildrop -v
maildrop 2.8.5 Copyright 1998-2015 Double Precision, Inc.
Courier-specific maildrop build. This version of maildrop should only be used
with Courier, and not any other mail server.

Fairly unambiguous. This part of the version string is only present in the  
courier-specific maildrop build.






pgpB6mBu8cYkE.pgp
Description: PGP signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Re: [courier-users] Message delivered, but no message in INBOX

[Markus Wanner]

Sam,

On 05/18/2017 12:29 AM, Sam Varshavchik wrote:
> When I refer to source releases, I always refer to
> http://www.courier-mta.org/download.html

Thanks for clarifying, that's usually referred to as upstream in Debian,
whereas "the package" is the result of packaging for Debian. Please
excuse the confusion this may have caused, I'll be more specific in the
future.

> I am not familiar with the details of Debian's packaging. I can only
> explain how I package the source.

Fair enough, you don't need to be. I not familiar with upstream sources,
either. And despite you thinking it's simple, it had quite some
surprises for me. I'm glad we uncovered those and I hope to find ways
that work well for both of us.

> There are no functional differences, except for maildrop.

I'm glad to hear.

> The
> differences are in the configuration. The biggest difference is
> maildrop, because it ties in directly into mail delivery, and it has
> Courier-specific features, and Courier has maildrop-specific features as
> well.

Understood.

(If you're provided a maildrop binary, how do you tell which variant it is?)

> It should be possible to build courier, and selectively carve out the
> built imap and sqwebmail components to be individually installed without
> courier.

I think that's how it's done for Debian, up until now.

> But that's going to require writing custom startup scripts. There's only
> one startup script for courier, that starts everything. It's fairly easy
> to carve out imap and webmail as an optional subpackage. Courier's
> startup script will try starting them only if it finds them installed.
> But left to their own merits, the subpackages won't do anything without
> writing and adding some startup scripts into the subpackages. Then they
> can be installed independently and use without Courier. But then, you'll
> also have to fix courier's startup script not to try starting them
> itself, since the subpackage will take care of with its own startup script.

Yes, I think all of those startup scripts are in place, including
systemd units. This allows Debian users to control (and install) the
services individually, which I think is an important feature.

Sounds like the only remaining issue is maildrop. I'll investigate
further on possible solutions.

Thank you for explaining and for your understanding of the Debian
specific requirements. I'm well aware those may seem weird sometimes and
are often hard to meet.

Kind Regards

Markus Wanner




signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users