similar to: Fwd: NFS question

We have migrated a mailsystem to postfix/dovecot, using the courier migrate script, and we have run into a problem with dovecot-uidlist. The messages are not listed in the correct order .. This is an example dovecot-uidlist -file: 1 1177585200 49 22 1179084774.P7191Q0M321163.webmail1,S=8245:2,S 24 1179377823.P15932Q0M835219.smtp1,S=3462:2,S 25 1179668346.P23942Q0M941365.webmail1,S=4820357:2,S 31

Here is a OS X message URI in angled brackets: <message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e> Markdown yields: <p><message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e></p> Shouldn't it have given instead: <p><a href="message://%3cE1KzXg9-0000Qb-3G at smtp1.mail.ox.ac.uk%3e">message://%3cE1KzXg9-0000Qb-3G at

On Fri, Feb 13, 2015 at 9:57 AM, Ken Smith <kens at kensnet.org> wrote: > Hi All, > > I'm just wanting to check that my understanding of the settings is correct > as my web searches are finding a lot of dated information. > > If I want a Centos 6 sendmail system act as the secondary MX for domain > bbbbb.co.uk do I just add a > > Connect:bbbbb.co.uk

On Fri, February 13, 2015 10:57, Ken Smith wrote: > Hi All, > > I'm just wanting to check that my understanding of the settings is > correct as my web searches are finding a lot of dated information. > > If I want a Centos 6 sendmail system act as the secondary MX for > domain > bbbbb.co.uk do I just add a > > Connect:bbbbb.co.uk RELAY > >

Hi All, I'm just wanting to check that my understanding of the settings is correct as my web searches are finding a lot of dated information. If I want a Centos 6 sendmail system act as the secondary MX for domain bbbbb.co.uk do I just add a Connect:bbbbb.co.uk RELAY statement into /etc/mail/access and restart sendmail Obviously I have the DNS MX records for the domain are

On Fri, February 13, 2015 11:04 am, Les Mikesell wrote: > On Fri, Feb 13, 2015 at 9:57 AM, Ken Smith <kens at kensnet.org> wrote: >> Hi All, >> >> I'm just wanting to check that my understanding of the settings is >> correct >> as my web searches are finding a lot of dated information. >> >> If I want a Centos 6 sendmail system act as the

I foolishly made the following typo: " disk = [ ''phy:/dev/vg00/virt-smtp1-root,0301,w'', ''phy:/dev/vg00/virt-smtp1-root,0302,w'' ] " instead of: " disk = [ ''phy:/dev/vg00/virt-smtp1-root,0301,w'', ''phy:/dev/vg00/virt-smtp1-swap,0302,w'' ]" (the type was that the same Dom0 block device is used twice in the

Smtp1.song.fi and smtp2.song.fi, our list servers, seem to have gotten listed in the bl.spamcop.net RBL. Spamcop listings are temporary and will time out, and because of occasional major false positives (or perhaps collateral damage?) like this I don't use it to reject mail. Anyone who IS using Spamcop to reject mail has missed much of today's list traffic. -- mail to this

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha1.tar.gz.sig This is the only v1.2.alpha announcement I'm going to send to dovecot-news list. Next announcement will be for either v1.2.beta1 or v1.2.rc1. I'm hoping that v1.2 stabilizes pretty soon. There are no huge changes like there were in 0.99->1.0 or

The ongoing discussion regarding Perl modules and RPMs, prompted me to post an issue I am currently facing. I support a development team that uses various third party tools, some free, some not, some of which are installed via RPMs, and some that are not. The development cycle is 18-24 months long, and then there are many years of support (continuing engineering) after that, for which

Now supported by v2.0. Also as a patch to v1.2: http://dovecot.org/patches/1.2/zlib-compress.diff I'm not really sure if I should commit it to v1.2 code tree. The code contains ugly copy&pasted io_stream_copy() and v1.2 is supposed to be feature complete.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature

http://bugzilla.mindrot.org/show_bug.cgi?id=406 Summary: Build openssh-3.4p1 fails, Mac OS X v1.2 Product: Portable OpenSSH Version: -current Platform: PPC OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

In RelaseNotes 6.8, at the section "Major changes", the word "TlSv1.2" should be changed to "TLS v1.2" . TlSv1.2 -> TLS v1.2 Now, in this ReleaseNotes, not "CentOS6" but "CentOS 6", And now, not "SMBIOS3.0.0 " but "SMBIOS 3.0.0 ". But now, why not "TLS v1.2" but "TlSv1.2" ?

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha2.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha2.tar.gz.sig Mainly the same fixes as in v1.1.3 -> v1.1.4 plus some more v1.2-specific fixes. Not many people have been testing v1.2 releases. Wonder if there's something I could do to improve that. I guess v1.2 is kind of missing those killer features that would get a

Hi R-Users, I read some texts related to KS-tests. Most of those authors stated, that KS-Tests are not suitable for binned data, but some of them refer to 'other' authors who are claiming that KS-Tests are okay for binned data. I searched for sources and can't find examples which approve that it is okay to use KS-Tests for binned data - do you have any links to articles or

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve

Hello Dovecot users, This is a simultaneous release of new versions of Sieve-related software for Dovecot v1.1 and v1.2. Only the Sieve implementation itself has seen significant development. The ManageSieve packages only have small fixes and the ManageSieve patches are updated as usual to match the new Dovecot releases. Changelog Sieve v0.1.5: * Ported the implementation of the Sieve

Hi Timo, I've just tried to convert my v1.2 configuration to a v2.0 configuration. Below a few obsolete warnings, among others "mail_executable has been replaced by service { executable }", was an interesting error: "doveconf: Error: duplicate listener: 198:" The broken parts of the converted configuration: # 2.0.beta4 (84ffb38839b9): /etc/dovecot/dovecot.conf # OS: Linux

Hello, While updating the ManageSieve implementation to the latest draft specification I noticed a major omission in the way script names are handled. Essentially, script names are directly appended to the sieve storage directory path and suffixed with '.sieve'. This does not take the use of '../' in script names into account. Therefore, clever virtual users that know the