Bug 39059 - Test univention-fetchmail
Test univention-fetchmail
Status: NEW
Product: UCS Test
Classification: Unclassified
Component: Mail
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-07-30 22:58 CEST by Sönke Schwardt-Krummrich
Modified: 2016-10-05 20:19 CEST (History)
0 users

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2015-07-30 22:58:54 CEST
http://docs.univention.de/manual-4.0.html#mail::fetchmail

The package univention-fetchmail adds additional attributes to the users/user object that hold information from where the fetchmail service should fetch new mails and deliver it to the local mailbox. This is used to fetch mail e.g. from your provider if mail is not delivered directly to your mail server.

Usually a remote server is specified. In the test script it should be sufficient to use a different IMAP/POP3 mailbox on the local system. If is possible that fetchmail/postfix rejects mails because a possible mail loop is detected. In that case please try to use the NetworkLoop.

Scenario:
new mail ===> mailbox of user A ==> fetchmail ==> mailbox of user B
- the test should save a copy of /etc/fetchmailrc before any LDAP changes are 
  performed
- create 2 users A and B
  - for user B the fetchmail settings have to be set: the mails shall be fetched 
    from mailbox A on $FQDN
- the default /etc/fetchmailrc contains an interval of 1200 seconds. This 
  interval should be reduced to e.g. 10 seconds by the script (load whole file 
  and replace statement accordingly).
- restart fetchmail
- send mail with token to user A and wait until the token appears in mailbox B


Please also check the additional fetchmail options:
- keep mails on server (is mailbox A empty after token appears in mailbox B?)
- use IMAP or POP3: cyrus and dovecot support both and can be deactivated 
  seperately (just to be sure, that the correct protocol is used)
- encrypted connection (by default please use always an encrypted connection; 
  the common usecase)