Couple of questions

[Steve Webb]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>> 1.)  If a pop user selects "keep messages on server" they start to see
>> duplicate emails.  I saw that other people on the listserv have also had
>> the same issues, but there's not been any resolution to this issue.  Q:
>> How come Cyrus doesn't implement the correct bahaviour, and is there any
>> work-around other than switching to IMAP over POP?  I've got pop users
>> that can't access IMAP (using phones for checking email when on travel
>> with "leave messages on server" then suck down the emails when they arrive
>> back at a desktop).  It's not feasable for them to move to IMAP and they
>> require this functionality.
>
> Are you certain this is the fault of Cyrus and not a deficient client
> that happened to work with UW?  Are they all using the same kind of
> phone (what phone)?

I confirmed that this happens with outlook, thunderbird and fetchmail.

The phone is a Palm Treo.

>> 2.)  It seems that Cyrus is inserting headers that confuse sendmail and/or
>> procmail.  When I'm tailing my procmail log, I see that all emails are
>> "From: cyrus at mail".  I'm guessing that procmail is getting this from the
>> "Return-Path:" header that doesn't get inserted into the email with
>> sendmail.  Q: Can I tell Cyrus to not insert this header or is there a
>> work-around for procmail to detect the correct From: header and not get
>> confused?
>
> I'm pretty certain such headers are coming from your MTA (postfix) and
> not Cyrus.  But I've never used Cyrus with procmail as SIEVE is usually
> sufficient.

Would postfix be inserting the "Return-Path: cyrus at mail" header?  I 
thought that it got inserted by the 'deliver' binary which I thought was 
part of Cyrus.

- - Steve

- -- 
Steve Webb - Lead System Administrator for Pronto.com
Email: swebb at pronto.com  (Please send any work requests to: rt at pronto.com)
Cell: 303-564-4269, Office: 303-497-9367, YIM: scumola
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFIhPyDbhtJr2D5JAsRAnK/AJ9MwnnDHzJhkwRfi/7Z+w445M3/eACdFIad
nDRAb0GEVlPXP+37pDWFeN0=
=aJej
-----END PGP SIGNATURE-----